z/OS IBM

Planning for Installation

Version 1 Release 1

GA22-7504-01
z/OS IBM

Planning for Installation

Version 1 Release 1

GA22-7504-01
 Note
Before using this information and the product it supports, be sure to read the general information under “Appendix G.
Notices” on page 285.

Second Edition, June 2001

This is a major revision of GA22–7504–00.
This edition applies to version 1, release 1 of z/OS (5694-A01) and to all subsequent releases and modifications until
otherwise indicated in new editions.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are
not stocked at the address below.
IBM welcomes your comments. A form for readers’ comments may be provided at the back of this publication, or you
may address your comments to the following address:
IBM Corporation
Department 55JA, Mail Station P384
2455 South Road
Poughkeepsie, NY 12601-5400
United States of America

FAX (United States and Canada): 1+845+432-9405

FAX (Other Countries):
Your International Access Code +1+845+432-9405

IBMLink (United States customers only): IBMUSM10(MHVRCFS)

Internet e-mail: [email protected]
World Wide Web: http://www.ibm.com/servers/eserver/zseries/zos/zosqs.html
If you would like a reply, be sure to include your name, address, telephone number, or FAX number.
Make sure to include the following in your comment or note:
v Title and order number of this book
v Page number or topic related to your comment
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1996, 2001. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
 Contents
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

About This Book . . . . . . . . . . . . . . . . . . . . . . . . ix

Who Should Use This Book . . . . . . . . . . . . . . . . . . . . ix
How to Use This Book . . . . . . . . . . . . . . . . . . . . . . ix
Order Numbers of Non-z/OS Publications Referred to in This Book . . . . . . x
Summary of World Wide Web Sites Referred to in This Book . . . . . . . . x

| Summary of Changes . . . . . . . . . . . . . . . . . . . . . xiii

| Changes to This Book for z/OS V1R1 . . . . . . . . . . . . . . . . xiii
| Changes to ServerPac, CBPDO, and SystemPac for z/OS V1R1 . . . . . . xiv

Chapter 1. Learning about z/OS . . . . . . . . . . . . . . . . . . 1

Packaging and Delivery . . . . . . . . . . . . . . . . . . . . . . 1
Introduction to z/OS Elements and Features . . . . . . . . . . . . . 1
List of Base Elements and Optional Features . . . . . . . . . . . . . 3
List of Elements, Features, and Functions Removed from OS/390 . . . . . 20
| List of Elements, Features, and Functions to Be Removed from z/OS . . . . 23
Methods of Installing z/OS. . . . . . . . . . . . . . . . . . . . 24
National Languages in Which z/OS Is Available . . . . . . . . . . . . 25
Integration Testing by IBM . . . . . . . . . . . . . . . . . . . . . 27
Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Service Policy . . . . . . . . . . . . . . . . . . . . . . . . 28
ServerPac Service Level . . . . . . . . . . . . . . . . . . . . 29
CBPDO Service Level . . . . . . . . . . . . . . . . . . . . . 29
SystemPac Service Level . . . . . . . . . . . . . . . . . . . . 30
PSP Information . . . . . . . . . . . . . . . . . . . . . . . 30
Maintenance after Installation . . . . . . . . . . . . . . . . . . 31
Service Distribution . . . . . . . . . . . . . . . . . . . . . . 32
Education and Training . . . . . . . . . . . . . . . . . . . . . . 34
Publications . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 2. Choosing the Software Installation Method . . . . . . . . 37 .

Overview of Methods for Installing z/OS. . . . . . . . . . . . . . . 37 .
ServerPac Overview (Entitled) . . . . . . . . . . . . . . . . . 37 .
CBPDO Overview (Entitled) . . . . . . . . . . . . . . . . . . 38 .
SystemPac Overview (Fee) . . . . . . . . . . . . . . . . . . 38 .
Overview of Other Installation Methods (Fee). . . . . . . . . . . . 39 .
Additional Details about ServerPac, CBPDO, and SystemPac. . . . . . . 39 .
How You Order — ServerPac, CBPDO, and SystemPac. . . . . . . . 39 .
What IBM Does for You — ServerPac, CBPDO, and SystemPac . . . . 40 .
What You Receive from IBM — ServerPac, CBPDO, and SystemPac . . . 42 .
What Actions You Need to Take — ServerPac, CBPDO, and SystemPac 44
Deciding Which Software Installation Method Is Best for You . . . . . . . . 45

Chapter 3. Preparing the Driving System . . . . . . . . . . . . . . 47

What Is the Customized Offerings Driver? . . . . . . . . . . . . . . . 47
Identifying Driving System Software Requirements for ServerPac and
Dump-by-Data-Set SystemPac Orders . . . . . . . . . . . . . . . 48
Requirements to Load Data Sets from the Installation Tapes . . . . . . . 48
Other Driving System Requirements . . . . . . . . . . . . . . . . 51
Preparing for Installation . . . . . . . . . . . . . . . . . . . . 51

© Copyright IBM Corp. 1996, 2001 iii

 Identifying Driving System Software Requirements for Full Volume Dump
SystemPac Orders. . . . . . . . . . . . . . . . . . . . . . . 53
Identifying Driving System Software Requirements for CBPDO Orders . . . . 54
Driving System Wave 0 . . . . . . . . . . . . . . . . . . . . . 54
Driving System Wave 1 . . . . . . . . . . . . . . . . . . . . . 54
Driving System Wave 2 . . . . . . . . . . . . . . . . . . . . . 57
Driving System Wave 3 . . . . . . . . . . . . . . . . . . . . . 57
Identifying Driving System Requirements to Install Subsystems . . . . . . . 57
Identifying Driving System Hardware Requirements . . . . . . . . . . . 57

Chapter 4. Preparing the Target System . . . . . . . . . . . . . . . 59

Choosing Software Products to Install and Identifying Requisites . . . . . . 59
Choosing the z/OS Base and Optional Features. . . . . . . . . . . . 59
Identifying Functional Requisites for z/OS Elements and Features . . . . . 60
Choosing IBM Products That You Want to Run with z/OS . . . . . . . . 60
Choosing ISV Products That You Want to Run with z/OS . . . . . . . . 61
Ordering z/OS and Related IBM Products . . . . . . . . . . . . . . . 61
| Ordering the z/OS V1R1 Upgrade Package for OS/390 V2R10 . . . . . . 62
Identifying Hardware Requirements for the Target System . . . . . . . . . 62
Identifying Processor Requirements . . . . . . . . . . . . . . . . 62
Identifying DASD Space Requirements . . . . . . . . . . . . . . . 63
Identifying I/O Device Requirements . . . . . . . . . . . . . . . . 64
Identifying Service Needed for the Target System . . . . . . . . . . . . 64
If You Are Installing a ServerPac Order... . . . . . . . . . . . . . . 64
If You Are Installing a CBPDO Order... . . . . . . . . . . . . . . . 65
If You Are Installing a SystemPac Order... . . . . . . . . . . . . . . 65
Using Your Existing JES2 or JES3 with z/OS V1R1 . . . . . . . . . . . 65
Allowable JES-BCP Combinations . . . . . . . . . . . . . . . . . 65
JES Data Compatibility . . . . . . . . . . . . . . . . . . . . . 66
Service Required to Use Your Existing JES2 or JES3. . . . . . . . . . 66
ServerPac and SystemPac Delivery of JES2, JES3, and SDSF . . . . . . 66
Placing Your Existing JES2 or JES3 in a Separate Zone . . . . . . . . 67
Using z/OS V1R1 SDSF with Your Existing JES2 . . . . . . . . . . . 68
Migrating Your Existing JES2 or JES3 to z/OS V1R1 Level. . . . . . . . 69

Chapter 5. Ensuring Coexistence . . . . . . . . . . . . . . . . . 71

Coexistence Policy . . . . . . . . . . . . . . . . . . . . . . . 72
OS/390 R6 Coexistence Service . . . . . . . . . . . . . . . . . . 74
OS/390 R7 Coexistence Service . . . . . . . . . . . . . . . . . . 76
OS/390 R8 Coexistence Service . . . . . . . . . . . . . . . . . . 78
OS/390 R9 Coexistence Service . . . . . . . . . . . . . . . . . . 79
| OS/390 R10 Coexistence Service . . . . . . . . . . . . . . . . . . 80
JES2 Coexistence Service . . . . . . . . . . . . . . . . . . . . 81
JES3 Coexistence Service . . . . . . . . . . . . . . . . . . . . 81

Chapter 6. Preparing for Migration . . . . . . . . . . . . . . . . .83

| Planning for z/OS on a z900 Server . . . . . . . . . . . . . . . . .83
How to Use the Migration Tables . . . . . . . . . . . . . . . . . .87
| Migrating from OS/390 R6 to z/OS V1R1 . . . . . . . . . . . . . . .89
| Migrating from OS/390 R7 to z/OS V1R1 . . . . . . . . . . . . . . .99
| Migrating from OS/390 R8 to z/OS V1R1 . . . . . . . . . . . . . . . 110
| Migrating from OS/390 R9 to z/OS V1R1 . . . . . . . . . . . . . . . 121
| Migrating from OS/390 R10 to z/OS V1R1 . . . . . . . . . . . . . . 130
Identifying Migration Actions Needed for ISV Products . . . . . . . . . . 137
Miscellaneous Migration Actions . . . . . . . . . . . . . . . . . . 138
Migrating Files in the /etc Directory . . . . . . . . . . . . . . . . 138

iv z/OS V1R1.0 Planning for Installation

 Migrating Your Application Development Environment . . . . . . . . . 138
Migration Actions for BookManager BookServer . . . . . . . . . . . 138
Migration Actions for C/C++ . . . . . . . . . . . . . . . . . . . 142
Migration Actions for Dynamic Enablement Member IFAPRDxx . . . . . . 142
| Migration Actions for ILM . . . . . . . . . . . . . . . . . . . . 143
Migration Actions for Infoprint Server . . . . . . . . . . . . . . . 144
Migration Actions for JES2 . . . . . . . . . . . . . . . . . . . 147
Migration Actions for Language Environment . . . . . . . . . . . . 147
Migration Actions for ServerPac and SystemPac . . . . . . . . . . . 148
Virtual Storage Migration Considerations . . . . . . . . . . . . . . 149

Chapter 7. Preparing for Customization and Test. . . . . . . . . . . 151

Using Dynamic Enablement on an S/390 Server . . . . . . . . . . . . 151
Deciding Whether to Dynamically Enable . . . . . . . . . . . . . . 152
Dynamic Enablement Step 1: Notify IBM . . . . . . . . . . . . . . 154
Dynamic Enablement Step 2: Update Parmlib . . . . . . . . . . . . 154
Dynamic Enablement Step 3: Establish the Active Parmlib Member . . . . 159
Disabling What Was Enabled . . . . . . . . . . . . . . . . . . 159
Scheduling Test Activities . . . . . . . . . . . . . . . . . . . . 160
Establishing a Fallback Plan and Procedures . . . . . . . . . . . . . 160
Rolling z/OS across a Multisystem Configuration . . . . . . . . . . . . 161

Chapter 8. Preparing for Future Installations . . . . . . . . . . . . 163

System and Installation Requirements . . . . . . . . . . . . . . . . 163
Separating Data from Software . . . . . . . . . . . . . . . . . . 164
Placing Data Sets on Specific Volumes . . . . . . . . . . . . . . . 167
Product Sets . . . . . . . . . . . . . . . . . . . . . . . . 167
Recommended Data Set Placement . . . . . . . . . . . . . . . 170
Implementing the Recommended Data Set Placements . . . . . . . . 181
Choosing a Naming Convention for Data Sets . . . . . . . . . . . . . 183
Using Symbolic Substitution. . . . . . . . . . . . . . . . . . . 183
Data Set Names Restructured . . . . . . . . . . . . . . . . . . 184
Using Indirect Catalog Entries . . . . . . . . . . . . . . . . . . . 184
Using Parmlib Concatenation (Logical Parmlib) . . . . . . . . . . . . 185
DASD Space Utilization and Performance . . . . . . . . . . . . . . 185
Undefined Record Format Data Sets . . . . . . . . . . . . . . . 186
Using Recommended Block Sizes for z/OS Data Sets . . . . . . . . . 186

Appendix A. Installation Plan Skeleton . . . . . . . . . . . . . . . 189

Learn about z/OS . . . . . . . . . . . . . . . . . . . . . . . 189
Prepare the Driving System . . . . . . . . . . . . . . . . . . . . 190
Driving System Components: Software . . . . . . . . . . . . . . 190
Driving System Components: Hardware . . . . . . . . . . . . . . 191
Prepare Target System Hardware and Software . . . . . . . . . . . . 191
Target System Components: Software . . . . . . . . . . . . . . . 191
Target System Components: Hardware . . . . . . . . . . . . . . 192
Ensure Coexistence . . . . . . . . . . . . . . . . . . . . . . 192
Coexistence Service Required . . . . . . . . . . . . . . . . . . 192
Additional Coexistence Actions Required . . . . . . . . . . . . . . 192
Prepare for Migration . . . . . . . . . . . . . . . . . . . . . . 193
Pre-IPL Migration Actions . . . . . . . . . . . . . . . . . . . 193
Post-IPL Migration Actions . . . . . . . . . . . . . . . . . . . 194
Build and Verify the Target System . . . . . . . . . . . . . . . . . 194
Build and Verify the Target System (ServerPac or Dump-by-Data-Set
SystemPac Installation) . . . . . . . . . . . . . . . . . . . 195
Build and Verify the Target System (CBPDO Installation) . . . . . . . . 196

Contents v
 Build and Verify the Target System (SystemPac Full Volume Dump
Installation) . . . . . . . . . . . . . . . . . . . . . . . . 197
Customize and Test the System . . . . . . . . . . . . . . . . . . 198
Customization Actions . . . . . . . . . . . . . . . . . . . . . 198
Test Activities . . . . . . . . . . . . . . . . . . . . . . . . 199
Plan for Future Installations . . . . . . . . . . . . . . . . . . . . 199

Appendix B. Software Requirements for z/OS Elements and Features 201

Appendix C. Minimum Levels of IBM Software Products That Run with

z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Appendix D. Hardware Requirements for z/OS Elements and Features 229

Hardware Requirements for Communications Server . . . . . . . . . . 239
IP Hardware Requirements . . . . . . . . . . . . . . . . . . . 239
SNA Hardware Requirements . . . . . . . . . . . . . . . . . . 242

Appendix E. Data Set Placement Recommendations for Target Volumes 243

CLIST Libraries . . . . . . . . . . . . . . . . . . . . . . . . 243
Data Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 244
EXEC Libraries . . . . . . . . . . . . . . . . . . . . . . . . 250
Font Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 250
Help Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 251
Load Module Libraries . . . . . . . . . . . . . . . . . . . . . . 252
Macro Libraries . . . . . . . . . . . . . . . . . . . . . . . . 257
Message Libraries . . . . . . . . . . . . . . . . . . . . . . . 259
Parameter Libraries (Parmlibs) . . . . . . . . . . . . . . . . . . 262
Panel Libraries . . . . . . . . . . . . . . . . . . . . . . . . 262
Procedure Libraries (Proclibs) . . . . . . . . . . . . . . . . . . . 265
Sample Libraries . . . . . . . . . . . . . . . . . . . . . . . . 265
Skeleton Libraries . . . . . . . . . . . . . . . . . . . . . . . 267
Softcopy Libraries . . . . . . . . . . . . . . . . . . . . . . . 268
Source Libraries . . . . . . . . . . . . . . . . . . . . . . . . 270
Table Libraries . . . . . . . . . . . . . . . . . . . . . . . . 271
Text Libraries . . . . . . . . . . . . . . . . . . . . . . . . . 272

Appendix F. Making a Copy of Your System Software (Cloning) . . . . . 275

Choosing Names . . . . . . . . . . . . . . . . . . . . . . . 276
Initializing the New Volumes . . . . . . . . . . . . . . . . . . . 277
Setting Up SMS . . . . . . . . . . . . . . . . . . . . . . . . 278
Defining New Catalogs and CSI Data Sets . . . . . . . . . . . . . . 278
Copying the Software Data Sets . . . . . . . . . . . . . . . . . . 279
Copying the SMP/E Zones . . . . . . . . . . . . . . . . . . . . 280
Making the Copy Usable . . . . . . . . . . . . . . . . . . . . . 282
Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Migrating to Another System . . . . . . . . . . . . . . . . . . . 282

Appendix G. Notices . . . . . . . . . . . . . . . . . . . . . . 285

Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 286

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

vi z/OS V1R1.0 Planning for Installation

 Tables
1. Base elements and optional features in z/OS V1R1 . . . . . . . . . . . . . . . . . . 4
2. Elements, features, and major functions removed from OS/390 . . . . . . . . . . . . . . 20
3. National languages supported (in addition to U.S. English) and the elements and features
available in each language . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4. Expiration dates for z/OS and OS/390 service support. End-of-service dates with an asterisk (*)
have already been announced. Other end-of-service dates are anticipated based on the
three-year service policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5. DASD storage requirements for all z/OS V1R1 elements and features . . . . . . . . . . . 63
6. Coexistence service (PTFs) needed on OS/390 R6 systems . . . . . . . . . . . . . . . 74
7. Coexistence service (PTFs) needed on OS/390 R7 systems . . . . . . . . . . . . . . . 76
8. Coexistence service (PTFs) needed on OS/390 R8 systems . . . . . . . . . . . . . . . 78
9. Coexistence service (PTFs) needed on OS/390 R9 systems . . . . . . . . . . . . . . . 79
| 10. Coexistence service (PTFs) needed on OS/390 R10 systems . . . . . . . . . . . . . . 80
11. Migrating from OS/390 R8 to z/OS V1R1 . . . . . . . . . . . . . . . . . . . . . . 89
| 12. Migrating from OS/390 R6 to z/OS V1R1 . . . . . . . . . . . . . . . . . . . . . . 89
| 13. Migrating from OS/390 R7 to z/OS V1R1 . . . . . . . . . . . . . . . . . . . . . . 99
| 14. Migrating from OS/390 R8 to z/OS V1R1 . . . . . . . . . . . . . . . . . . . . . 110
| 15. Migrating from OS/390 R9 to z/OS V1R1 . . . . . . . . . . . . . . . . . . . . . 121
| 16. Migrating from OS/390 R10 to z/OS V1R1 . . . . . . . . . . . . . . . . . . . . . 130
17. FEATURENAME values for z/OS priced features and TCP/IP . . . . . . . . . . . . . . 155
18. Software requirements for z/OS elements and features . . . . . . . . . . . . . . . . 201
19. Minimum levels of products that run with z/OS V1R1 . . . . . . . . . . . . . . . . . 217
20. Hardware requirements for z/OS elements and features . . . . . . . . . . . . . . . . 229
21. CLIST libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
22. NLV CLIST libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
23. Data libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
24. NLV Data libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
25. EXEC libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
26. Font and printing libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
27. NLV font and printing libraries . . . . . . . . . . . . . . . . . . . . . . . . . 251
28. Help and English help libraries . . . . . . . . . . . . . . . . . . . . . . . . . 251
29. NLV help libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
30. Required LPA and optional RMODE 31 LPA-eligible load libraries . . . . . . . . . . . . 252
31. LPA-eligible RMODE 24 load libraries. . . . . . . . . . . . . . . . . . . . . . . 253
32. Load libraries for change migration. . . . . . . . . . . . . . . . . . . . . . . . 253
33. Load libraries for callable services . . . . . . . . . . . . . . . . . . . . . . . . 254
34. Other load libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
35. Macro libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
36. NLV macro libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
37. Message and English message libraries . . . . . . . . . . . . . . . . . . . . . . 259
38. NLV message libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
39. Parameter libraries (parmlibs). . . . . . . . . . . . . . . . . . . . . . . . . . 262
40. Panel and English panel libraries . . . . . . . . . . . . . . . . . . . . . . . . 262
41. NLV panel libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
42. Procedure libraries (proclibs) . . . . . . . . . . . . . . . . . . . . . . . . . . 265
43. Sample libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
44. Skeleton and English skeleton libraries . . . . . . . . . . . . . . . . . . . . . . 267
45. NLV skeleton libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
46. Softcopy libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
47. NLV softcopy libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
48. Source libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
49. Table and English table libraries . . . . . . . . . . . . . . . . . . . . . . . . . 271
50. NLV table libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

© Copyright IBM Corp. 1996, 2001 vii

51. Text libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
52. NLV text libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

viii z/OS V1R1.0 Planning for Installation

 About This Book
This book helps you prepare to install z/OS by giving you information you need to
write an installation plan. To install means to perform the tasks necessary to make
the system operational, starting with a decision to either install for the first time or
upgrade, and ending when the system is ready for production. An installation plan is
a record of the actions you need to take to install z/OS; see “Appendix A.
Installation Plan Skeleton” on page 189 for a skeleton.

Do you know about the wizard version of this book?

| The z/OS Installation Planning Wizard is a Web-based, interactive (wizard)
| version of the book you’re reading. It differs from the “static” printed and
| softcopy versions in that the information you read is tailored to your system
| environment, based on questions you answer when you start using the wizard.
| Look for the z/OS Installation Planning Wizard at the z/OS wizard Web site:
| http://www.ibm.com/servers/eserver/zseries/zos/bkserv/wizards.html

The book is not intended to help those:

v Planning to move from a single-system environment to a Parallel Sysplex
environment. For such a move, see the zSeries Parallel Sysplex Customization
Wizard at:
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/wizards.html
| v Planning to migrate from unsupported levels of OS/390 or from MVS/ESA SP. In
order to migrate from these earlier levels, IBM recommends that you use a
fee-based deliverable such as described in “Overview of Methods for Installing
z/OS” on page 37. In addition to standard fee services offerings, IBM offers
customized hourly service contracts that can be built specifically to your
statement of work requirements.

Who Should Use This Book

This book is intended for experienced OS/390 or MVS users planning to install
z/OS Version 1 Release 1. By “experienced”, we mean that the reader’s experience
consists of installing and managing the OS/390 or MVS/ESA SP operating system,
subsystems, network products, non-IBM products, and other software that runs with
OS/390 or MVS/ESA SP.

How to Use This Book

The organization of this book is based on a logical sequence of actions required to
install z/OS. Therefore, we suggest that you start with Chapter 1 and read
sequentially through the book. Fill out your installation plan as you go, or later,
using your own blank installation plan or a copy of the IBM-provided installation
plan skeleton (see “Appendix A. Installation Plan Skeleton” on page 189).

When you read this book in softcopy (online) form and you come across highlighted
references to other books or to World Wide Web sites, you can link directly to those
books or sites in order to search or browse for further information. On the Web, link
by clicking on a highlighted book title or Web address. Elsewhere (CD-ROM or
z/OS BookManager READ), either click on a highlighted book title or put the cursor
on a highlighted book title and press Enter.

© Copyright IBM Corp. 1996, 2001 ix

 Order Numbers of Non-z/OS Publications Referred to in This Book
Where it might help, this book refers to other books for further information. The
order numbers of z/OS books referred to are listed in z/OS Information Roadmap,
GA22-7500. The order numbers of non-z/OS books referred to are listed below.

Hardware:
v S/390 Processor Resource/Systems Manager Planning Guide, GA22-7236
v zSeries 900 Processor Resource/Systems Manager Planning Guide, SB10-7033
| v OSA Planning, GC23-3870
| v z900: OSA-2 Planning Guide, GA22–7477
| v S/390: OSA-Express Customer’s Guide and Reference, SA22-7403
| v z900: OSA-Express Customer’s Guide and Reference, SA22–7476

Languages:
v COBOL for OS/390 & VM and COBOL for MVS & VM Compiler and Run-Time
Migration Guide, GC26-4764
v Language Environment for MVS & VM Fortran Run-Time Migration Guide,
SC26-8499
v PL/I for MVS & VM Compiler and Run-Time Migration Guide, SC26-3118
v VisualAge PL/I for OS/390 Compiler and Run-Time Migration Guide, SC26-9474

ServerPac:
v ServerPac: Installing Your Order (no order number; custom-built to your order
and provided as LIST3820, LIST1403, and BOOK files on ServerPac tapes)
v ServerPac: Using the Installation Dialog, SC28-1244

Subsystems:
v IMS/ESA V5 Release Planning, GC26-8031
v IMS/ESA V6 Release Planning Guide, GC26-8744

SystemPac:
v SystemPac Installation Guide (no order number; custom-built to your order and
provided as LIST3820, LIST1403, and BOOK files on SystemPac tapes)
v SystemPac: CustomPac Dialog Reference (no order number; provided as
LIST3820 file on SystemPac tapes)
v SystemPac: CustomPac Messages (no order number; provided as LIST3820 file
on SystemPac tapes)

Summary of World Wide Web Sites Referred to in This Book

Where necessary, this book refers to information on the World Wide Web. The Web
sites referred to are summarized here for your convenience. If you are viewing this
book using BookManager BookServer, you can click on the Web addresses to link
directly to the Web sites.

Downloads:
v IBM Printing Systems home page, from which you can download IBM Network
Printer Manager for the Web:
http://www.ibm.com/printers
| v Support for Unicode:

x z/OS V1R1.0 Planning for Installation

| http://www6.software.ibm.com/dl/os390/unicodespt-p

| Education and training:

v IBM Education and Training:
http://www.training.ibm.com/

Hardware:
v Architectural enhancements required by z/OS V1R1:
http://www.ibm.com/s390/os390/plug1.html

Installation and ordering:

v CustomPac fee offerings:
http://www.ibm.com/ca/custompac/
v IBM License Manager (ILM):
http://www.ibm.com/servers/eserver/zseries/zos/ilm/
v Planning and Migration Assistant:
http://www.ibm.com/s390/pma/
v ShopzSeries:
| https://inetsd01.boulder.ibm.com/ShopzSeries/ShopzSeries.jsp

ISVs:
| v The Global Solutions Directory, which is a directory of independent software
| vendors (ISVs) and products that support z/OS and OS/390:
| http://www.ibm.com/software/solutions/isv/igssg.nsf/LanguageSelector/?OpenForm
| v Information about compatibility between ISV products and z/OS. Included is
| ISV-provided compatibility information for IBM’s new hardware architecture
| (z/Architecture). This information is voluntary and is provided at the discretion of
| the ISVs. The list of ISVs represented will continue to evolve as vendors assess
| their products for z/Architecture support.
| http://www.ibm.com/eserver/zseries/solutions/s390da/osnp.html
| v Information about selectable ISV products delivered in SystemPac:
http://www.ibm.com/ca/custompac/

Professional, product support, and network services:

v IBM Global Services:
http://www.ibm.com/services/

Publications, flashes, and papers:

| v z/OS Internet Library:
| http://www.ibm.com/servers/eserver/zseries/zos/bkserv/
| v IBM Systems Center publications:
http://www.ibm.com/redbooks
v IBM Systems Center flashes:
http://www.ibm.com/support/techdocs
| v White paper about migration from LANRES:
| http://www.ibm.com/servers/eserver/zseries/library/whitepapers/gm130035.html

| Service:
v System/390 Technical Support:
http://www.ibm.com/s390/support/

About This Book xi

 v System/390 Service Update Facility:
http://www.ibm.com/s390/products/suf/
v RefreshPac (fee offering):
http://www.ibm.com/ca/custompac/
v To download Enhanced HOLDDATA:
http://service.boulder.ibm.com/390holddata.html
v C/C++ service, including informational APARs:
http://www.ibm.com/software/ad/c390/cmvssupp.htm

Wizards (interactive information tools):

| v The z/OS Installation Planning Wizard, the zSeries Parallel Sysplex
| Customization Wizard, and other z/OS wizards:
| http://www.ibm.com/servers/eserver/zseries/zos/bkserv/wizards.html

| z/OS home page:

| http://www.ibm.com/servers/eserver/zseries/zos/

xii z/OS V1R1.0 Planning for Installation

|
| Summary of Changes
| This topic summarizes:
| v The changes made to this book, which documents z/OS Version 1 Release 1
| (V1R1), in comparison to the predecessor book, which documents OS/390
| Version 2 Release 10 (V2R10)
| v The changes made to the ServerPac, CBPDO, and SystemPac installation
| packages for z/OS V1R1, as compared to OS/390 V2R10

| This book includes terminology, maintenance, and editorial changes. Technical

| changes or additions to the text and illustrations are indicated by a vertical line to
| the left of the change.

| Note: The Web-only copy of this book has been changed between the initial
| release of the book and the edition you’re looking at. Some Web addresses
| were updated, some driving system and coexistence PTF numbers were
| added and corrected, and the minimum VM/ESA release required to run
| z/OS as a VM guest on a G5, G6, or Multiprise 3000 server was corrected
| from VM/ESA V2R3 to VM/ESA V2R4. These changes were rolled into the
| edition you’re looking at.
|
| Changes to This Book for z/OS V1R1
| The following changes were made to this book:
| v New product name: z/OS is the follow-on to OS/390. Throughout the book,
| references to the operating system name have been changed appropriately.
| v New and changed elements and features: Two base elements are new: IBM
| License Manager (ILM) and Managed System Infrastructure for Setup (msys for
| Setup). One base element is changed: BCP. No base elements are deleted. No
| optional features are new, changed, or deleted.
| You’ll find descriptions of the new base elements in Table 1 on page 4, software
| requirements in Table 18 on page 201, hardware requirements in Table 20 on
| page 229, and ILM migration information in “Migration Actions for ILM” on
| page 143. Also, there are new target and distribution libraries (and associated
| DDDEFs) for the new base elements. The DDDEFs are listed in “Appendix E.
| Data Set Placement Recommendations for Target Volumes” on page 243.
| v z/OS V1R1 Upgrade Package for OS/390 V2R10: This CBPDO-installable
| deliverable (unpriced feature) is provided exclusively for those migrating from
| OS/390 R10 to z/OS V1R1. Its purpose is to provide a quick and easy upgrade
| to the first release of z/OS. It consists of the two new base elements (ILM and
| msys for Setup) and the one updated base element (BCP). All the other base
| elements and optional features are unchanged from OS/390 R10; there’s no
| need to reinstall them. For ordering information, see “Ordering the z/OS V1R1
| Upgrade Package for OS/390 V2R10” on page 62.
| v Driving system requirements: Driving system requirements have changed as
| follows. For these and all driving system requirements, see “Chapter 3. Preparing
| the Driving System” on page 47.
| – MVS/ESA SP V5 is no longer allowed as a driving system.
| – The minimum OS/390 driving system is now OS/390 R6; it used to be OS/390
| R4.
| – The Customized Offerings Driver (5665-343) is now a subset of an OS/390
| R9 system; it used to be a subset of an OS/390 R4 system.

© Copyright IBM Corp. 1996, 2001 xiii

| – Because the driving system now requires OS/390 UNIX System Services in
| full function mode with a working pax command, data sets (both HFS and
| non-HFS) for ServerPac and dump-by-data-set SystemPac orders must now
| be unloaded only from the driving system. Prior releases allowed the HFS
| data sets to optionally be unloaded from the target system.
| v Processors supported: z/OS V1R1 exploits architectural enhancements that are
| implemented on certain processors. Therefore, z/OS V1R1 runs only on certain
| processors.
| z/OS V1R1 runs on the following new processor (as does OS/390 R10):
| – IBM ^ zSeries 900 (z900)

| z/OS V1R1 also runs on the following processors (as does OS/390 R10):
| – IBM S/390 Parallel Enterprise Server – G5 and G6
| – IBM S/390 Multiprise 3000

| z/OS V1R1 does not run on the following processors that OS/390 R10 runs on:
| – IBM Parallel Enterprise Server – R2 and R3 models as well as G3 and G4
| – IBM S/390 Multiprise 2000
| – IBM S/390 Integrated Server
| – IBM PC Server System/390
| – IBM RS/6000 and System/390 Server-on-Board

| Processor support is described in “Identifying Processor Requirements” on

| page 62. For information about migrating both your processor and operating
| system, see “Planning for z/OS on a z900 Server” on page 83.
| v Dynamic enablement: When z/OS runs on an S/390 server (G5, G6, or
| Multiprise 3000), you enable and disable priced features the way you did in
| OS/390. But when z/OS runs on a z900 server, you use the new base element
| IBM License Manager (ILM) to enable and disable priced features. (Note: ILM will
| be initially delivered 30 March 2001 as part of z/OS. IBM testing of ILM is
| planned to be complete by the end of September 2001, at which time customer
| production use of ILM will be available.) See the discussion of priced features in
| “Introduction to z/OS Elements and Features” on page 1 for more information.
| v Coexistence: OS/390 R10 and z/OS V1R1 are being treated as a single
| coexistence level, rather than two coexistence levels, due to the unique
| characteristics of z/OS V1R1 and the z/OS V1R1 Upgrade Package for OS/390
| V2R10. For details, see“Coexistence Policy” on page 72.
| v End of service: Some information has been deleted because of the expiration of
| service support for MVS/ESA SP V5, OS/390 V1, and the first two releases of
| OS/390 V2. (As of 31 January 2001, MVS/ESA SP V5.1, OS/390 V1R1, and
| OS/390 V1R2 are no longer service supported. As of 31 March 2001, MVS/ESA
| SP V5.2, MVS/ESA SP V5.2.2, OS/390 V1R3, OS/390 V2R4, and OS/390 V2R5
| are no longer service supported.) Among the information items deleted are
| coexistence service (PTF) tables in “Chapter 5. Ensuring Coexistence” on
| page 71 and migration tables in “Chapter 6. Preparing for Migration” on page 83.
| v New topic: “List of Elements, Features, and Functions to Be Removed from
| z/OS” on page 23.
|
| Changes to ServerPac, CBPDO, and SystemPac for z/OS V1R1
| The following changes were made to the packages you can use to install z/OS:
| v The ServerPac and SystemPac offerings are enhanced to help decrease the
| amount of time spent in the CustomPac Installation Dialog while installing z/OS.
| These enhancements include:

xiv z/OS V1R1.0 Planning for Installation

| – The ability to have all or some target and DLIB data sets assigned to physical
| volumes automatically. Using the dialog’s Recommended System Layout
| option, you can quickly configure a system according to z/OS’s recommended
| system layout, which is documented in “Appendix E. Data Set Placement
| Recommendations for Target Volumes” on page 243.
| – A new View and Change facility to make it easier to change data set attributes
| and move data sets between volumes.
| – The ability to rename all data sets in the order.
| – Other enhancements satisfying many customer requirements.
| v ServerPac and SystemPac are enhanced to include the creation of a monoplex
| sysplex environment; the enablement of WLM in goal mode; the enablement of
| the OCSF Base component of the Cryptographic Services element; some SMS
| and IP setup for IBM License Manager (ILM); and the use of the system logger
| for LOGREC, OPERLOG, and ILM. Additionally, a security environment will be
| created to support each of these functions and ILM. Finally, SystemPac is
| enhanced with the enablement of resource recovery services (RRS).
| v SystemPac is further enhanced with the default enablement of the following:
| – CICS Transaction Server for OS/390 V1R3 (5655-147) now has the following
| enabled: CICS log manager, CICS Web support, CICS 3270 bridge, and
| external CICS interface.
| – DB2 Universal Database Server for OS/390 V6R1 (5645-DB2) now has the
| following enabled: DB2 ODBC, DB2 JDBC, DB2 Net.Data, and
| WLM-established stored procedures.

| HOLDDATA cover letters for ISV products installed using SMP/E are now
| supported by SystemPac. The cover letters will be delivered using the same
| mechanism as for IBM products. You will now be able to review the ISV
| HOLDDATA for the service applied to your SystemPac order without the need to
| contact ISV support.

| More ISV products are now available for ordering through SystemPac,
| representing an increase in both the number of products and the vendor
| representation. For a list of available ISVs offered with SystemPac, visit
| http://www.ibm.com/ca/custompac/.
| v The z/OS V1R1 Upgrade Package for OS/390 V2R10 is new, as described in
| “Changes to This Book for z/OS V1R1” on page xiii.
| v ServerPac, CBPDO, and SystemPac driving system requirements have changed,
| as described in “Changes to This Book for z/OS V1R1” on page xiii.

Summary of Changes xv
xvi z/OS V1R1.0 Planning for Installation
|
Chapter 1. Learning about z/OS
| z/OS, the next generation of the OS/390 operating system, enables you to manage
| the volatility of e-business workloads. z/OS and the IBM ^ zSeries 900
| (z900) deliver the 64-bit architecture (z/Architecture) to provide qualities of service
| that are critical for the e-business world. 64-bit real storage support eliminates
| expanded storage and helps eliminate paging. 64-bit real storage support may allow
| you to consolidate your current systems into fewer logical partitions (LPARs) or to a
| single native image.

| z/OS and the z900 server extend the industry-leading flexibility and integration
| features of the S/390 platform with the introduction of Intelligent Resource Director
| (IRD). IRD enables resources to be dynamically managed across LPARs based on
| workload priorities.

| z/OS introduces a new technology to facilitate its manageability. Managed System

| Infrastructure for Setup (msys for Setup) provides a new approach for installing and
| configuring z/OS and products that run on z/OS. This new technology can greatly
| reduce the complexity associated with these tasks today.

| z/OS and the z900 server, along with a new Workload License Charges pricing
| model, offer you flexibility in how your software product licenses are managed and
| charged. The new IBM License Manager (ILM) and other supporting technology
| allow you to pay for products based on the computing resources necessary to
| perform your business tasks.

| Because z/OS is built on OS/390, those familiar with OS/390 will recognize the
| significant features that have been carried forward to z/OS. For example, each new
| level is comprehensively tested by IBM in an environment that simulates customer
| conditions.

| You can find information about z/OS on the Internet at the z/OS Web site:
| http://www.ibm.com/servers/eserver/zseries/zos/

| The rest of this chapter helps you learn about z/OS by describing packaging and
delivery, integration testing by IBM, service, education and training, and
publications.

Packaging and Delivery

This section introduces the z/OS elements and features, lists those that have been
and will be removed from the system, introduces the methods available to install
z/OS, and lists the national languages in which z/OS is available.

Introduction to z/OS Elements and Features

z/OS consists of base elements and optional features:
v The base elements (or simply elements) deliver essential operating system
| functions. The base elements consist of former OS/390 base elements and new
| ones added for z/OS. The base elements are listed in Table 1 on page 4. When
you order z/OS, you receive all of the base elements.
v The optional features (or simply features) are orderable with z/OS and provide
| additional operating system functions. The optional features consist of former
| OS/390 optional features. The optional features are listed in Table 1 on page 4.

© Copyright IBM Corp. 1996, 2001 1

 Optional features are unpriced or priced:
– Unpriced features are shipped to you only if you order them. If you plan to
use any unpriced features, IBM recommends that you order them when you
order your base elements. You must not wait until the next release becomes
available. Once a release’s base elements are no longer orderable, neither
are its unpriced features.
– Priced features are always shipped to you. When IBM packages your order,
we enable the priced features that you ordered. These features are ready to
use after you install z/OS (and customize them as needed). We disable the
priced features that you did not order. Although they are installed on your
system, you cannot use them. Later on, if you decide to use them, you notify
IBM and you enable them dynamically (which is known as dynamic
enablement). The way you dynamically enable depends on your processor:
| - When z/OS runs on an S/390 server (G5, G6, or Multiprise 3000), a z/OS
| product registration service, together with product policy statements,
| determine whether priced features have been ordered and should run.
| Priced features that are ordered concurrently with z/OS are shipped by IBM
| together with policy statements in parmlib that enable the ordered priced
| features. Priced features that have not been ordered are also shipped with
| z/OS, but with policy statements that disable the unordered features.
| If you subsequently enable any of the priced features, those features also
| become subject to the payment terms of your existing z/OS license as
| described in z/OS Licensed Program Specifications. You must notify IBM
| when you enable an optional feature that was shipped disabled from IBM. A
| detailed description of the enablement support for z/OS is in “Using
| Dynamic Enablement on an S/390 Server” on page 151.
| - When z/OS runs on a z900 server, and IBM License Manager (ILM) is
| being used in production mode, ILM manages your use of the product and
| its priced features according to the terms and conditions defined on the
| product certificate. Using ILM, you can update certificates directly to enable
| or disable features. The license change takes effect immediately on your
| system and is communicated to IBM on a monthly basis when you send in
| a reconciliation message.
| The reconciliation message contains records of all certificate changes and
| exception events recorded since the last reconciliation message (typically
| one month). This communication satisfies the requirement for notifying IBM
| when features are enabled. For a detailed description of how to enable or
| disable products using ILM, and how the monthly reconciliation process
| works, see z/OS IBM License Manager Administration.

| Note: ILM will be initially delivered on 30 March 2001 (as part of z/OS
| V1R1) for preproduction use, with Workload License Charges at full
| machine capacity. Customer production use of ILM, with Workload
| License Charges at less than full machine capacity, will be available
| when IBM completes full testing of ILM and you have applied the
| recommended z/OS service to make your system ILM
| production-ready. This testing by IBM is planned to be complete by
| the end of September 2001. Information about the service (PTFs)
| required to make ILM production-ready can be found at
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/. During ILM
| preproduction use on a z900 server, ILM can be active or inactive. If
| ILM is active, you enable features by updating certificates and you
| notify IBM of the change. (There is no communication in a

2 z/OS V1R1.0 Planning for Installation

| reconciliation message). If ILM is inactive, you enable features by
| updating parmlib and you notify IBM of the change.

| Elements and features may be exclusive or nonexclusive:

| v An element or feature is called exclusive to z/OS if it exists only within z/OS (not
| also as a separately orderable, or stand-alone, product) and if future functional
| enhancements will occur only within z/OS.
| v An element or feature is called nonexclusive if it exists both within z/OS and also
| as a stand-alone product.

List of Base Elements and Optional Features

Table 1 on page 4 lists the base elements and optional features in z/OS. The
following table headings are used:
Name What this book calls the element or feature. (To help you distinguish
elements from features, element names in this column are highlighted.)
Function level
The most recent release in which the element or feature changed.
(“Change” means that one or more of the element’s or feature’s FMIDs
[function modification identifiers] was changed, or that the element or
feature was added to the system. New function added in program
temporary fixes (PTFs) is not considered change.) Also, for nonexclusive
elements and features, the equivalent level of the stand-alone product is
listed in parentheses.
Do not confuse the function level with the product level. All elements and
features are at the z/OS V1R1 product level but they are at various function
levels. For example, the product level of DCE Application Support is z/OS
V1R1 DCE Application Support. Its function level is OS/390 R7 DCE
Application Support because OS/390 R7 was the last release in which it
changed.

| Note: ServerPac, CBPDO, and SystemPac contain all elements and

| features listed in the table, but the z/OS V1R1 Upgrade Package for
| OS/390 V2R10 (available in CBPDO format only) contains only the
| elements whose function level is z/OS V1R1. These elements are
| the BCP, ILM, and msys for Setup.
Type and description
v “Type” means the following:
– Whether it’s a base element or optional feature
– Whether the base element or optional feature is exclusive or
nonexclusive to z/OS
– If an optional feature, whether it’s priced or unpriced
– If an optional feature, whether it supports dynamic enablement (note
that all the priced features support dynamic enablement)
v “Description” is a brief description of the element or feature, and
miscellaneous facts about it.

To learn more about the functions that the elements and features provide, see z/OS
Introduction and Release Guide.

Chapter 1. Learning about z/OS 3

 Table 1. Base elements and optional features in z/OS V1R1
Name Function level Type and description
| BCP z/OS V1R1 Type: base element, exclusive.

The Base Control Program (BCP) provides essential operating system

services. The BCP includes the I/O configuration program (IOCP) and
components such as the workload manager (WLM) and system
management facilities (SMF). It also includes the z/OS UNIX System
Services (z/OS UNIX) kernel, which, prior to OS/390 R3, was part of
the base element that is now called z/OS UNIX System Services.

| Unicode callable system services for code set conversion and other
| Unicode text processing functions are available for z/OS V1R1 (as well
| as for OS/390 R8, R9, and R10) via download from
| http://www6.software.ibm.com/dl/os390/unicodespt-p. Support for
| Unicode will be integrated into z/OS V1R2. The Unicode program
| directory is available at:
| v PDF: http://publibfp.boulder.ibm.com/pubs/pdfs/os390/cunpde00.pdf
| v BookManager: http://www.s390.ibm.com/bookmgr-
| cgi/bookmgr.exe/BOOKS/CUNPDE00/CCONTENTS
| The Unicode user’s guide is available at:
| v PDF: http://publibfp.boulder.ibm.com/pubs/pdfs/os390/cunuge00.pdf
| v BookManager: http://www.s390.ibm.com/bookmgr-
| cgi/bookmgr.exe/BOOKS/CUNUGE00/CCONTENTS
|
BDT OS/390 R2 Type: base element, exclusive.

Bulk Data Transfer (BDT) provides the base services that the optional
BDT features (BDT File-to-File and BDT SNA NJE) need to transfer
data from one computer system to another. BDT became exclusive in
OS/390 R2.

You cannot activate any BDT functions until one or both of the optional
BDT features is enabled.
BDT File-to-File OS/390 R2 Type: optional feature, exclusive, priced, can be dynamically enabled.

BDT File-to-File allows users at one z/OS system in a SNA network to

copy data sets to or from another z/OS system in the network. This
feature is related to the element BDT.
BDT SNA NJE OS/390 R2 Type: optional feature, exclusive, priced, can be dynamically enabled.

BDT SNA NJE allows JES3 users to transmit jobs, output, commands,
and messages from one computer system to another within a SNA
network. This feature is related to the element BDT and the feature
JES3.
BookManager OS/390 R8 Type: base element, exclusive.
BookServer
BookManager BookServer converts BookManager books to HTML for
display through a web browser. This element was new to OS/390 in
R4. As of OS/390 R9 it became exclusive; the equivalent stand-alone
product, BookManager BookServer for World Wide Web for MVS/ESA
V2R2, 5655-A20, is no longer marketed.

4 z/OS V1R1.0 Planning for Installation

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
BookManager BUILD OS/390 R1 Type: optional feature, nonexclusive, priced, can be dynamically
enabled.
(BookManager
BUILD/MVS V1R3, BookManager BUILD creates softcopy books that can be used by any
5695-045) of the BookManager products, such as BookManager READ or
BookManager BookServer.
BookManager OS/390 R1 Type: base element, nonexclusive.
READ
(BookManager BookManager READ is used to display, search, and manage online
READ/MVS V1R3, books and bookshelves. A related optional feature is BookManager
5695-046) BUILD.

In OS/390 R10, the DBCS Print Utility formerly in the Softcopy Print
| element was added to BookManager READ via PTF UQ99324.
C/C++ IBM Open OS/390 R10 Type: base element, exclusive.
Class Library
C/C++ IBM Open Class Library provides a set of C/C++ class libraries.

Because the C/C++ IBM Open Class Library is a base element, your
applications can use it at run time without the requirement for you to
have a license for either the C/C++ with Debug Tool or C/C++ without
Debug Tool features. Also, your applications can access the required
dynamic link libraries (DLLs); you do not have to use the DLL Rename
Utility to package and redistribute these DLLs with your applications.

As of OS/390 R10, the C/C++ SOM Enable Class Library was removed
from OS/390.
C/C++ with Debug OS/390 R10 Type: optional feature, exclusive, priced, can be dynamically enabled.
Tool
C/C++ with Debug Tool includes:
v A C compiler
v A C++ compiler
v A debug tool, which runs with C and C++ as well as other languages
v C/C++ application development utilities.

This feature is related to the base element C/C++ IBM Open Class
Library.

The C/C++ Database Access Class Library (DACL) Utility was removed
as of OS/390 R4.

You can order only one of the two C/C++ features (C/C++ with Debug
Tool or C/C++ without Debug Tool).
C/C++ without OS/390 R10 Type: optional feature, exclusive, priced, can be dynamically enabled.
Debug Tool
This feature is the same as the C/C++ with Debug Tool feature except
that it does not have the Debug Tool component.

Chapter 1. Learning about z/OS 5

Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
Communications OS/390 R10 Type: base element, exclusive, can be dynamically enabled (see “z/OS
Server Alternate Base” on page 60).

Communications Server (also known as CS z/OS) supports secure

TCP/IP, SNA, and UNIX networking throughout an enterprise. It gives
you the ability to connect subsystems and applications to each other,
and to connect network devices (such as terminals and printers) to the
system.

Communications Server consists of two components: IP Services and

SNA Services. SNA Services includes AnyNet function. Prior to OS/390
R6, IP Services was the base element TCP/IP and SNA Services was
the base element VTAM.

In OS/390 R6 and R7, this element was known as eNetwork

Communications Server. In OS/390 R8 it was renamed SecureWay
Communications Server. In OS/390 R10 it was renamed IBM
Communications Server. In z/OS V1R1 it was renamed
Communications Server.

Related optional features are Communications Server NPF,

Communications Server Security Level 1, Communications Server
Security Level 2, and Communications Server Security Level 3.

See Table 2 on page 20 for functions that have been removed from
Communications Server.
Communications OS/390 R10 (but see Type: optional feature, exclusive, unpriced, cannot be dynamically
Server NPF description) enabled.

Communications Server NPF provides a printing function that reroutes

print data to the IP network. This feature is exclusive as of OS/390 R5.

Prior to OS/390 R7, this feature was known as TCP/IP NPF. In OS/390
R7 it was renamed eNetwork Communications Server NPF. In OS/390
R10 it was renamed IBM Communications Server NPF. In z/OS V1R1 it
was renamed Communications Server NPF.

Even though this feature’s FMID changed in OS/390 R10, the feature’s
function did not change.

Infoprint Server should be considered IBM’s strategic replacement for

Communications Server NPF. Significant future enhancements are not
planned for Communications Server NPF.

6 z/OS V1R1.0 Planning for Installation

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
Communications OS/390 R10 Type: optional feature, exclusive, unpriced, cannot be dynamically
Server Security Level enabled.
1
Communications Server Security Level 1 provides authentication and
security services in a TCP/IP network environment using Kerberos
non-DES encryption.

This feature was new to OS/390 in R7. It was then known as

SecureWay Communications Server Security Level 1. In OS/390 R10 it
was renamed IBM Communications Server Security Level 1. In z/OS
V1R1 it was renamed Communications Server Security Level 1.

This feature is related to the base element Communications Server.

As of OS/390 R10, IP Security CDMF has been removed from this

feature and merged into the base element Communications Server. IP
Security SSL RC2/RC24 has also been removed from this feature. The
level of IP Security SSL encryption that is used is determined by the
level of base element Cryptographic Services.

Communications Server Security Level 1 and Communications Server

Security Level 2 are mutually exclusive. Only one needs to be ordered
for you to obtain additional security function over what is provided in
the z/OS base.

| IBM plans to remove Communications Server Security Level 1 from

| z/OS as of V1R2. V1R1 will be the last release of z/OS that contains
| Communications Server Security Level 1. For more details, see “List of
| Elements, Features, and Functions to Be Removed from z/OS” on
| page 23.

Chapter 1. Learning about z/OS 7

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
Communications OS/390 R10 Type: optional feature, exclusive, unpriced, cannot be dynamically
Server Security Level enabled.
2
Communications Server Security Level 2 provides authentication and
security services in a TCP/IP network environment using Kerberos
56-bit DES encryption.

This feature was new to OS/390 in R7. It was then known as

SecureWay Communications Server Security Level 2. In OS/390 R10 it
was renamed IBM Communications Server Security Level 2. In z/OS
V1R1 it was renamed Communications Server Security Level 2.

This feature is related to the base element Communications Server.

As of OS/390 R10, IP Security DES/CDMF and SNMP CBC 56-bit DES

have been removed from this feature and merged into the base
element Communications Server. IP Security SSL 56-bit has also been
removed from this feature. The level of IP Security SSL encryption that
is used is determined by the level of base element Cryptographic
Services.

Communications Server Security Level 1 and Communications Server

Security Level 2 are mutually exclusive. Only one needs to be ordered
for you to obtain additional security function over what is provided in
the z/OS base.

| IBM plans to remove Communications Server Security Level 2 from

| z/OS as of V1R2. V1R1 will be the last release of z/OS that contains
| Communications Server Security Level 2. For more details, see “List of
| Elements, Features, and Functions to Be Removed from z/OS” on
| page 23.
Communications OS/390 R10 Type: optional feature, exclusive, unpriced, cannot be dynamically
Server Security Level enabled.
3
Communications Server Security Level 3 provides authentication and
security services in a TCP/IP network environment using IP SEC TDES
encryption. It supports packet filtering, tunnels, and network address
translation (NAT), which enable secure communication over private and
public networks. This feature provides the highest level of security of
the three Communications Server security features.

This feature was new to OS/390 in R7. It was then known as

SecureWay Communications Server Security Level 3. In OS/390 R10 it
was renamed IBM Communications Server Security Level 3. In z/OS
V1R1 it was renamed Communications Server Security Level 3.

This feature is related to the base element Communications Server and

to the Firewall Technologies component of the SecureWay Security
Server feature.

The availability of this feature outside the U.S. is subject to U.S. export
regulations.

You can order Communications Server Security Level 3 in addition to

one of the other two levels (Communications Server Security Level 1
and Communications Server Security Level 2).

8 z/OS V1R1.0 Planning for Installation

Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
Cryptographic OS/390 R10 Type: base element, exclusive.
Services
Cryptography is the transformation of data to conceal its meaning. In
z/OS, the base element Cryptographic Services, introduced in OS/390
R7, provides the following base cryptographic functions: data secrecy,
data integrity, personal identification, digital signatures, and the
management of cryptographic keys. Keys as long as 56 bits are
supported by this base element. (Keys longer than 56 bits are
supported by the related optional features OCSF Security Level 3 and
System SSL Security Level 3.)

Cryptographic Services consists of the following components, all of

which were last updated in OS/390 R10:
v OCSF Base.
v System Secure Sockets Layer (SSL) Base.
v Integrated Cryptographic Service Facility (ICSF). This component
started out as a nonexclusive base element in OS/390 R4 and
became exclusive in OS/390 R6. In OS/390 R7 it became a
component of Cryptographic Services.

As of OS/390 R9, Cryptographic Services includes the functions

formerly in optional features OCSF France, OCSF Security Level 1,
and OCSF Security Level 2. As of OS/390 R10, Cryptographic Services
includes the functions formerly in optional features IBM HTTP Server
Export Secure, IBM HTTP Server France Secure, and System SSL
Security Level 2. As a result, these optional features were removed
from OS/390.
DCE Application OS/390 R7 Type: base element, exclusive.
Support
DCE Application Support facilitates the interaction between Distributed
Computing Environment (DCE) clients and CICS or IMS regions. This
element was new in OS/390 R4.

As of OS/390 R6, the word “OpenEdition” was dropped from the

beginning of this element’s name.
DCE Base Services OS/390 R9 Type: base element, exclusive.

DCE Base Services provides services for developing and running

client/server applications, including remote procedure call, directory,
security, and distributed time services. This element is at the Open
Group Open Software Foundation (OSF) DCE 1.1 level.

As of OS/390 R6, the word “OpenEdition” was dropped from the

beginning of this element’s name. As of OS/390 R8, the LDAP Client
component was moved to the SecureWay Security Server feature.

As of OS/390 R9, DCE Base Services includes the function formerly in

optional features DCE User Data Privacy CDMF and DCE User Data
Privacy DES/CDMF. These optional features were removed from
OS/390. The function enables data encryption using the commercial
data masking facility (CDMF) and data encryption standard (DES)
algorithms.

Chapter 1. Learning about z/OS 9

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
DFSMSdfp OS/390 R10 Type: base element, exclusive.

DFSMSdfp provides storage, data, program, and device management

functions. Related optional features are DFSMSrmm, DFSMSdss, and
DFSMShsm.

DFSMSdfp was both a component of stand-alone product DFSMS/MVS

(5695-DF1) and, in OS/390 R1 through R9, a nonexclusive base
element of OS/390. As of OS/390 R10, DFSMSdfp is exclusive.
DFSMSdss OS/390 R10 Type: optional feature, exclusive, priced, can be dynamically enabled.

DFSMSdss copies and moves data for backup and recovery, and to
reduce free-space fragmentation.

Prior to DFSMS/MVS, DFSMSdss was a stand-alone product called

Data Facility Data Set Services (DFDSS) V2. As of OS/390,
DFSMSdss was both a component of stand-alone product
DFSMS/MVS (5695-DF1) and, through OS/390 R9, a nonexclusive
optional feature of OS/390. As of OS/390 R10, DFSMSdss is exclusive.
| DFSMShsm (and OS/390 R10 Type: optional feature, exclusive, priced, can be dynamically enabled.
| DFSMSdss)
DFSMShsm provides automated DASD storage management, including
space management for low and inactive data, and availability
management for accidental data loss caused by local and site
disasters. DFSMShsm also lets you make effective use of tape media.

Prior to DFSMS/MVS, DFSMShsm was a stand-alone product called

Data Facility Hierarchical Storage Manager (DFHSM). As of OS/390,
DFSMShsm was both a component of stand-alone product
DFSMS/MVS (5695-DF1) and, through OS/390 R9, a nonexclusive
optional feature of OS/390. As of OS/390 R10, DFSMShsm is
exclusive.

| DFSMShsm requires DFSMSdss. For this reason, DFSMShsm is not

| available by itself. If you want to use DFSMShsm, you must order the
| DFSMShsm/DFSMSdss combination. (DFSMSdss is also available by
| itself for those who don’t want DFSMShsm.)
DFSMSrmm OS/390 R10 Type: optional feature, exclusive, priced, can be dynamically enabled.

DFSMSrmm helps you manage your removable media as one

enterprise-wide library across systems that can share DASD.

DFSMSrmm was both a component of stand-alone product

DFSMS/MVS (5695-DF1) and, in OS/390 R1 through R9, a
nonexclusive optional feature of OS/390. As of OS/390 R10,
DFSMSrmm is exclusive.
DFSORT OS/390 R7 Type: optional feature, nonexclusive, priced, can be dynamically
enabled.
(DFSORT V1R14,
5740-SM1) DFSORT sorts, merges, and copies data. This feature was new in
OS/390 R2.

10 z/OS V1R1.0 Planning for Installation

Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
Distributed File OS/390 R10 Type: base element, exclusive.
Service
Distributed File Service includes the DCE file serving (DFS) component
of the Open Group Open Software Foundation (OSF) DCE. The file
serving support (the DFS client and server) is at the OSF 1.2.2 level.

This element also delivers server message block (SMB) file/print

serving support. The SMB support is based on the X/Open PC
Interworking: SMB, Version 2. Included in the support is access to
HFS, sequential, PDS, PDSE, and VSAM data sets from Windows 3.11
(Windows for Workgroups), Windows 95, Windows 98, Windows NT
4.0, Windows 2000 Professional, and OS/2 workstations. Windows
workstation users can also exploit z/OS printer capabilities via the SMB
file/print server interface to the z/OS Infoprint Server feature.

For the software necessary to use the DFS or SMB file/print serving
support, as well as the other Distributed File Service functions, see
“Appendix B. Software Requirements for z/OS Elements and Features”
on page 201.

Prior to OS/390 R5, this element was called OpenEdition DCE DFS.
Encina Toolkit OS/390 R7 Type: base element, exclusive.
Executive
Encina Toolkit Executive provides a set of tools for developing client
components of distributed transactional applications. This element was
new in OS/390 R4.
EREP OS/390 R1 Type: base element, nonexclusive.

(EREP MVS V3R5, The Environmental Record Editing and Printing Program (EREP) edits
5658-260) and prints reports for the records placed in the error recording data set
(ERDS), helping IBM service representatives fix problems.
ESCON Director OS/390 R1 Type: base element, exclusive.
Support
ESCON Director Support enables the reporting of ESCON director
device errors to z/OS. This element was both an orderable feature of
MVS/ESA SP V5 and a base element of OS/390. It became exclusive
in OS/390 R10, when MVS/ESA SP V5 was no longer marketed.
FFST OS/390 R2 Type: base element, exclusive.

First Failure Support Technology (FFST) provides immediate

notification and first failure data capture for software events. FFST was
new in OS/390 R2. As of OS/390 R9, it is exclusive; the equivalent
stand-alone product, FFST/MVS V1R2, 5695-044, is no longer
marketed.
GDDM OS/390 R2 Type: base element, nonexclusive.

(GDDM/MVS V3R2, GDDM provides presentation services and device-driving capability. It

5695-167) includes PCLK and OS/2 Link and REXX code. Related optional
features are GDDM-Presentation Graphics Feature and GDDM-REXX.
Other GDDM-associated products (IVU, GKS, IMD) are not in z/OS,
but are separately orderable.

Chapter 1. Learning about z/OS 11

Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
GDDM-PGF OS/390 R2 Type: optional feature, nonexclusive, priced, can be dynamically
enabled.
(GDDM/PGF
V2R1.3, 5668-812) GDDM-Presentation Graphics Feature (PGF) is a set of programs for
creating presentation material in a variety of styles. This feature was
new in OS/390 R2.

This feature is related to the base element GDDM.

GDDM-REXX OS/390 R2 Type: optional feature, nonexclusive, priced, can be dynamically
enabled.
(GDDM-REXX/MVS
V3R2, 5664-336) GDDM-REXX is a productivity tool that enables programmers to
prototype GDDM applications and to create small routines and utility
programs quickly and easily.

This feature is related to the base element GDDM.

HCD OS/390 R9 Type: base element, exclusive.

Hardware Configuration Definition (HCD) defines both the operating

system configuration and the processor hardware configuration for a
system. A related optional feature is HCM.
HCM OS/390 R9 Type: optional feature, exclusive, priced, can be dynamically enabled.

Hardware Configuration Manager (HCM) is a PWS-based client/server

interface to the base element HCD. This feature was new in OS/390
R4.
HLASM OS/390 R10 Type: base element, nonexclusive.

(HLASM for MVS & High Level Assembler (HLASM) integrates almost all functions of past
VM & VSE V1R4, assemblers and provides extensions and improvements. A related
5696-234) optional feature is the HLASM Toolkit.
HLASM Toolkit OS/390 R10 Type: optional feature, nonexclusive, priced, can be dynamically
enabled.
(Toolkit feature of
HLASM for MVS & HLASM Toolkit provides tools to improve application development,
VM & VSE V1R4, debugging, and recovery. It is related to the base element HLASM.
5696-234)

12 z/OS V1R1.0 Planning for Installation

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
IBM HTTP Server OS/390 R10 Type: base element, exclusive.

IBM HTTP Server is z/OS’s Web server. It provides scalable, high

performance Web serving for critical e-business applications. It
supports Secure Sockets Layer (SSL) secure connections, dynamic
caching using the Fast Response Cache Accelerator, multiple IP
addresses, proxy authentication, and double-byte character set
characters.

Prior to OS/390 R4, this element was known as base element Internet
Connection Secure Server (ICSS) or Internet Connection Server (ICS).
In OS/390 R4, R5, and R6, this element was known as base element
Lotus Domino Go Webserver. In OS/390 R7 and R8, this element
became known as IBM HTTP Server and became a component of
base element WebSphere Application Server. In OS/390 R9, IBM HTTP
Server again became a base element (no longer a component of
WebSphere Application Server).

A related optional feature, IBM HTTP Server NA Secure, provides

increased security.

As of OS/390 R10, the HTTP Server CA utility is no longer available.

See Table 2 on page 20 for further information.
IBM HTTP Server OS/390 R10 Type: optional feature, exclusive, unpriced, cannot be dynamically
NA Secure enabled.

IBM HTTP Server NA Secure supports Secure Sockets Layer (SSL)

connections using 128-bit encryption. This feature is related to the base
element IBM HTTP Server.

Before OS/390 R4, this feature was called ICSS North America Secure.
As of OS/390 R4 it was rebranded to Lotus Domino Go Webserver
North America Secure. As of OS/390 R7 it received its current name.
ICKDSF OS/390 R1 Type: base element, nonexclusive.

(ICKDSF R16, The Device Support Facility (ICKDSF) enables you to perform functions
5655-257) needed for the installation and use of IBM DASD.
| ILM z/OS V1R1 Type: base element, exclusive.

| IBM License Manager (ILM) is a combination of license management

| tools that you use to manage licenses and check compliance with
| software terms and conditions. This gives you more direct control over
| your software licenses and their usage.

| ILM will be initially delivered on 30 March 2001 (as part of z/OS V1R1)
| for preproduction use, with Workload License Charges at full machine
| capacity. Customer production use of ILM, with Workload License
| Charges at less than full machine capacity, will be available when IBM
| completes full testing of ILM and you have applied the recommended
| z/OS service to make your system ILM production-ready. This testing
| by IBM is planned to be complete by the end of September 2001.
| Information about the service (PTFs) required to make ILM
| production-ready can be found at
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/.

| ILM is new in z/OS V1R1.

Chapter 1. Learning about z/OS 13

Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
Infoprint Server OS/390 R8 Type: optional feature, exclusive, priced, can be dynamically enabled.

Infoprint Server allows you to print files on z/OS printers from any
workstation that has TCP/IP access. This feature was named OS/390
Print Server when it first became part of OS/390 in R5. In OS/390 R8
its name was changed to OS/390 Infoprint Server. This feature consists
of the following components:
v IP PrintWay. This component has its roots in the IP PrintWay feature
of PSF/MVS V2R2 and the IP PrintWay/NetSpool feature of OS/390
R3.
v NetSpool. This component has its roots in the NetSpool feature of
PSF/MVS V2R2 and the IP PrintWay/NetSpool feature of OS/390
R3.
v Print Interface, new in OS/390 R5.
v Printer Inventory Manager, new in OS/390 R8.
v SNMP Subagent, new in OS/390 R8.
v Transform Manager, new in OS/390 R8.
v Batch Print Capability, new in OS/390 R8.

IBM recommends that you use the Infoprint Server feature rather than
the Communications Server NPF feature because the IP PrintWay
component of Infoprint Server provides improved function, capacity,
performance, and usability over Communications Server NPF. In
addition, IBM recommends that you use Infoprint Server instead of the
IP PrintWay and NetSpool features of PSF V3.
ISPF OS/390 R10 Type: base element, exclusive.

ISPF is a full-screen editor and dialog manager. As of OS/390 R5,

ISPF became exclusive.

As of OS/390 R8, the VisualAge for ISPF function was removed from
OS/390.
JES2 OS/390 R10 Type: base element, exclusive.

JES2 accepts the submission of work for the BCP. JES2 exercises
independent control over its job processing functions, whereas JES3
exercises centralized control.

Prior levels of JES2 can be used with z/OS V1R1. See “Allowable
JES-BCP Combinations” on page 65.
JES3 OS/390 R10 Type: optional feature, exclusive, priced, can be dynamically enabled.

JES3 accepts the submission of work for the BCP. JES3 exercises
centralized control over its job processing functions, whereas JES2
exercises independent control.

Prior levels of JES3 can be used with z/OS V1R1. See “Allowable
JES-BCP Combinations” on page 65.

14 z/OS V1R1.0 Planning for Installation

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
LAN Server OS/390 R5 Type: base element, exclusive.

LAN Server enables local area network (LAN) workstation users to

store and share data and applications in a central location on a
System/390, which allows the large storage capacity of a System/390
to relieve the capacity constraints of workstation-based servers. This
element can be used as a file-sharing system for OS/2 LAN Server
networks, a Network File System file-serving protocol, or both. Support
for Network File System file-serving protocols is provided either through
TCP/IP or through Network File System front-end processors.

Important: LAN Server is being removed from z/OS because the

prerequisite OS/2 software is no longer available. OS/390 R9 was the
last release to include both the workstation (on diskettes) and host
components. OS/390 R10 and z/OS V1R1 have only the host
component. After z/OS V1R1, neither component will be available. For
customers who want to migrate to z/OS V1R1 prior to migrating off
LAN Server, the OS/2 Front End Processor configurations from
previous releases of LAN Server are still supported on z/OS V1R1.
See S/390 File and Print Serving, SG24-5330, for alternative solutions
and migration guidance.
Language OS/390 R10 Type: base element, exclusive.
Environment
Language Environment provides the run-time environment for programs
generated with:
v OS/390 C/C++
v C/C++ for MVS/ESA
v AD/Cycle C/370
v VisualAge for Java, Enterprise Edition for OS/390
v COBOL for OS/390 & VM
v COBOL for MVS & VM
v AD/Cycle COBOL/370
v VisualAge PL/I for OS/390
v PL/I for MVS & VM
v AD/Cycle PL/I for MVS & VM
v VS FORTRAN and FORTRAN IV (in compatibility mode)

Inclusion of Language Environment as a base element in z/OS does

not replace the need for separate compilers.

As of OS/390 R9, Language Environment includes the function

formerly in optional feature Language Environment Data Decryption.
The optional feature was removed from OS/390. The function provides,
for certain C functions, decryption of data using the data encryption
standard (DES) algorithm.
LANRES OS/390 R5 Type: base element, exclusive.

LANRES integrates NetWare LANs and System/390 environments.

Included with LANRES are diskettes that you use to install LANRES
code on the Novell NetWare Server.

| IBM intends to remove LANRES from z/OS. V1R2 will be the last
| release of z/OS that contains LANRES. For migration information, see
| the white paper at http://www.ibm.com/servers/eserver/
| zseries/library/whitepapers/gm130035.html.

Chapter 1. Learning about z/OS 15

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
MICR/OCR OS/390 R1 Type: base element, exclusive.

This element provides the device support code for various magnetic
and optical devices. This element was both an orderable feature of
MVS/ESA SP V5 and a base element of OS/390. It became exclusive
in OS/390 R10, when MVS/ESA SP V5 was no longer marketed.
| msys for Setup z/OS V1R1 Type: base element, exclusive.

| Managed System Infrastructure for Setup (msys for Setup) offers a new
| approach for installing and configuring z/OS and products that run on
| z/OS. The configuration process is driven by a graphical user interface
| that greatly facilitates the definition of customization parameters.
| Updates are under the control of the msys administrator and are made
| directly to the system. In z/OS V1R1, you can use msys for Setup to
| easily set up a Parallel Sysplex resource sharing environment.

| This element is new in z/OS V1R1.

Network File OS/390 R6 Type: base element, exclusive.
System
Network File System acts as a file server to workstations, personal
computers, or other authorized systems in a TCP/IP network. In
OS/390 R2 it was enhanced and its function was equivalent to the
stand-alone product DFSMS/MVS V1R3 Network File System. In
OS/390 R6 it became exclusive, function was added, and
“DFSMS/MVS” was dropped from the beginning of its name.

This element consists of a client (Network File System Client) and a

server (Network File System Server).

Network File System Server and LAN Server cannot work

simultaneously on the same processor to provide Network File System
services through TCP/IP. At setup or run time, you must choose which
function to use.

This element supports Berkeley sockets, and not TCP/IP Sockets.

As of OS/390 R4, this element is always enabled, even when the

alternate base configuration is ordered.
OCSF Security Level OS/390 R10 Type: optional feature, exclusive, unpriced, cannot be dynamically
3 enabled.

OCSF Security Level 3, in conjunction with base element

Cryptographic Services, provides 56-bit-and-greater software
cryptographic services, a data library service provider, certificate library
service providers, trust policy service providers, and hardware
cryptographic services.

This feature was new in OS/390 R7.

The availability of this feature outside the U.S. is subject to U.S. export
regulations.

16 z/OS V1R1.0 Planning for Installation

Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
OSA/SF OS/390 R8 Type: base element, nonexclusive.

(OSA/SF for OS/390 Open Systems Adapter/Support Facility (OSA/SF) provides a

V2R1, 5655-B57) user-friendly interface for monitoring and controlling the S/390 Open
Systems Adapter feature, which provides S/390 network connectivity
directly to local area networks (LANs) and wide area networks (WANs)
that support IP and SNA protocols. OS/390 R8 OSA/SF (as well as
OSA/SF V2) introduced support for a new Windows-based GUI, as well
as support for the new OSA-Express functions, such as QDIO mode.
OS/390 R8 and later OSA/SF (and OSA/SF V2) continue to support
the OSA-2 function.

OSA-Express supports Gigabit Ethernet Connection, ATM, and Fast

Ethernet connections. OSA-2 supports Ethernet, Fast Ethernet,
Token-Ring, FDDI, and ATM connections. Resource availability
improvements include multiple IP address and default IP address
support for each path through the OSA function, as well as support for
primary and secondary routing paths when multiple instances of
TCP/IP are used.

As of OS/390 R8, OSA-1 function was no longer supported in OS/390.

(Likewise, the OSA-1 feature, which is in OSA/SF V1, is not in OSA/SF
V2.)
RMF OS/390 R10 Type: optional feature, exclusive, priced, can be dynamically enabled.

Resource Measurement Facility (RMF) gathers data about z/OS

resource usage and provides reports at any system in a sysplex.
SDSF OS/390 R10 Type: optional feature, exclusive, priced, can be dynamically enabled.

System Display and Search Facility (SDSF) provides you with

information to monitor, manage, and control your z/OS system.

See “Using z/OS V1R1 SDSF with Your Existing JES2” on page 68 to
see how to use the current SDSF with your existing JES2.

Chapter 1. Learning about z/OS 17

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
SecureWay Security OS/390 R10 (but see Type: optional feature, exclusive, priced, can be dynamically enabled.
Server description)
SecureWay Security Server for OS/390 lets you control access to
protected resources. SecureWay Security Server consists of the
following components, most of which last changed in OS/390 R10:
v DCE Security Server, last changed in OS/390 R9. This component is
at the OSF DCE 1.2.2 level. In OS/390 R5, this component was
upgraded to support Kerberos V5.1.
v Firewall Technologies, part of the OS/390 R4 Firewall Technologies
kit, integrated into OS/390 R5, and last changed in OS/390 R10.
v LDAP Server, new in OS/390 R5 and last changed in OS/390 R10.
In OS/390 R8, LDAP Client was removed from base element DCE
Base Services and merged into LDAP Server. Also as of OS/390 R8,
LDAP Server is licensed with the base operating system and can be
used without ordering or enabling SecureWay Security Server.
v Network Authentication and Privacy Service, new in OS/390 R10.
Network Authentication and Privacy Service is licensed with the base
operating system and can be used without ordering or enabling
SecureWay Security Server.
v Open Cryptographic Enhanced Plug-ins (OCEP), new in OS/390 R8
and last changed in OS/390 R10.
v RACF, last changed in OS/390 R10.

In OS/390 R9, the word “SecureWay” was added to this feature’s name
to strengthen its identification as part of the SecureWay family of
e-business software.
SMP/E OS/390 R7 Type: base element, exclusive.

SMP/E is a tool for installing and maintaining software, and for

managing the inventory of software that has been installed.

The Planning and Migration Assistant, a component of SMP/E, can

help you maintain, plan for, and order new releases of z/OS and other
products. It provides reports that use IBM-supplied data, your SMP/E
consolidated software inventory (CSI) data set, and a CustomPac
inventory file. The Planning and Migration Assistant Web site is
http://www.ibm.com/s390/pma/.
SOMobjects ADE OS/390 R4 Type: optional feature, exclusive, priced, can be dynamically enabled.

SOMobjects is a technology that allows applications written in different

programming languages to use the same object-oriented class libraries.

SOMobjects Application Development Environment (ADE) provides a

SOM compiler and source code for the SOM kernel (root) classes,
Interface Repository Framework, and emitter Framework.

| IBM plans to remove SOMobjects ADE from z/OS as of V1R2. V1R1

| will be the last release of z/OS that contains SOMobjects ADE. For
| more details, see “List of Elements, Features, and Functions to Be
| Removed from z/OS” on page 23.

18 z/OS V1R1.0 Planning for Installation

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
SOMobjects RTL OS/390 R4 Type: base element, exclusive.

SOMobjects Runtime Library (RTL) is a set of functions for creating

objects and invoking methods on them.

| IBM plans to remove SOMobjects RTL from z/OS as of V1R2. V1R1

| will be the last release of z/OS that contains SOMobjects RTL. For
| more details, see “List of Elements, Features, and Functions to Be
| Removed from z/OS” on page 23.
System SSL Security OS/390 R10 Type: optional feature, exclusive, unpriced, cannot be dynamically
Level 3 enabled.

System Secure Sockets Layer (SSL) Security Level 3 provides privacy

between a client and a server through use of the SSL protocol and up
to 168-bit TDES user data cryptography.

The availability of this feature outside the U.S. is subject to U.S. export
regulations.

This feature was new to OS/390 in R7 and was then named System
SSL Crypto. In OS/390 R8 it received its current name.
Text Search OS/390 R9 Type: base element, exclusive.

Text Search is a database and Web search engine. It has two

components:
v IBM Text Search Engine is a database search engine that is also
used in several other IBM products, such as Intelligent Miner for Text
and DB2 Text Extenders.
v NetQuestion Solution extends the IBM Text Search Engine into a
search engine for z/OS Web servers.

Text Search, as an integral part (base element) of OS/390, was new in

R8. Text Search is also available as a Web download for OS/390 R7
and earlier releases. OS/390 R8 and later Text Search is functionally
enhanced compared to the Web download versions.

Text Search includes the function in the former OS/390 R7 base

element NetQuestion. NetQuestion was new to OS/390 in R4.
TIOC OS/390 R1 Type: base element, exclusive.

TIOC allows console services and TSO/E to communicate with the

terminal hardware. This element was both a component of MVS/ESA
SP V5 and a base element of OS/390. It became exclusive in OS/390
R10, when MVS/ESA SP V5 was no longer marketed.
Tivoli Management OS/390 R9 Type: base element, nonexclusive.
Framework
(Tivoli Management Tivoli Management Framework enables z/OS to be managed (via an
Framework V3R6.1 agent) by the Tivoli framework-based applications that support z/OS.
for OS/390, This element was new in OS/390 R7.
5697-D10)
| IBM plans to remove Tivoli Management Framework from z/OS as of
| V1R2. V1R1 will be the last release of z/OS that contains Tivoli
| Management Framework. Tivoli Management Framework will only be
| available as a stand-alone product, which will enable earlier access to
| the most current level of its function in support of the latest level of
| Tivoli management applications.

Chapter 1. Learning about z/OS 19

 Table 1. Base elements and optional features in z/OS V1R1 (continued)
Name Function level Type and description
TSO/E OS/390 R4 Type: base element, exclusive.

Time Sharing Option/Extensions (TSO/E) provides an interactive

terminal interface. As in prior releases of TSO/E, this element includes
CLISTs and REXX, but does not include a REXX compiler.
z/OS UNIX System OS/390 R10 (but see Type: base element, exclusive.
Services description)
z/OS UNIX System Services (z/OS UNIX) provides the standard
command interface familiar to interactive UNIX users. This element
contains the following components:
v Application Services, last changed in OS/390 R10. This component
includes the Shell, Utilities, Debugger, and Parallel Environment.
v Connection Manager, last changed in OS/390 R7.
v Process Manager, last changed in OS/390 R7.
v Integrated Call Level Interface (ICLI), last changed in OS/390 R10.

This element was known as OpenEdition in the past.

3270 PC File OS/390 R2 Type: base element, nonexclusive.
Transfer Program
(3270 PC File 3270 PC File Transfer Program transfers files from the host to the
Transfer Program workstation for offline data manipulation, updating, or correction or for
V1R1.1, 5665-311) the transfer and storage of local data in the host system. This element
was new in OS/390 R2.

List of Elements, Features, and Functions Removed from OS/390

A number of elements, features, and major functions have been removed from
OS/390 over the course of its life, and are not in z/OS. See Table 2.
Table 2. Elements, features, and major functions removed from OS/390
Name of element, feature, or major function Last release shipping it, and comments
Application Enabling Technology (AET) base element OS/390 R7
C/C++ IBM Open Class Library base element’s C/C++ OS/390 R9
SOM Enable Class Library
C/C++ with Debug Tool and C/C++ without Debug Tool OS/390 R3
features’ C/C++ Database Access Class Library (DACL)
function
Communications Server base element’s 3172 Offload OS/390 R4
function
Communications Server base element’s High Speed UDP OS/390 R9. Instead, use the base TCP/IP stack to obtain
facility of the IP Services component equivalent function and performance.
| Communications Server base element’s Host On-Demand OS/390 R7. Instead, consider purchasing the stand-alone
| component product SecureWay Host On-Demand V4 (part number
| 41L1766, 41L1767, 41L1768, 0704820, 0704824, or
| 0704825). It contains more function than the former Host
| On-Demand component.
Communications Server base element’s Network Station OS/390 R4. Instead, consider purchasing the stand-alone
Client and Network Station Manager functions product Network Station Manager (5648-C05).
DCE User Data Privacy CDMF feature OS/390 R8. Now part of the DCE Base Services base
element.
DCE User Data Privacy DES/CDMF feature OS/390 R8. Now part of the DCE Base Services base
element.

20 z/OS V1R1.0 Planning for Installation

Table 2. Elements, features, and major functions removed from OS/390 (continued)
Name of element, feature, or major function Last release shipping it, and comments
IBM HTTP Server base element’s HTTP Server OS/390 R9. The HTTP Server Certificate Authority (CA)
Certificate Authority utility utility enabled an installation to act as a certificate
authority. This utility was intended to satisfy certificate
requests within an intranet and was not intended for
Internet commerce. In its place, you can use functions
provided by the z/OS System Secure Sockets Layer
(SSL) utility gskkyman or the RACF RACDCERT
command to set up your own certificate authority, or you
can purchase a certificate authority software product. For
more information, see z/OS HTTP Server Planning,
Installing, and Using, z/OS System Secure Sockets Layer
Programming, and z/OS SecureWay Security Server
RACF Command Language Reference.
IBM HTTP Server Export Secure feature OS/390 R9. No longer needed. The equivalent level of
security is provided by the Cryptographic Services base
element.
IBM HTTP Server France Secure feature OS/390 R9. No longer needed due to change in French
import regulations. The equivalent level of security is
provided by the Cryptographic Services base element.
LAN Server base element’s workstation code OS/390 R9. LAN Server is being removed from z/OS
because the prerequisite OS/2 software is no longer
available. OS/390 R9 was the last release to include both
the workstation (on diskettes) and host components.
OS/390 R10 and z/OS V1R1 have only the host
component. After z/OS V1R1, neither component will be
available. For customers who want to migrate to z/OS
V1R1 prior to migrating off LAN Server, the OS/2 Front
End Processor configurations from previous releases of
LAN Server are still supported on z/OS V1R1. See S/390
File and Print Serving, SG24-5330, for alternative
solutions and migration guidance.
Language Environment Data Decryption feature OS/390 R8. Now part of the Language Environment base
element.
OCSF France feature OS/390 R8. Now part of the Cryptographic Services base
element.
OCSF Security Level 1 feature OS/390 R8. Now part of the Cryptographic Services base
element.
OCSF Security Level 2 feature OS/390 R8. Now part of the Cryptographic Services base
element.
OSA-1 function of the OSA/SF base element OS/390 R7
Security Server LDAP Server DES feature OS/390 R7. Instead, use the System SSL Security Level
3 feature.

Chapter 1. Learning about z/OS 21

 Table 2. Elements, features, and major functions removed from OS/390 (continued)
Name of element, feature, or major function Last release shipping it, and comments
Softcopy Print base element (including DBCS Softcopy OS/390 R9. The purpose of the Softcopy Print element
Print) was to print BookManager books (or topics) on AFP
printers. Migration aids are:
| v Sections of BookManager books (served by
| BookServer) can be printed from the z/OS Internet
| Library (http://www.ibm.com/servers/eserver/
| zseries/zos/bkserv/) using the print function of your
| browser.
| v PDF files of the z/OS books are available for printing.
| You can obtain the PDFs from the z/OS Internet
| Library or from the z/OS Collection CD-ROM or DVD.
v For customers who wish to continue to use the
Softcopy Print function to print BookManager books on
AFP printers, you need to have the following products
installed:
For single-byte character set printing (this includes
English):
– AFP Font Collection V2R1 (5648-B33)
– BookMaster V1R4 (5688-015)
– DCF V1R4 (5748-XX9)
– PSF V3R1 for OS/390 (5655-B17) or later

For double-byte character set (DBCS) printing:

– All of the requirements for single-byte printing
– The AFP DBCS fonts for your language
– The DBCS Print Utility, formerly part of Softcopy
| Print but now part of BookManager READ via PTF
| UQ99324.
– BookMaster PTF UQ04721 for the DBCS profiles
Note that as of OS/390 R10, a subset of the AFP Font
Collection is no longer shipped as part of the base
operating system. If you were relying on the use of these
fonts for AFP printing, you might need to purchase the
AFP Font Collection (5648-B33).
SOMobjects Service Classes base element OS/390 R3
System SSL Security Level 2 feature OS/390 R9. Now part of the Cryptographic Services base
element.
SystemView for MVS Base base element OS/390 R6
TCP/IP Offload feature OS/390 R4. No longer needed due to performance
enhancements.
VisualAge for ISPF function of the ISPF base element OS/390 R7. ISPF panel source created with VisualAge for
ISPF can continue to be used. To maintain the source,
use the ISPF PDF editor.
VisualLift ADE feature OS/390 R9. The equivalent stand-alone product,
VisualLift for MVS, VSE, & VM V1R1.2 (5748-109), is
withdrawn from marketing.
VisualLift RTE base element OS/390 R9. The equivalent stand-alone product,
VisualLift for MVS, VSE, & VM V1R1.2 (5748-109), is
withdrawn from marketing.

22 z/OS V1R1.0 Planning for Installation

 Table 2. Elements, features, and major functions removed from OS/390 (continued)
Name of element, feature, or major function Last release shipping it, and comments
WebSphere Application Server base element OS/390 R9. Instead, use the stand-alone product
WebSphere Application Server for OS/390 V3
(5655-A98).
WebSphere Application Server base element, Japanese OS/390 R8
version

| List of Elements, Features, and Functions to Be Removed from z/OS

| This section lists items that IBM has announced will be removed from z/OS in the
| future. You are encouraged to consider these removals when making your plans for
| system upgrades. These statements represent IBM’s current intentions. IBM
| development plans are subject to change or withdrawal without further notice.

| The following will be in z/OS for the last time in V1R1 (that is, will be withdrawn
| with V1R2):
| v The base element LAN Server is being removed from z/OS because the
| prerequisite OS/2 software is no longer available. OS/390 R9 was the last
| release to include both the workstation (on diskettes) and host components.
| OS/390 R10 and z/OS V1R1 have only the host component. After z/OS V1R1,
| neither component will be available. For customers who want to migrate to z/OS
| V1R1 prior to migrating off LAN Server, the OS/2 Front End Processor
| configurations from previous releases of LAN Server are still supported on z/OS
| V1R1. See S/390 File and Print Serving, SG24-5330, for alternative solutions and
| migration guidance.
| v Version 4 Kerberos support will be withdrawn from two Communications Server
| features in favor of the more current Kerberos V5 support already provided as a
| part of the z/OS SecureWay Security Server feature. As a result, the features
| Communications Server Security Level 1 and Communications Server
| Security Level 2 will be removed from z/OS. You should modify any applications
| that currently use the Kerberos Version 4 support provided by these features to
| use the Kerberos Version 5 support provided by the z/OS SecureWay Security
| Server feature.
| v Library Management Facility (LMF) services such as LMPROM, LMHIER,
| LMREVIEW, LMACT, and LMDEACT are being withdrawn from base element
| ISPF to take advantage of better and more modern library function in option 10
| SCLM.
| v The C/C++ compilers will no longer support the GENPCH and USEPCH
| compiler options for Pre-Compiled Header (PCH) files. GENPCH and USEPCH
| served as a tactical initiative to reduce compile times. IBM will concentrate
| instead on improving compile times by building the compilers with successively
| higher levels of optimization from release to release, exploiting the ongoing
| optimization improvements made in the compilers.
| v Optional feature RMF provides several options for viewing real-time performance
| data. The RMF local display session requires a BTAM connection. Since IBM
| has announced the end of service for BTAM, this RMF display option will be
| withdrawn. You will continue to have access to Monitor II information without an
| active TSO/TCAS subsystem by means of RMF Client/Server Enabling (RMFCS).
| v Tivoli Management Framework will no longer be included as a base element of
| z/OS. It will only be available as a stand-alone product, which will enable earlier
| access to the most current level of its function in support of the latest level of
| Tivoli management applications.

Chapter 1. Learning about z/OS 23

| v Object-oriented technology has come a long way since IBM’s introduction of
| SOMobjects in June of 1995. It is now the cornerstone of e-business.
| SOMobjects provided an introduction to object-oriented technology and a way to
| build applications that took advantage of everything the emerging technology had
| to offer, coupled with the advantages of the S/390 platform. As the technology
| advanced, IBM incorporated those advances into a new line of products called
| WebSphere, specifically aimed at the e-business environment and its
| requirements.
| Given that product direction, IBM plans to remove SOMobjects ADE and
| SOMobjects RTL from z/OS. However, because there continues to be value in
| the ability to build COBOL object-oriented applications, and the COBOL
| object-oriented technology is based on SOMobjects, IBM plans to incorporate the
| necessary subset of SOMobjects ADE into the IBM COBOL for OS/390 & VM
| compiler product. The subset of SOMobjects RTL needed for object-oriented
| COBOL applications will be incorporated into the Language Environment base
| element. This will allow COBOL customers to continue to maintain, enhance, and
| execute object-oriented COBOL applications.

| The following will be in z/OS for the last time in V1R2:

| v The base element LANRES. For migration information, see the white paper at
| http://www.ibm.com/servers/eserver/zseries/library/whitepapers/gm130035.html.
| v Workload manager (WLM) compatibility mode. WLM in goal mode continues to
| grow in its role and importance. Each new release of the operating system and
| supporting subsystems brings further exploitation of WLM goal mode for
| improvements and efficiencies in system performance and workload balancing.
| Goal mode is required to get the most benefit from the new Intelligent Resource
| Director (IRD) functions in z/OS. Consequently, goal mode will be the only
| supported mode after z/OS V1R2.

| Methods of Installing z/OS

Because the base elements and optional features of z/OS are integrated into a
single package with compatible service levels, you must install, with few
exceptions, the entire z/OS product. See “Choosing the z/OS Base and Optional
Features” on page 59 for details about this policy.

You can install z/OS using one of several IBM packages. Two of these packages
are available at no additional charge when you license z/OS:
v ServerPac is a software delivery package consisting of products and service for
which IBM has performed the SMP/E installation steps and some of the
post-SMP/E installation steps. To install the package on your system and
complete the installation of the software it includes, you use the CustomPac
Installation Dialog.
v CBPDO (Custom-Built Product Delivery Option) is a software delivery package
consisting of uninstalled products and unintegrated service. You must use SMP/E
to install the individual z/OS elements and features, and their service, before you
can IPL (initial program load).
| For those migrating from OS/390 R10, a CBPDO-installable software delivery
| package called z/OS V1R1 Upgrade Package for OS/390 V2R10 is provided. It
| consists of two new base elements (ILM and msys for Setup) and one updated
| base element (BCP). It provides a quick and easy upgrade to the first release of
| z/OS.

Other installation packages and offerings are available for an additional fee. For
example:

24 z/OS V1R1.0 Planning for Installation

 v SystemPac is a software delivery package consisting of IBM and independent
software vendor (ISV) products and service. It is tailored to your specifications,
which you supply during order entry. SystemPac comes in two varieties: a full
volume dump format (you install using volume restore) and a dump-by-data-set
format (you install using the CustomPac Installation Dialog).

See “Chapter 2. Choosing the Software Installation Method” on page 37 for details
about all the methods of installing z/OS.

National Languages in Which z/OS Is Available

z/OS is provided in U.S. English. In addition, 16 other languages are supported.
However, not all elements and features are available in each of the 16 languages.
Table 3 shows the 16 languages and lists which elements and features are
available in each.

When you order z/OS, you receive it in the following languages:

v U.S. English
v Fourteen national languages for base element BookManager BookServer (U.S.
English and the 13 languages listed in Table 3)
v Fourteen national languages for base element Text Search (U.S. English and the
13 languages listed in Table 3)
If you want an additional language, you have to specify the national language
version (NLV) feature number in your order.

If you order the z/OS base in a non-English language, you get all priced features
(which support dynamic enablement) in English and any priced features that are
available in that non-English language. If you order a priced feature in a
non-English language, you get it in that language and in English.

The enablement setting is based on whether an element or feature was ordered in

any language.
Table 3. National languages supported (in addition to U.S. English) and the elements and
features available in each language
National language Base elements Priced optional features
Brazilian Portuguese v BookManager BookServer v BookManager BUILD
(See note.)
v BookManager READ
v GDDM
v Text Search (See note.)
Canadian French v BookManager READ v BookManager BUILD
v GDDM
Danish v BookManager BookServer
(See note.)
v BookManager READ
v GDDM
v Text Search (See note.)
Dutch v BookManager BookServer
(See note.)
v BookManager READ

Chapter 1. Learning about z/OS 25

 Table 3. National languages supported (in addition to U.S. English) and the elements and
features available in each language (continued)
National language Base elements Priced optional features
French v BookManager BookServer v BookManager BUILD
(See note.)
v BookManager READ
v GDDM
v Text Search (See note.)
German v BookManager BookServer v BookManager BUILD
(See note.)
v BookManager READ
v GDDM
v ISPF
v Text Search (See note.)
v TSO/E
Italian v BookManager BookServer
(See note.)
v BookManager READ
v GDDM
v Text Search (See note.)
Japanese v BCP v C/C++ with Debug Tool
v BookManager BookServer v C/C++ without Debug Tool
(DBCS) (See note.) v DFSORT
v C/C++ IBM Open Class v Infoprint Server
Library v RMF
v DCE Application Support v SDSF
v DCE Base Services v SecureWay Security Server
v DFSMSdfp v SOMobjects ADE
v DFSMSdss
v DFSMShsm
v DFSMSrmm
v Distributed File Service
v Encina Toolkit Executive
v GDDM
v HCD
v IBM HTTP Server
v ICKDSF
v ISPF
v JES2
v LAN Server
v Language Environment
v LANRES
v SMP/E
v SOMobjects RTL
v SSL Base component of
Cryptographic Services
v Text Search (See note.)
v TSO/E
v z/OS UNIX System Services
Korean v BookManager BookServer
(DBCS) (See note.)
v GDDM
v Text Search (See note.)
Norwegian v BookManager BookServer
(See note.)
v GDDM
v Text Search (See note.)

26 z/OS V1R1.0 Planning for Installation

 Table 3. National languages supported (in addition to U.S. English) and the elements and
features available in each language (continued)
National language Base elements Priced optional features
Simplified Chinese v BookManager BookServer
(DBCS) (See note.)
v GDDM
v z/OS UNIX System Services
kernel in the BCP
v Text Search (See note.)
v TSO/E
v z/OS UNIX System Services
Spanish v BookManager BookServer v BookManager BUILD
(See note.) v Infoprint Server
v BookManager READ
v GDDM
v Text Search (See note.)
Swedish v BookManager BookServer
(See note.)
v GDDM
v Text Search (See note.)
Swiss German v ISPF
Traditional Chinese v BookManager BookServer
(DBCS) (See note.)
v GDDM
v Text Search (See note.)
Uppercase English v ISPF
v Text Search (See note.)
Note: All BookManager BookServer and Text Search national languages are provided with
the z/OS base license and therefore do not have to be separately ordered.

Integration Testing by IBM

Each release of z/OS undergoes integration testing by a team of IBM testers and
system programmers. The test system simulates a customer production Parallel
Sysplex environment running z/OS and many other related software products such
as DB2, IMS, and CICS. The team migrates to each new release of z/OS, puts the
system into production, and then verifies that all products work together.

The team produces a quarterly report containing test results and advice for
customers. The report is entitled z/OS Parallel Sysplex Test Report and will be
available from the z/OS Integration Test Web site. This Web site will include
illustrations of the team’s hardware, software, networking, and application
enablement configurations.

The team follows a process that includes simulating the workload stress levels,
transaction rates, and lock contention rates that customers might experience. They
stress many of the same areas of the system that customers stress. In their report
they include detailed descriptions of their hardware, software, networking, and
application enablement configurations, as well as the key operational, performance,
and availability characteristics of their Parallel Sysplex environment. They provide
recommended recovery procedures, recommended service levels, and a variety of
hints and tips distilled from their own experiences. They let you know about the
mistakes they make so you can avoid those mistakes.

Chapter 1. Learning about z/OS 27

 Service is also tested in this environment. The test system is brought up to the
minimum z/OS service level that will be shipped with ServerPac orders. In general,
this is the PUT level that was available two months prior to general availability (GA),
plus Recommended Service Upgrade (RSU) packages that might also have
become available. If testing identifies a need for corrective service, program
temporary fixes (PTFs) are added to the system and tested. Each integration-tested
| PTF is identified with a SOURCEID of ZOSV1Rn (where n is the release number).

Service
This topic describes IBM’s service policy for z/OS, the level of service that is
provided with your order, what PSP information is, the preventive maintenance that
you should perform after installing z/OS, and how preventive and corrective service
are distributed.

Service Policy
IBM’s current policy is to provide maintenance for each release of z/OS for three
years following its general availability (GA) date. See Table 4 for the end-of-service
dates for z/OS V1R1 and all OS/390 releases.
Notes:
1. IBM intends to provide at least twelve months notice prior to the withdrawal of
service for any version or release of z/OS. For the versions and releases
marked with an asterisk (*) in the table, notice has already been given.
2. Service on the last release of a version might be extended beyond the intended
three-year period.
Table 4. Expiration dates for z/OS and OS/390 service support. End-of-service dates with an
asterisk (*) have already been announced. Other end-of-service dates are anticipated based
on the three-year service policy.
General availability (GA)
Version and release date End-of-service (EOS) date
OS/390 V1R1 29 March 1996 31 January 2001*
OS/390 V1R2 27 September 1996 31 January 2001*
OS/390 V1R3 28 March 1997 31 March 2001*
OS/390 V2R4 26 September 1997 31 March 2001*
OS/390 V2R5 27 March 1998 31 March 2001*
| OS/390 V2R6 25 September 1998 31 March 2002*
OS/390 V2R7 26 March 1999 March 2002
OS/390 V2R8 24 September 1999 September 2002
OS/390 V2R9 31 March 2000 March 2003
OS/390 V2R10 29 September 2000 September 2003
| z/OS V1R1 30 March 2001 March 2004

Program temporary fix (PTF) distributions, including Recommended Service

Upgrades (RSUs), will continue to be available monthly while a release is current.
RSU integration testing for a release will be performed for five quarters after the
general availability date for that release.

Note that there is a difference between how long a release is serviced and how
long IBM will ensure coexistence within a multisystem configuration. To provide you

28 z/OS V1R1.0 Planning for Installation

 with release migration flexibility, IBM allows four consecutive releases of z/OS to
coexist in a multisystem configuration. See “Coexistence Policy” on page 72 for
details.

ServerPac Service Level

For ServerPac orders, service is integrated with product code according to the
following timeline:
v All products in your ServerPac will incorporate the PTFs contained in the
Extended Service Offering (ESO) packages that are available approximately two
months before the z/OS release becomes generally available.
v All products will incorporate high impact or pervasive (HIPER) and PTF-in-error
(PE) fixes that are available approximately one week before your order is built.
v All z/OS elements and features will incorporate additional service that has been
| through z/OS integration testing (SOURCEID ZOSV1Rn, where n is the release
number).
v On a monthly basis, ServerPac integrates the RSU PTFs that were available
approximately two months before your order was built.

ServerPac: Installing Your Order, which comes with your order, specifies the
integrated service level applicable to your order.

Your ServerPac order will also contain a service tape containing unintegrated
service.

CBPDO Service Level

For CBPDO orders, service is not integrated. You must receive and apply the
service during the installation process.

The following service is shipped with default CBPDO orders:

v Service for all products, elements, and features that you ordered.
v Service for all products previously ordered with the same system release
identifier (SREL), as reflected in the customer profile for the customer number
used when the order was placed. The starting service level is determined in one
| of the following ways:
| – If you specify a starting service level when ordering CBPDO, you will receive
| all the service from that level to the current level.
| – If you do not specify a starting service level, and you have previously ordered
| the same CBPDO SREL, you will receive all the service following the ending
| service level of your previous CBPDO order for the same SREL.
| – If you do not specify a starting service level, and your previous order is more
| than two years old, or if you are ordering a CBPDO SREL for the first time,
| the starting service level will default to the lowest valid level available at the
| time your order is placed.

As of September 2000 you have new options that allow you to customize the
service provided in your order. See “Limiting the Amount of CBPDO Service” on
page 33 for details.

The Memo to Users Extension that comes with CBPDO orders describes the
SOURCEIDs for service delivered on the CBPDO tape. For example,
| integration-tested PTFs have a SOURCEID of ZOSV1R1 for z/OS V1R1. z/OS
V1R1.0 Program Directory describes the SMP/E SOURCEIDs to be used to install
z/OS.

Chapter 1. Learning about z/OS 29

 SystemPac Service Level
For SystemPac orders, service is integrated with product code according to the
following timeline:
v All products in your SystemPac order will incorporate the PTFs contained in the
Extended Service Offering (ESO) packages that are available approximately one
month before the z/OS release becomes generally available.
v All products will incorporate high impact or pervasive (HIPER) and PTF-in-error
(PE) fixes that are available approximately one week before your order is built.
v All z/OS elements and features will incorporate additional service that has been
| through z/OS integration testing (SOURCEID ZOSV1Rn, where n is the release
number).
v On a monthly basis, SystemPac integrates the RSU PTFs that were available
approximately one month before your order was built.
v The service and maintenance incorporated in independent software vendor (ISV)
products depends on when the order is manufactured. The service and
maintenance can range from current to approximately two months old. Check
with your ISV to ensure that you have the most current levels of service
available.

Your SystemPac order will also contain a service tape containing unintegrated
service (applicable to the products in your order).

PSP Information
z/OS and most products that run on it provide files containing information that
became available after the product books were printed. Kept on IBM’s RETAIN
system and also available using IBMLink, these files are called preventive service
planning (PSP) “buckets”, or just “PSPs”. These terms were chosen when PSP
buckets contained only APAR- and PTF-related information, but over time
customers asked for a more general repository of important installation-related
information, and the role of the PSP bucket has grown.

PSP buckets are identified by an upgrade identifier, and specific parts of them are
called subsets. Each upgrade contains information about a product. Subsets contain
information about specific parts of a product. For example, the z/OS PSP bucket
has subsets for the BCP, JES2, ServerPac, and others. For software upgrades
other than SystemPac, refer to z/OS V1R1.0 Program Directory. For SystemPac,
the upgrade is CUSTOMPAC and the subsets are SYSPAC/FVD (for full volume
dump format) and SYSPAC/DBD (for dump-by-data-set format). For hardware
upgrades, refer to “PSP Hardware Upgrade Identifiers” on page 63.

At the beginning of each PSP bucket is a change index. For each subset, the
change index identifies the date of the latest entries in each section. You can
quickly determine whether there are new entries you need to read by checking the
change index.

Each subset is broken into five sections, numbered 1 through 5:

Section 1
Installation Information. This section contains any changes to installation
procedures or information about additional requisite PTFs.
Section 2
This section contains any major changes to product publications.

30 z/OS V1R1.0 Planning for Installation

 Section 3
General Section. This section contains important information that does not
fit in another section.
Section 4
Service Recommendations. The original purpose of the PSP bucket was to
provide this information, which includes a list of HIPER APARs and their
fixes, as well as other important service-related information.
Section 5
Cross-Product Dependencies. This section contains information about the
levels or service levels of other products you might need to run with the
software you intend to install, or service that you might need to install to run
other products.

You receive PSP buckets with your order, as members of a data set named
hlq.CPAC.PGMDIR (for ServerPac and SystemPac) or hlq.IPO1.PGMDIR (for
CBPDO). You should download the latest PSP buckets using IBMLink or
Information/Access, or request them from your IBM Support Center.

Maintenance after Installation

After you have installed z/OS, IBM suggests that you install preventive maintenance
using Recommended Service Upgrades (RSUs). An RSU is an SMP/E SOURCEID
(RSUyymm) used to identify a subset of available PTFs. It is limited to PTFs that
meet the following criteria:
v Severity 1 or 2
v High impact or pervasive APAR (HIPER)
v PTF-in-error (PE) fix
v Security or integrity
v Special attention (recommended because of new function, serviceability,
installability, or pervasiveness)

RSUs are designed to reduce the volume of maintenance that you need to apply.
RSUs are available monthly. IBM recommends that you install an RSU every three
months if possible, with the RSU level being current month minus two.

You should also regularly (weekly if possible) review current HIPER and PE PTFs
as part of your preventive maintenance policy. You should roll these fixes into
production at least monthly. If you are unable to install RSU maintenance every
three months, then it is more important to review the HIPER and PE fixes on a
regular basis.

For SystemPac users, follow-on services (SFSs) come free as an option when you
order a SystemPac. You can order a maximum of three SFSs with maximum
intervals of 90 days apart. SFSs contain PTFs fixing PEs and HIPERs. They are
built according to the copy of the SMP/E consolidated software inventory (CSI) of
your system. Thus, these critical services are tailored to fit your environment.

One way to review HIPER and PE PTFs is to use Enhanced HOLDDATA.

Enhanced HOLDDATA is HOLDDATA with additional information to identify the
reason for the hold and a fixing PTF. Enhanced HOLDDATA provides a hold against
function SYSMODs (FMIDs) for HIPER and PE PTFs. (Nonenhanced HOLDDATA
provides a hold only against PE PTFs.)

To display the Enhanced HOLDDATA, use the SMP/E REPORT ERRSYSMODS

command. The SMP/E report, when used with Enhanced HOLDDATA, identifies

Chapter 1. Learning about z/OS 31

 missing critical service that applies to your specific system. This allows you to
identify any missing HIPER and PE fixes for any target zone. Additionally, the report
identifies whether a corrective PTF is available, whether the corrective PTF is
already in RECEIVE status, and the reason indicator for a HIPER.

Enhanced HOLDDATA is available through ESO packages, with CBPDO orders,

through the S/390 Service Update Facility (SUF), and from the World Wide Web.
For more information, see the ESO Memo to Users Extension, the CBPDO Memo
to Users Extension, or the Enhanced HOLDDATA Web site at:
http://service.boulder.ibm.com/390holddata.html

To perform (or install) service on elements and features, you must minimally meet
the driving system requirements for CBPDO Wave 2, which include having OS/390
UNIX kernel services operating in full-function mode on the system that is driving
the service installation. For CBPDO Wave 2 driving system requirements, see
“Driving System Wave 2” on page 57.

Service Distribution
Preventive and corrective service are delivered using processes such as Extended
Service Offering (ESO), CBPDO, RefreshPac, and ServiceLink.

The S/390 Technical Support Web site contains information about problem
submission, problem review, open and closed APARs, documentation, and a pointer
to ServiceLink. The Web address is:
http://www.ibm.com/s390/support/

System/390 Service Update Facility

S/390 Service Update Facility (SUF) is an Internet-based software service tool that
| makes ordering and receiving z/OS, OS/390, z/VM, VM/ESA, and VSE/ESA
software service quick and easy. SUF allows system programmers to order both
corrective and preventive service via the Internet. Because SUF accesses the
consolidated software inventory (CSI), the service is tailored; only the service
missing from the customer’s system is sent.

z/OS service, both corrective and preventive, can be delivered via the Internet or
via standard physical media. A common “GUI” interface is provided via the SUF
Customer Application Server. This workstation server can support multiple system
programmers supporting multiple S/390 servers.

For details regarding prerequisites, entitlement, and how to obtain SUF, refer to the
S/390 SUF home page:
http://www.ibm.com/s390/products/suf

RefreshPac
RefreshPac is a software preventive service offering that is available worldwide.
RefreshPac can update one or all target and DLIB zone pairs residing in a target
and DLIB consolidated software inventory (CSI). These zone pairs must belong to
the same system release identifier (SREL). RefreshPac is customized by providing
input from the customer in the form of a copy of the CSI information that the target
and DLIB zone pairs to be serviced resided in. Upon delivery of the RefreshPac,
you are entitled to selective follow-on services (SFSs). SFSs contain PTFs that fix
PE and HIPER fixes that are discovered after the package was shipped to you. By
applying SFSs repeatedly, HIPER and PE fixes are flushed out of your system, thus
providing a highly available system for your applications.

32 z/OS V1R1.0 Planning for Installation

 Limiting the Amount of CBPDO Service
Prior to September 2000, CBPDO provided service for all releases of each product
licensed under a customer number in the ordered SREL, as well as unintegrated
service for the ordered products. Consequently, many customers received much
more service than they anticipated.

As of September 2000, CBPDO has been enhanced to optionally provide service

for either (1) the ordered products only or, (2) for MVS SREL orders, selected
releases. This change allows you to customize the service in your z/OS order to
your specific needs as well as reduce the overall size of the deliverable. This
enhancement is not available with subscription CBPDOs.

The following options are now available when ordering CBPDO:

v Product-only option.
| If you intend to install only the products delivered with your CBPDO order, and
| not to service your entire system, select the option to include service for the
| ordered products only. This is referred to as the product-only option. Selecting
| this option will significantly reduce the size of your order. This option can also be
| used to obtain the equivalent FMID and service content formerly delivered with
| the stand-alone product and CUM tape. Note that this option is the default when
| you use ShopzSeries (the Web application for ordering software) to place a
| CBPDO order that includes one or more products.
| Your customer service history will not be updated when using the product-only
| option. Therefore, your next non-product-only CBPDO order for the same SREL
| will duplicate some of the service you received on the product-only CBPDO.
| Likewise, if you receive subscription CBPDOs, you should expect to receive
| duplicate service if one of these orders follows a product-only CBPDO order for
| the same SREL.
| When ordering z/OS in CBPDO, IBM recommends that you do not include any
| other products in the same order. If you intend to service your entire system at
| the same time you install z/OS, consider placing two orders. Include z/OS and
| service for the ordered products only in one order. Then place a separate order
| to obtain service for your entitled products. This will limit the volume of data
| provided for each task to a manageable size.

| Note: For customers ordering the z/OS V1R1 Upgrade Package for OS/390
| V2R10, it is highly recommended that you not select the product-only
| option. Use the selective service option (selecting all OS/390 or z/OS
| release levels installed in your enterprise, including OS/390 R10) so that
| you will receive service for OS/390 R10 on which the Upgrade Package is
| based.
v Selective service option.
| When ordering service for your entitled MVS products, IBM recommends limiting
| the service provided for the base operating system product (that is, z/OS) to
| those releases currently available in your enterprise. This is referred to as the
| selective service option. Your order will include service only for the releases you
| select. If you do not use this option, your order will include service for all
| releases of each version of the base operating system entitled to your customer
| number, resulting in an extremely large order. Note that this option is required if
| you order service for your entitled MVS products through ShopzSeries.
| Your customer service history will be updated when using the selective service
| option. Therefore, your next MVS (Z038) CBPDO order will not contain service
| applicable to the base operating system product for the PUT/RSU levels
| delivered in your selective service CBPDO order. For this reason, in order to

Chapter 1. Learning about z/OS 33

| avoid a service gap, IBM recommends that when you use the selective service
| option you select all z/OS and OS/390 release levels available in your enterprise.
| If you choose to intentionally omit any releases, your next order must specify a
| starting service level in order to obtain the back-level service for the omitted
| releases.

We recommend keeping your global zone FMID list up to date, as well as using the
SMP/E enhanced RECEIVE command in order to screen out additional PTFs that
do not need to be received.

| CBPDO Subscriptions
| v There is a limit of four automatic shipments of service-only CBPDOs per SREL
| per year.
| v For an order to ship during a selected month, your customer profile must be
| updated by the preceding month.
| v The service level of a CBPDO is determined by the last CBPDO ordered in the
| same SREL, regardless of whether it was a subscription or individual order.
| Therefore, if you order a CBPDO prior to receiving your subscription CBPDO, the
| subscription will contain only new service approved for distribution since the prior
| CBPDO was created.
| v If you have never received a CBPDO for the SREL you are subscribing to, the
| first order will include the maximum two years of service. As with any product
| serviced using CBPDO, the SREL cannot be more than two years back-level in
| service. To avoid receiving two years of service, order a CBPDO (product or
| service-only) prior to subscribing, using existing methods and specifying a
| starting service level. Your first subscription order will then include service
| starting from the latest level received in your prior order.
| v If you wish to change the frequency or the particular month (or months) of the
| subscription CBPDO, delete from your customer profile the subscription CBPDO
| program number (5751-CS8) containing the subscription (7xxx) feature numbers.
| Then submit a new subscription CBPDO order.
|
Education and Training
IBM courses are available for z/OS. For schedules and enrollment:
v Phone enrollment: 1-800-IBM-TEACH
v On the World Wide Web:
http://www.training.ibm.com/

Publications
You can learn about the function provided by z/OS in z/OS Introduction and
Release Guide.

Refer to z/OS Information Roadmap for a list of titles and order numbers of all the
z/OS product books, descriptions of the books, information about the media in
which they’re available (CD-ROM, DVD, printed, or online), and how to get copies.

The two books mentioned above, as well as the rest of the z/OS product books, are
online at the z/OS Internet Library site. The books are provided in BookManager
form served up by BookManager BookServer. You can browse or download them. If
you download them, you can browse them on your workstation using any of the
BookManager products. The books are also provided in Portable Document Format
(PDF) form. You can download them and then print (or browse) them on almost any

34 z/OS V1R1.0 Planning for Installation

 workstation platform using the Adobe Acrobat Reader, which is available free from
the Web. Or, with the Infoprint Server feature of z/OS and the Infoprint Server
Transforms (5697-F51) product, you can transform PDF files to AFP format on z/OS
and print them on high-speed IBM AFP printers.

The z/OS Internet Library is at:

| http://www.ibm.com/servers/eserver/zseries/zos/bkserv/

At the z/OS Internet Library site you will also find:

v Up-to-the-minute technical information. For example, you will find the latest
updates to z/OS publications that result from DOC (documentation) APARs and
PTFs (++HOLD DOC).
| v Wizards. These are interactive assistants that ask you a series of questions
| about the task you want to do and then custom-build a checklist of steps for you
| to follow. For customization tasks, the wizards generate output such as:
| – Tailored instructions
| – Jobs, policies, and parmlib members that you can upload to z/OS and use
| v LookAt. LookAt improves z/OS message retrieval. Enter a message ID and
| LookAt will quickly return the message explanation.

Two other sources of information are:

v Redbooks, which are developed and published by IBM’s International Technical
Support Organization (ITSO). These books, named for the color of their covers,
are “how to” books written by very experienced IBM professionals from all over
the world. You can find redbooks at:
http://www.ibm.com/redbooks
v “Flashes”, which are articles written by IBM Systems Center personnel. Flashes
alert customers and IBM personnel to significant new technical developments
and guidance for the installation, use, and maintenance of IBM products. You can
find flashes at:
http://www.ibm.com/support/techdocs

Chapter 1. Learning about z/OS 35

36 z/OS V1R1.0 Planning for Installation
 Chapter 2. Choosing the Software Installation Method
z/OS can be installed using one of several IBM packages. Two of these packages
are available as part of your z/OS license, at no additional charge. Other packages
and offerings are available for a fee. This chapter helps you decide which to
choose.

Overview of Methods for Installing z/OS

This section provides an overview of the methods available for installing z/OS. Two
methods are entitled with z/OS, that is, they are provided as part of your z/OS
| license: ServerPac and CBPDO. (The new z/OS V1R1 Upgrade Package for
| OS/390 V2R10 is a CBPDO deliverable.) Other methods, such as SystemPac, are
available for an additional fee.

There is no FunctionPac or ProductPac for z/OS. There is no stand-alone product

tape for z/OS.

ServerPac Overview (Entitled)

ServerPac is an entitled software delivery package consisting of products and
service for which IBM has performed the SMP/E installation steps and some of the
post-SMP/E installation steps. To install the package on your system and complete
the installation of the software it includes, you use the CustomPac1 Installation
Dialog, which is the same dialog that is used for all the CustomPac offerings,
including SystemPac (dump-by-data-set format), ProductPac, and RefreshPac.

Two types of ServerPac installation are available to you. (You choose the type when
you install, not when you order.)
v A full system replacement installs a complete z/OS system. It installs all the data
sets you need to IPL, to log on to the target system, and to run a z/OS image in
order to complete other installation and customization tasks. The installed data
sets fall into two major categories:
1. System software and related data sets (such as distribution and target
libraries, SMP/E CSI 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 system
replacement helps assure a successful first IPL.

Depending on your environment, you might need to merge your existing

operational data sets with the data sets created by ServerPac. You can do this
before or after first IPL.
v A software upgrade installs only system software and related data sets (category
1 above). It does not create new operational data sets (category 2 above). With a
software upgrade, all operational data sets are assumed to already exist and to
be usable by the 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 parameters required by the new software level or change
data sets so they will work with both the old and new levels.

1. The CustomPac Web site is: http://www.ibm.com/ca/custompac/

© Copyright IBM Corp. 1996, 2001 37

 A software upgrade uses your existing catalog structure. This includes your
existing master catalog (with direct or indirect cataloging references) and user
catalogs. In addition, software upgrade allows you to create new user catalogs as
part of the installation process.
A software upgrade is possible for z/OS only, not for the subsystems.

CBPDO Overview (Entitled)

CBPDO (Custom-Built Product Delivery Option) is an entitled software delivery
package consisting of uninstalled products and unintegrated service. You must use
SMP/E to install the individual z/OS elements and features, and their service, before
you can IPL.

Although you can order other IBM products in the same CBPDO package as z/OS,
IBM recommends that you order other products in the same SREL (system release
identifier) separately because z/OS is a large product that spans many tapes. This
will significantly reduce the number of tape mounts required to install z/OS and the
other products.

| If you are migrating from OS/390 R10, you should use CBPDO to install the z/OS
| V1R1 Upgrade Package for OS/390 V2R10. This software delivery package is
| available only for those migrating from OS/390 R10, and it provides a quick and
| easy upgrade to the first release of z/OS. It consists of two new base elements
| (ILM and msys for Setup) and one updated base element (BCP). The rest of z/OS
| is unchanged and does not need to be reinstalled.

| Note: Be aware of the following important service consideration when ordering and
| installing the Upgrade Package. It is highly recommended that you upgrade
| service for the entire OS/390 R10 product at the time you install the Upgrade
| Package. This will ensure that you are at the minimum service level that was
| integration tested by IBM. Therefore, you should choose the CBPDO
| selective service option when ordering the Upgrade Package. (This option is
| described in “Limiting the Amount of CBPDO Service” on page 33). This will
| provide you with service for OS/390 R10, the Upgrade Package, and other
| products in your ordering profile.

SystemPac Overview (Fee)

SystemPac is a software package, available for an additional fee and offered
worldwide, that helps you install z/OS, its subsystems (DB2, IMS, CICS, and NCP),
and selected ISV products. SystemPac is tailored to your specifications; it is
manufactured according to parameters and input/output definition file (IODF)
definitions that you supply during order entry. The goal is to have the system
tailored to your specifications and have products enabled according to your
specified configuration. Parameters are collected by telephone. Using a printed
questionnaire as a guide, you tell an IBM representative your responses. Upon
completion, a printout showing all the parameters and definitions you specified is
sent to you for reference.

SystemPac comes in two formats: a full volume dump format (you install using
volume restore) and a dump-by-data-set format (you install using the CustomPac
Installation Dialog). In both formats, selected products, elements, features, and
functions (such as z/OS UNIX System Services, Communications Server, IBM
| HTTP Server, and WLM goal mode) are enabled with IBM defaults to allow you to
exploit e-commerce upon IPL once your enterprise connectivity is established.

38 z/OS V1R1.0 Planning for Installation

 SystemPac is designed for those who have limited skill or time to install or upgrade
z/OS but who want to install or upgrade to exploit z/OS functions in e-commerce or
other areas.

You can find information about SystemPac on the Web at:

http://www.ibm.com/ca/custompac/

Overview of Other Installation Methods (Fee)

Other fee-based methods (besides SystemPac) for installing z/OS are:
v The Entry Server Offering (available in some countries) is a packaged solution
that includes hardware, software, installation services, maintenance and financing
to help customers get to current technology.
v Other fee-based offerings include z/OS Select in the United Kingdom, Rapid
Migration Offering in Canada, Software Management in Germany, and Express
Plus Offering in France. Most of these offerings are based on SystemPac. These
offerings vary in scale; they can go as far as to include a total system cutover.
v Other fee-based services include customized solutions, hardware services, and
software services.

Contact an IBM representative for details about these fee-based installation

services or browse the IBM Global Services Web page at:
http://www.ibm.com/services/

Note: Except in this chapter, the scope of discussion in this book about installation
methods is limited to both of the entitled methods (ServerPac and CBPDO)
and one of the fee-based methods (SystemPac).

Additional Details about ServerPac, CBPDO, and SystemPac

This section provides a more detailed comparison of the two entitled installation
methods, ServerPac and CBPDO, and one of the fee methods, SystemPac.
Information is presented from the standpoints of how you order, what IBM does for
you, what you receive from IBM, and what actions you need to take.

How You Order — ServerPac, CBPDO, and SystemPac

ServerPac:
v You can order software products by using the self-service Web application
ShopzSeries, by using IBMLink, or by contacting an IBM representative. You can
find ShopzSeries at:
| https://inetsd01.boulder.ibm.com/ShopzSeries/ShopzSeries.jsp

When ordering upgrades to software products for which you’re currently licensed,
you can generate an SMP/E report of installed software to be upgraded, and
upload the report to ShopzSeries. ShopzSeries selects upgrades and performs
technical requisite checking. ShopzSeries then lets you submit the order and
track it through delivery.

The order is for a unique system release identifier (SREL). IBM recommends that
you order all products that you intend to install, migrate, and maintain on the
same schedule as z/OS (the “z/OS product set”) in the same ServerPac. (See
“Product Sets” on page 167 for a description of product sets.)

CBPDO:

Chapter 2. Choosing the Software Installation Method 39

 v You can order software products by using the self-service Web application
ShopzSeries, by using IBMLink, or by contacting an IBM representative. You can
find ShopzSeries at:
| https://inetsd01.boulder.ibm.com/ShopzSeries/ShopzSeries.jsp

When ordering upgrades to software products for which you’re currently licensed,
you can generate an SMP/E report of installed software to be upgraded, and
upload the report to ShopzSeries. ShopzSeries selects upgrades and performs
technical requisite checking. ShopzSeries then lets you submit the order and
track it through delivery.

You can place an order for products having one or more system release
identifiers (SRELs). The order will result in one set of CBPDO tapes for each
SREL for which you selected products in the order. IBM recommends that you
order only z/OS elements and features (or their equivalent stand-alone products)
using the CBPDO product-only option. (Ordering equivalent levels of
nonexclusive elements does not increase the size of the CBPDO because the
FMIDs (function modification identifiers) are the same, but it does enable the
IFAPRD00 PARMLIB member to be built correctly.) If you need to update other
products in the z/OS SREL, place a separate CBPDO order for these products.
v Optionally, you specify the desired starting service level.
| v If you’re migrating from OS/390 R10, see “Ordering the z/OS V1R1 Upgrade
| Package for OS/390 V2R10” on page 62.

SystemPac:
v You use an order checklist, which is available on the Internet
(http://www.ibm.com/s390/swinfo/os390.htm), on IBMLink via the configurator, or
from an IBM representative. Unlike a ServerPac order, a SystemPac order can
be for multiple system release identifiers (SRELs). IBM recommends that you
order in the same SystemPac all products that you intend to install, migrate, and
maintain on the same schedule as z/OS. The order checklist contains both IBM
and selected independent software vendor (ISV) products.
v When you place your SystemPac order, be sure to select the selective follow-on
services (SFSs) as well. You can specify a maximum of three SFSs at intervals
of 30, 60, or 90 days apart. SFSs contain PTFs fixing PE and HIPER PTFs that
are discovered after your system is built. SFSs are tailored to the SMP/E CSI of
your system. The goal of SFSs is to stabilize your system over time, thus
improving its availability. SFSs are delivered on the same media type as your
original order.
v Upon placing the order, an IBM representative will contact you to provide
additional help to have your order enriched. Enrichment is an important part of
SystemPac. Through a local order entry tool, your system’s parameters (such as
volume serials, DASD types, catalog names, SMP/E definitions, and SMS
definitions) are collected. This enables the SystemPac to be built exactly the way
you specified, eliminating the need for customizing upon system restore. This
also enables IBM to enable subsystems and products according to your
specifications (for example, z/OS UNIX System Services in full function mode
according to your SMS specifications).
v You also need to send a copy of your IODF to the IBM manufacturing center.
Your SystemPac will be built according to your IODF input. You can send the
IODF electronically or via physical media.

What IBM Does for You — ServerPac, CBPDO, and SystemPac

ServerPac:

40 z/OS V1R1.0 Planning for Installation

 v IBM integrates the products you ordered and selected service into target and
distribution libraries and their SMP/E zones.
v IBM customizes parmlib according to the products and features that you ordered.
v IBM verifies the resulting system for the specific package by doing an IPL,
submitting a job, logging on to TSO/E, and checking the job’s output. IBM
performs this test using the operational data sets supplied with the ServerPac.
The effect of this test on your first IPL depends on your installation path:
– If you choose the full system replacement installation path, the test helps
assure a successful first IPL.
– If you choose the software upgrade installation path, you will use your own
existing operational data sets, so this test will not assure that the system will
IPL in your environment. However, it does make sure that the software itself
can be used to IPL given a usable set of operational data sets.
v IBM selects all unintegrated service for products ordered and includes it on a
service tape.

CBPDO:
v IBM includes the products that were ordered.
v Unless you specify otherwise, IBM selects service for the products you ordered
and for products that are:
– Already licensed under the same customer number you used to place your
order
– Installable in the same SREL as the base product (like z/OS or CICS) that you
specified

As of September 2000 you have new options that allow you to customize the
service provided in your order. See “Limiting the Amount of CBPDO Service” on
page 33 for details.
| v For complete z/OS V1R1 CBPDO orders, IBM builds a customized job stream to
| enable the ordered features that use dynamic enablement. If you order the z/OS
| V1R1 Upgrade Package for OS/390 R10, you have to convert your OS/390 R10
| copy of PARMLIB member IFAPRDxx. For details, see “Migration Actions for
| Dynamic Enablement Member IFAPRDxx” on page 142.

SystemPac:
v IBM integrates products (including subsystems and certain ISV products) and
selected service into target and distribution libraries and their SMP/E zones. For
a list of available ISV products, visit:
http://www.ibm.com/ca/custompac/
v IBM builds the system according to your specifications. SystemPac is built using
a copy of your IODF as input. An IBM representative will assist you to obtain
your specifications. For a list of specifications, see the local order entry user’s
guide at:
http://www.ibm.com/ca/custompac/
v IBM enables selected products, subsystems, elements, and features so that they
can be exploited upon IPL. Examples are:
– Enablement of z/OS UNIX System Services in full function mode according to
your specifications of an SMS environment.
– Optional enablement of IBM HTTP Server. The enablement of z/OS UNIX
System Services, Communications Server (IP Services), and IBM HTTP
Server provide you with Internet access upon restore and IPL.
– Optional enablement of Infoprint Server using IBM defaults.

Chapter 2. Choosing the Software Installation Method 41

 – Optional enablement of workload manager (WLM) in goal mode using a
sample policy.
– Enablement of selected ISV products through collected customers’
specifications, for example, SVC for Syncsort.
– Enablement of subsystems (CICS, IMS, and DB2) up to the point where you
can execute a full IVP.
– Optional enablement of WLM-established or DB2-established stored
procedures.
– Optional enablement of indirect cataloging with full volume dump SystemPac.
By using symbolic volume serials for target volumes, indirect cataloging allows
the system residence volume to be used by different systems. Indirect
cataloging thus minimizes the effort of changing system parameters (such as
parmlib) after cloning before you can enable your cloned system to be up and
running.
v IBM verifies the resulting system for the specific package by doing an IPL and
IVP tests. Integrated subsystems are also IVP tested. The output of jobs is
checked.
v IBM selects all unintegrated service for products ordered and includes it on a
service tape.
v IBM supplies selective follow-on services (SFSs) upon the initial shipment of your
system. These services are delivered to you according to the frequencies and
intervals you specified during ordering.

What You Receive from IBM — ServerPac, CBPDO, and SystemPac

ServerPac only:
v Tapes in IEBCOPY dump-by-data-set format (not a physical volume dump)
containing a complete generated z/OS system. This consists of distribution and
target libraries, consolidated software inventory (CSI), data sets needed for
system operation, CustomPac sample data sets, and integrated service.
v The CustomPac Installation Dialog. This dialog generates tailored installation jobs
and saves detailed definitions of volume, catalog, and data set configurations,
which can be tailored, saved, and merged to install subsequent ServerPacs.
v Documentation to guide installation, up to and including installation verification
procedures (IVPs). The book ServerPac: Installing Your Order is custom-built to
your order and is provided in printable (LIST3820), ISPF-browseable (LIST1403),
and BookManager-viewable (BOOK) formats.
v Reports that contain information on the PTFs that were integrated in your order.

CBPDO only:
v Stacked tapes of products and service.
| v For complete z/OS V1R1 CBPDO orders, limited installation jobs and
documentation to receive products and service, create the dynamic enablement
parmlib member (IFAPRDxx), and create SMP/E FMIDSETs for each installation
ripple. (Installation is divided into four stages called waves. Waves 1 and 2, in
order to be more manageable, are divided into several tasks called ripples.)
| v For orders of the z/OS V1R1 Upgrade Package for OS/390 V2R10, limited
| installation jobs and documentation to receive products and service. There is no
| job to create the dynamic parmlib member; instead, you convert your OS/390
| R10 member for use on z/OS. Installation isn’t done in stages; instead, all FMIDs
| are installed at once.

SystemPac only:

42 z/OS V1R1.0 Planning for Installation

 v Tapes containing a complete generated z/OS system. This complete system
consists of distribution and target libraries, consolidated software inventory (CSI),
data sets needed for system operation, CustomPac sample data sets, and
integrated service.
If the SystemPac is in dump-by-data-set format, the tapes are in IEBCOPY
dump-by-data-set format (not a physical volume dump). If the SystemPac is in
full volume dump format, the tapes are in physical volume format (DFSMSdss
dumped or Innovation Data Processing FDR dumped, depending on your choice
during ordering).
v The CustomPac Installation Dialog. This dialog generates tailored installation jobs
and saves detailed definitions of volume, catalog, and data set configurations,
which can be tailored, saved, and merged to install subsequent CustomPac
packages. Although the dialog is shipped, you will not need to invoke it to install
your full volume dump SystemPac and its subsequent SFSs.
v Documentation to guide installation, up to and including IVPs. The installation
guide that is custom-built to your order is provided in printable (LIST3820),
ISPF-browseable (LIST1403), and BookManager-viewable (BOOK) formats.
v SystemPac: CustomPac Dialog Reference and SystemPac: CustomPac
Messages. These two documents guide you step-by-step in using the dialog to
perform various tasks.
v Reports that contain information on the PTFs that were integrated in your order.
v Subsequent SFS tapes and installation guides. The number and timing of
shipments depend on the frequencies and intervals you specified during order
entry. SFSs can be installed by using the CustomPac Installation Dialog or by
using batch JCL.

ServerPac, CBPDO, and SystemPac:

| v Policy statements (in IFAPRDxx) for all orders except those for the z/OS V1R1
| Upgrade Package for OS/390 V2R10. The policy statements are needed if you
| use an S/390 server or for the ILM preproduction period on a z900 server.
| v Product certificates for new license orders for z/OS on a z900 server. For
| information about installing the product certificates, see z/OS IBM License
| Manager Administration.
v Diskettes for LANRES.
v Program directories in softcopy and hardcopy form. The softcopy program
directories are in viewable and printable LIST1403 format. Also, an index that
describes which program directory members are associated with each product in
your order is provided in member $INDEXPD in data set CPAC.PGMDIR.
v PSP information.
v All product publications in BookManager form on CD-ROMs. Also on the
CD-ROMs are tools to upload, manage, and view the books. The BookManager
Library Readers let you view the books on your workstation. The SoftCopy
Librarian (SCL) lets you upload books from the CD-ROMs to your z/OS host
DASD. The SoftCopy Librarian runs under Windows 95 and Windows NT, and
can help you set up and manage repositories of BookManager books on your
z/OS hosts. (BookManager READ or BookManager BookServer, both z/OS base
| elements, let you view the books in these host repositories.) LookAt, a z/OS
| online help facility, lets you retrieve z/OS message explanations quickly using
| only the message identifier (ID).
v All product publications in printable form on CD-ROMs. The books are provided
as Portable Document Format (PDF) files. You can print (and view) these files on
almost any workstation platform using the Adobe Acrobat Reader, which is
available free from the Internet.

Chapter 2. Choosing the Software Installation Method 43

| v Three publications in hardcopy form: this book, z/OS Planning for Workload
| License Charges, and z/OS Hot Topics Newsletter.
v z/OS source materials, for example, BCP and BDT source. However, unlike other
materials, the source materials are sent only if you order them.

What Actions You Need to Take — ServerPac, CBPDO, and SystemPac

ServerPac:
v Use the CustomPac Installation Dialog, as described in ServerPac: Using the
Installation Dialog, to:
– Load configuration data for your order to DASD from tape.
– Select the type of installation you prefer: full system replacement or software
upgrade. Each requires a different amount of work and a different order of
tasks. Refer to “Deciding Which Software Installation Method Is Best for You”
on page 45 for guidance in making your selection.
– Customize the system.
– Run the jobs that install distribution and target libraries for your target system.
– Run the IVPs provided. IVPs are provided for most, but not all, elements,
features, and products.
v Follow the instructions in ServerPac: Installing Your Order about preparing your
system for first IPL and verification. For example, if you’re using the software
upgrade installation path, you must ensure that all operational data sets needed
to IPL, run batch jobs, and use TSO/E exist on the target system before you IPL
the target system. These operational data sets include but are not limited to:
– A complete set of the necessary system control files (such as parmlib and
VTAMLST)
– A master catalog that can be updated while building the target system
– Page data sets
– A BRODCAST data set
– Spool and checkpoint data sets
– Security database
| v If running z/OS V1R1 on a z900 server in ILM production mode, set up a license
| server and load the product certificates. Refer to z/OS IBM License Manager
| Planning and Customization.

CBPDO:
v Use sample jobs to receive (SMP/E RECEIVE) products and service.
v Follow instructions in the program directory to install the elements and features,
with associated service. Work includes:
– Various tasks prior to running SMP/E APPLYs
– Running SMP/E APPLYs
– Post-APPLY tasks
– Customization
– Running IVPs
– Running SMP/E ACCEPTs
– Post-ACCEPT cleanup.

| For regular CBPDO orders, you install FMID-by-FMID and you do the work
| above for each wave and ripple. For orders of the z/OS V1R1 Upgrade Package
| for OS/390 V2R10, you install all FMIDs at once and you do the work above
| once.

44 z/OS V1R1.0 Planning for Installation

| v If running z/OS V1R1 on a z900 server in ILM production mode, set up a license
| server and load the product certificates. Refer to z/OS IBM License Manager
| Planning and Customization.

SystemPac full volume dump format:

v Follow the instructions for preparing to install in SystemPac Installation Guide.
You can install your SystemPac using stand-alone utilities or batch JCL. With
stand-alone utilities, there is no need for a driving system. You simply initialize
your DASD volumes and restore the SystemPac tapes to DASD, following the
samples supplied in the installation guide. If you install your SystemPac using
batch JCL, create the initialization and restore JCL following the samples
supplied in the installation guide.

SystemPac dump-by-data-set format:

v Use the CustomPac Installation Dialog, as described in SystemPac: CustomPac
Dialog Reference, to:
– Receive your order from tape to driving system DASD.
– Select the type of installation you prefer: full system replacement or software
upgrade. Each requires a different amount of work and a different order of
tasks. Refer to “Deciding Which Software Installation Method Is Best for You”
for guidance in making your selection.
– Customize the system.
– Run the jobs that install distribution and target libraries for your target system.
– Run the IVPs provided. IVPs are provided for most, but not all, elements,
features, and products.
v Follow the instructions in the installation guide to prepare your system for first
IPL and verification. For example, if you’re doing a software upgrade, you must
ensure that all operational data sets needed to IPL, run batch jobs, and use
TSO/E exist on the target system before you IPL the target system. These
operational data sets include but are not limited to:
– A complete set of the necessary system control files (such as parmlib and
VTAMLST)
– A master catalog that can be updated while building the target system
– Page data sets
– Couple data sets
– A BRODCAST data set
– Spool and checkpoint data sets
– Security database

Deciding Which Software Installation Method Is Best for You

The best installation method is usually the one that requires the least amount of
work for you. Based on this premise, IBM recommends the following.

| If you’re new to z/OS and never had OS/390, or if you’re migrating from an
| operating system level that is no longer supported (OS/390 R5 and earlier, or
| any of the MVS operating systems), use one of the following:
v SystemPac in full volume dump format. (SystemPac is a fee offering.)
v One of the other fee methods.
v ServerPac using the full system replacement installation path. (ServerPac is
entitled.) This situation requires the Customized Offerings Driver (5665-343) as a
driving system. (The Customized Offerings Driver is entitled.)

Chapter 2. Choosing the Software Installation Method 45

| If you’re migrating from OS/390 R6, R7, R8, or R9, use any method (ServerPac,
CBPDO, or fee):
v Of the entitled methods (ServerPac and CBPDO):
– Use ServerPac if most of the elements and features already installed on your
system are not equivalent to the z/OS V1R1 level. Of your two choices within
ServerPac, software upgrade is preferable to full system replacement in the
following cases:
- You’re creating a new system image that will share operational data sets
(like the master catalog and parmlib) with existing systems.
- Your new environment will be similar to your old one.
- Your data set layouts will be the same or similar. (IBM’s recommendations
are described in “Placing Data Sets on Specific Volumes” on page 167).
- You prefer to migrate your operational data sets before (not after) IPLing
the new system for the first time.
– Use CBPDO if most of the elements and features already installed on your
system are equivalent to the z/OS V1R1 level, your enterprise has good to
excellent product installation skills, and you are within six months of service
currency. Otherwise, using ServerPac will probably take significantly less time
and effort.
v Of the fee methods (SystemPac full volume dump, SystemPac dump-by-data-set,
and the other more-tailored services):
– Use SystemPac full volume dump if you can. The restore of the system is
performed via volume restore. You get an IPLable system within a day. There
is no need to use installation dialogs for restoring and customizing. All
customizing is performed up front during local order entry, which an IBM
technical representative will guide you through.
– Use SystemPac dump-by-data-set if you want to do a software upgrade
instead of a full system replacement. The software upgrade installation path is
preferable to a full system replacement for the same reasons as in a
ServerPac installation, described above.
– Choose other fee offerings (for example, Select in the United Kingdom, Rapid
Migration Offering in Canada, Software Management in Germany, Express
Plus Offering in France) if you want to have more than a system replacement
done. Some of the additional activities you might want done for you are
system automation; production cutover; database and related applications
migration; backup and recovery; data management; disaster recovery;
parmlib, proclib, and VTAMLST conversion; and on-site support.

| If you’re migrating from OS/390 R10, use CBPDO to install the z/OS V1R1
| Upgrade Package for OS/390 R10. This deliverable provides a quick and easy
| upgrade to z/OS V1R1. It consists of two new base elements (ILM and msys for
| Setup) and one updated base element (BCP). All the other base elements and
| optional features are unchanged from OS/390 R10; there’s no need to reinstall
| them. Refer to “Ordering the z/OS V1R1 Upgrade Package for OS/390 V2R10” on
| page 62 for more information.

See “Chapter 3. Preparing the Driving System” on page 47 to find out the driving
system software and hardware requirements necessary to install a ServerPac,
CBPDO, or SystemPac order.

| Migrating to a new processor could affect your choice of installation method. See
| “Planning for z/OS on a z900 Server” on page 83.

46 z/OS V1R1.0 Planning for Installation

 Chapter 3. Preparing the Driving System
The driving system is the system image (hardware and software) that you use to
install the target system. The target system is the system software libraries and
other data sets that you are installing. You log on to the driving system and run jobs
there to create or update the target system. Once the target system is built, it can
be IPLed on the same hardware (same LPAR or same processor) or different
hardware than that used for the driving system.

This chapter identifies the software and hardware you will need for your driving
system. See “Chapter 4. Preparing the Target System” on page 59 for the software
and hardware you will need for your target system.

| Do not confuse the driving system discussed in this chapter (the installation driving
| system) with the msys for Setup driving system. To allow the setup of system
| components in a system that is not currently IPLed, msys for Setup supports a
| driving system and a target system. The msys for Setup driving system is the
| system where the msys for Setup code runs. The msys for Setup target system is
| the system that is being configured. For software requirements for the msys for
| Setup driving system, see “Appendix B. Software Requirements for z/OS Elements
| and Features” on page 201.

Need for driving system coexistence service

If your driving system will share resources with your target system after the
target system has been IPLed, then be sure to install applicable coexistence
service (see “Chapter 5. Ensuring Coexistence” on page 71) on the driving
system before you IPL the target system. If you don’t install the coexistence
service, you will probably experience problems due to incompatible data
structures (such as incompatible data sets, VTOCs, catalog records, GRS
tokens, or APPC bind mappings).

The Customized Offerings Driver (5665-343) is an entitled driving system,

described below. If you plan to use it, you must do one of the following:
v Provide a completely isolated DASD environment within which only the
Customized Offerings Driver will be used, or
v Install coexistence or fallback PTFs on your existing system before IPLing
the Customized Offerings Driver so that your existing system can be used
after the Customized Offerings Driver has been IPLed.

What Is the Customized Offerings Driver?

The Customized Offerings Driver (5665-343) is an entitled driving system you can
use if your existing system does not meet driving system requirements and you do
not want to upgrade your existing system to meet those requirements. This driver is
| a subset of an OS/390 R9 system.

The Customized Offerings Driver is in DFDSS dump/restore format and supports

3380, 3390, and 9345 DASD devices. The Customized Offerings Driver requires a
locally attached non-SNA terminal and a system console from the IBM (or
equivalent) family of supported terminal types: 317x, 327x, 319x, or 348x. An IBM
(or equivalent) supported tape drive is also required to restore the driver.

© Copyright IBM Corp. 1996, 2001 47

 The Customized Offerings Driver is intended to run in single-system image and
monoplex modes only. Its use in multisystem configurations is not supported. The
Customized Offerings Driver is intended to be used only to install new levels of
z/OS using ServerPac or CBPDO and to install service on the new software until a
copy (clone) of the new system can be made. The use of the Customized Offerings
Driver for other purposes is not supported. For example, IBM does not support the
use of the Customized Offerings Driver to run any production workload.

The Customized Offerings Driver includes an HFS and the necessary function to
use Communications Server (IP Services), SecureWay Security Server, and the
system-managed storage (SMS) facility of DFSMSdfp, but these items are not
customized. However, existing environments can be connected to, and used from,
the Customized Offerings Driver system. The Customized Offerings Driver supports
non-SMS-managed PDSE and HFS data sets.

Depending on the level of your existing system, the Customized Offerings Driver
might be at higher product and service levels. Therefore, as is true of the level of
software you plan to install, fallback service might be necessary to let you IPL and
use your existing level of software after the Customized Offerings Driver has been
IPLed and used in any environment. You must either use the Customized
Offerings Driver in a completely isolated environment or install the needed
fallback service on your existing system before the Customized Offerings
Driver is IPLed. A completely isolated environment shares no DASD with any other
system and will not be used to IPL any lower level of software.

Installing the service on your existing system, as described in “Chapter 5. Ensuring

Coexistence” on page 71, will also satisfy the requirements for falling back from the
Customized Offerings Driver. This will allow you to IPL and use your current level of
software after using either the Customized Offerings Driver or the new system. (IBM
has installed the service on the Customized Offerings Driver to allow it to be IPLed
and used (if necessary) after the new system has been IPLed and used.)

Identifying Driving System Software Requirements for ServerPac and

Dump-by-Data-Set SystemPac Orders
The most significant driving system requirements deal with the software needed to
load data sets from the installation tapes. This section contains three topics that
describe those and other requirements for ServerPac and dump-by-data-set
SystemPac orders.

Requirements to Load Data Sets from the Installation Tapes

| Note: ServerPac installation has been simplified by restoring all data sets
| (including HFS data sets) from the driving system. Prior releases allowed
| HFS data sets to optionally be restored from the target system. This option is
| no longer necessary and has been removed.

Either of the following driving systems satisfies the operating system requirement to
load (restore) data sets for ServerPac or dump-by-data-set SystemPac orders:
v The Customized Offerings Driver (5665-343). This entitled driving system is
provided for those whose existing system does not meet the requirements of a
driving system and who choose to not upgrade their driving system. For further
information, see “What Is the Customized Offerings Driver?” on page 47.
v OS/390 at any of the following levels:

48 z/OS V1R1.0 Planning for Installation

 – OS/390 R6 with the following PTFs:
- BCP: UW52846 (OS/390 UNIX kernel), UW66027
- DFSMSdfp: UW39107, UW39108, UW39371, UW39642, UW39830,
UW39942, UW40092, UW40270, UW40390, UW40395, UW40430,
UW40479, UW41018, UW41285, UW41334, UW50654, UW54887,
UW56138, UW57467, UW62067, UW62148, UW62252, UW64189,
| UW65973, UW66946, UW68577, UW68804, UW72304, UW73003,
UW90578, UW90651
| - DFSMSdss: UW65984, UW66178, UW66447, UW76512
- DFSMShsm: UW66207
- ISPF: UW66120
| - OS/390 UNIX System Services: UW52332, UW69452, UW75982
| - SecureWay Security Server: UW76337
| - SMP/E: UR51455 and, if Japanese, UR51461 (service level 25.25)
- TSO: UW66144
– OS/390 R7 with the following PTFs:
- BCP: UW66027
| - DFSMSdfp: UW62149, UW62253, UW64190, UW65974, UW66947,
| UW68578, UW68805, UW72305, UW73004, UW90654
| - DFSMSdss: UW65985, UW66179, UW66448, UW76513
- DFSMShsm: UW66208
- ISPF: UW66120
| - OS/390 UNIX System Services: UW68481, UW75983
| - SecureWay Security Server: UW76337
| - SMP/E: UR52066 and, if Japanese, UR52068 (service level 27.16)
- TSO: UW66144
– OS/390 R8 with the following PTFs:
- BCP: UW66028
- The same DFSMSdfp, DFSMSdss, and DFSMShsm PTFs as for OS/390
R7 (above)
- ISPF: UW66121
| - OS/390 UNIX System Services: UW68480, UW75984
| - SecureWay Security Server: UW76338
| - SMP/E: UR52066 and, if Japanese, UR52068 (service level 27.16)
- TSO: UW66144
– OS/390 R9 with the following PTFs:
- BCP: UW66028
- The same DFSMSdfp, DFSMSdss, and DFSMShsm PTFs as for OS/390
R7 (above)
| - OS/390 UNIX System Services: UW68482, UW75985
| - SecureWay Security Server: UW76338
| - SMP/E: UR52066 and, if Japanese, UR52068 (service level 27.16)
- TSO: UW66144
| – OS/390 R10 with the following PTFs:
| - DFSMSdfp: UW72306
| - DFSMSdss: UW76514

Chapter 3. Preparing the Driving System 49

| - OS/390 UNIX System Services: UW75986
| - SecureWay Security Server: UW76339
| - SMP/E: UR52066 and, if Japanese, UR52068 (service level 27.16)
| - TSO: UW66144, UW72455

The following additional requirements apply:

v A locally-attached or network-attached terminal that can be used to establish a
TSO/E session on the IPLed system is required.
v Installation must be performed from a user ID that:
– Is a superuser (UID=0). Notice that you must be a superuser; just having
access to the BPX.SUPERUSER resource in the RACF facility class is not
sufficient. This is because the pax utility is used to load the ServerPac HFS
and this utility does not use the BPX.SUPERUSER resource to establish
superuser identification.
– Has read access to facility class resources BPX.FILEATTR.APF and
BPX.FILEATTR.PROGCTL (or BPX.FILEATTR.* if you choose to use a
generic name for both resources).
In order to define these facility class resources, you can use the following
commands (which are also provided in SYS1.SAMPLIB member BPXISEC1
| and in the z/OS UNIX Customization Wizard at
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/wizards.html):
SETROPTS CLASSACT(FACILITY) RACLIST(FACILITY)
RDEFINE FACILITY BPX.FILEATTR.APF UACC(NONE)
RDEFINE FACILITY BPX.FILEATTR.PROGCTL UACC(NONE)

PERMIT BPX.FILEATTR.APF CLASS(FACILITY) ID(your_userid) ACCESS(READ)

PERMIT BPX.FILEATTR.PROGCTL CLASS(FACILITY) ID(your_userid) ACCESS(READ)
SETROPTS RACLIST(FACILITY) REFRESH

Or, if you choose to use a generic facility:

SETROPTS CLASSACT(FACILITY) GENERIC(FACILITY) RACLIST(FACILITY)
RDEFINE FACILITY BPX.FILEATTR.* UACC(NONE)

PERMIT BPX.FILEATTR.* CLASS(FACILITY) ID(your_userid) ACCESS(READ)

SETROPTS RACLIST(FACILITY) REFRESH
v The Storage Management Subsystem (SMS) must be active to allocate HFS and
PDSE data sets, whether they are SMS-managed or non-SMS-managed. Also,
the use of HFS data sets is supported only when SMS is active in at least a null
configuration, even when the data sets are not SMS-managed. Do either of the
following:
– To allocate non-SMS-managed HFS and PDSE data sets, you must activate
SMS on the driving system in at least a null configuration. (If your driving
system is OS/390, it is assumed that you have installed the PTFs for loading
data sets, listed above.) You must also activate SMS on the target system.
| – To allocate SMS-managed HFS and PDSE data sets, you must activate SMS
| on the driving system in at least a minimal configuration. Then you must
| define a storage group, create SMS-managed volumes, and write, translate,
| and activate a storage class ACS routine that allows the allocation of PDSE
| and HFS data sets with the names in the ALLOCDS job. You must also
| activate SMS on the target system.
v For ServerPac only: An activated OMVS address space with OS/390 UNIX kernel
services operating in full function mode is required.

50 z/OS V1R1.0 Planning for Installation

 Other Driving System Requirements
In addition to the requirements necessary to load data sets from the installation
tapes, there are other driving system requirements for ServerPac and
dump-by-data-set SystemPac orders. These additional requirements are:
v CustomPac Installation Dialog. If you are installing a ServerPac or
dump-by-data-set SystemPac for the first time, you need to install the
CustomPac Installation Dialog on your driving system. See ServerPac: Using the
Installation Dialog or SystemPac: CustomPac Dialog Reference for instructions.
For subsequent orders you do not need to reinstall the dialog. IBM ships dialog
updates with each order. Version checking is carried out during the receive step,
and if necessary, the dialog is updated during the install order step.
You should check the PSP bucket (for example, by using IBMLink) for possible
updates to the CustomPac Installation Dialog. For ServerPac, the upgrade is
| ZOSV1R1 and the subset is SERVERPAC. For SystemPac dump-by-data-set
orders, the upgrade is CUSTOMPAC and the subset is SYSPAC/DBD.
v Service. In order for you to install service on the target system that you’re
building, your driving system must minimally meet the driving system
requirements for CBPDO Wave 2 (see “Driving System Wave 2” on page 57) and
must have the current levels (z/OS V1R1) of SMP/E and HLASM.
The service jobs generated by the CustomPac Installation Dialog use the target
system’s level (z/OS V1R1) of SMP/E and HLASM. If you choose to use your
own jobs, model them after the jobs provided by ServerPac or dump-by-data-set
SystemPac by adding STEPLIB DD statements to access MIGLIB (for SMP/E)
and SASMMOD1 (for HLASM). Be sure that the SASMMOD1 and SYS1.MIGLIB
data sets are APF authorized.

Note: Another way to install service is from a copy of your target system.

Preparing for Installation

If you are going to install z/OS using a ServerPac or dump-by-data-set SystemPac,
take the following steps:
1. Separate customization data and non-z/OS products from your system software
as described in “Separating Data from Software” on page 164. This will minimize
your installation and migration workload not only for this installation but for
future ones.
2. Plan your data set layout ahead of time. Before running any of the jobs
generated by the CustomPac Installation Dialog, decide where (on which
volumes) you want to place product libraries and other data sets. You may
choose to implement IBM’s recommended layout as described in
“Recommended Data Set Placement” on page 170 and shown in “Appendix E.
Data Set Placement Recommendations for Target Volumes” on page 243, or you
could lay out the same catalog and volume structure of your current system.
After completing the installation, you can save the configuration (including
layout) and use it in future installations.
| The easiest way to implement IBM’s recommended layout is to assign your
| order’s data sets to DASD volumes automatically, using the dialog’s Create a
| Recommended System Layout function. This function helps you configure a
| target system that complies with the recommended system layout. The
| alternative is to assign data sets manually using either (1) the View and Change
| Data Sets by Selected Attributes function or (2) the Summary Display
| commands on the Modify System Layout Options panel.
As part of layout planning, decide whether you’ll want to merge any data sets
that have matching attributes in order to create a single panel library, single

Chapter 3. Preparing the Driving System 51

| message library, and so forth. This is most easily done using the View and
| Change Data Sets by Selected Attributes option. See ServerPac: Using the
Installation Dialog or SystemPac: CustomPac Dialog Reference for information
about merging data sets in a ServerPac or dump-by-data-set SystemPac. Be
aware that not all data sets that can be merged should be merged.
3. If possible, have empty volumes available onto which you will install your order.
Empty volumes make it easier to start over if necessary. But if you choose to
place data sets on volumes that are not empty, follow these steps:
a. Back up the target volumes.
b. Check the names of data sets on the volumes. A data set name on a given
volume must not be the same as the name of a data set that you plan to
install on that volume. You can use the Report function of the CustomPac
Installation Dialog to get a list of data sets in your current configuration.
All data sets are initially allocated with a system-specific alias (SSA). Later
during installation they are renamed to remove the SSA. If you are installing
onto existing volumes you must ensure that the existing data set names are
unique. For example, data set XYZ will be initially allocated as SSA.XYZ.
Later during installation it will be renamed to XYZ. Therefore, neither
SSA.XYZ nor XYZ can previously exist on the same volume.
4. Make sure that any data sets you choose to SMS-manage will not have names,
with or without an SSA, that duplicate the names of existing data sets on your
driving system. This is because SMS-managed data sets cannot coexist with
like-named data sets in the driving system’s catalog structure. Data sets with
duplicate names will become inaccessible from your driving system during
installation, and installation jobs will fail.
5. If you have decided to do a software upgrade instead of a full system
replacement, follow these steps:
a. Back up catalogs that will be updated by the installation process. You can
use the Defining Alias-to-Catalog Relationships panel in the CustomPac
Installation Dialog to determine which catalogs will be updated. Consider
using a DASD backup utility such as DFSMSdss or the IDCAMS EXPORT
TEMPORARY command. (But don’t use the IDCAMS REPRO command.
REPRO changes volume ownership for VSAM and SMS-managed data sets
from the input catalog to the output catalog.) For information about
DFSMSdss, see z/OS DFSMSdss Storage Administration Guide and z/OS
DFSMSdss Storage Administration Reference. For information about backing
up catalogs using the EXPORT command, see z/OS DFSMS: Managing
Catalogs and z/OS DFSMS Access Method Services.
b. Back up other operational data sets (like parmlib, proclib, the primary RACF
database, and SMS CDS data sets) that will be updated during the
installation.
c. When using the CustomPac Installation Dialog’s Modify System Layout
function, make sure that the data set layout you specify matches your
current system’s catalog and volume structure (with the exception of new
data sets that will be allocated as part of the installation and old data sets
that you don’t need to keep). If you choose software upgrade, you will run
two installation jobs that report differences between the data set layout you
specify and the current system’s data set layout.
If you cannot avoid changing the layout, you have to decide whether to
change the existing configuration or the new configuration. If the existing
catalogs will never be used to IPL a system other than the new target, or the
changes will not affect other systems that use the same catalog, you can
change the existing configuration. However, if the existing catalogs will be

52 z/OS V1R1.0 Planning for Installation

 used to IPL other systems and there is a possibility that users of those
systems will be adversely impacted by the changes that the new catalog
entries introduce, you must change your existing environment before
performing the installation, change your planned configuration to make it
compatible with your existing environment, or use new catalogs for the
installation.
d. If you intend to use the software upgrade installation path, you should plan
to back up the catalogs that will be updated. Use a utility like DFSMSdss or
IDCAMS EXPORT to do the backup.
6. Set up parmlib and proclib concatenation as described in z/OS MVS
Initialization and Tuning Reference. This step will save migration time now and
in future installations.
7. If you use indirect cataloging at your site and have chosen to do a full system
replacement, you will have some additional migration work to do after installing
because the new catalogs created by the installation process use volume/unit
referencing, not indirect cataloging. You can do one of the following:
v Add the new entries to your existing catalogs and connect the new user
catalogs to your existing catalogs.
v Update the new catalogs to use indirect and extended indirect catalog
entries.

Identifying Driving System Software Requirements for Full Volume

Dump SystemPac Orders
For a SystemPac full volume dump installation, there are three possible ways to
restore your order:
v With stand-alone utilities.
If you do not have an OS/390 or z/OS driving system, your SystemPac order
contains the stand-alone versions of the following utility programs so that you can
install your order:
– ICKDSF, to be used to initialize DASD, create VTOCs, and perform other
utility functions during system installation
– DFSMSdss, to restore the volume from tape to DASD

The utilities are provided based on selections you make during local order entry.
See the SystemPac Installation Guide supplied with your order for details about
running these utilities.
v With batch JCL.
This is the most common way to install a full volume dump order. If you have an
OS/390 driving system, you can install your order through a batch job that
initializes and restores the DASD volumes. However, you need to have the
following software:
– ICKDSF R16
| – DFSMSdss V1R4 or later, or Innovation Data Processing’s FDR V5.3.44 or
| later

The JCL to restore the DASD volumes is described in the SystemPac Installation
Guide supplied with your order.

Chapter 3. Preparing the Driving System 53

 A full volume dump order is a load-and-go implementation that allows you to IPL
your system as it is restored. You can customize after you have brought up your
target system. Jobs are “file-tailored” and stored in a library, as described in the
SystemPac Installation Guide.
v With the CustomPac Installation Dialog.
If you previously installed a ServerPac or dump-by-data-set SystemPac order
and you have the CustomPac Installation Dialog installed, you can use the dialog
to receive your order from the RIM tape and then use the dialog to install your
order. If you use this method, after your DASD volumes are restored and the
catalog volume is available, you need to connect the target system master
catalog to your driving system. For details, see the SystemPac Installation Guide
sent with your order.

Identifying Driving System Software Requirements for CBPDO Orders

| The driving system requirements for a CBPDO installation of z/OS depend on which
| installation package you’re using:
| v If you’re doing a complete z/OS V1R1 CBPDO installation, you install in four
| stages called waves. See the requirements for each wave below.
| v If you’re installing the z/OS V1R1 Upgrade Package for OS/390 V2R10, your
| driving system must meet the requirements in “Driving System Wave 2” on
| page 57.

Driving System Wave 0

In Wave 0 you install HLASM and SMP/E, which are the elements that must be
installed on, or available from, the driving system for subsequent wave installations.

You can use either of the following as the driving system for installing Wave 0:
v The Customized Offerings Driver (5665-343). This entitled driving system is
provided for those whose existing system does not meet the requirements of a
driving system and who choose to not upgrade their driving system. For further
information, see “What Is the Customized Offerings Driver?” on page 47.
v OS/390 at any of the following levels, with the following SMP/E PTFs:
| – OS/390 R6 with SMP/E PTFs (service level 25.25) UR51455 and, if
| Japanese, UR51461.
| – OS/390 R7 or later with SMP/E PTF (service level 27.19) UR52320.

Driving System Wave 1

In Wave 1 you install elements and features that establish (1) IP connectivity and
(2) an activated OMVS address space with z/OS UNIX kernel services operating in
full function mode.

Either of the following driving systems satisfies the operating system requirement
for installing Wave 1:
v The Customized Offerings Driver (5665-343).
v OS/390 at any of the levels below, except that the HLASM and SMP/E elements
must be at OS/390 R7 or later. To satisfy the HLASM and SMP/E requirements,
you can use STEPLIB DD statements to access z/OS V1R1 HLASM in the Wave
0 target system’s SASMMOD1 data set, and z/OS V1R1 SMP/E in the Wave 0
target system’s SYS1.MIGLIB data set. Ensure that the target system’s
SASMMOD1 and SYS1.MIGLIB data sets are APF authorized on the driving
system.

54 z/OS V1R1.0 Planning for Installation

 – OS/390 R6 requires the following PTFs:
- BCP: UW52846 (OS/390 UNIX kernel), UW66027
- DFSMSdfp:
v If DFSMS/MVS V1R4 level: UW39107, UW39108, UW39371, UW39642,
UW39830, UW39942, UW40092, UW40270, UW40390, UW40395,
UW40430, UW40479, UW41018, UW41285, UW41334, UW50654,
UW54887, UW56138, UW57467, UW62067, UW62148, UW62252,
| UW64189, UW65973, UW66946, UW68577, UW68804, UW72304,
| UW73003, UW90578, UW90651
| v If DFSMS/MVS V1R5 level: UW62149, UW62253, UW64190, UW65974,
| UW66947, UW68578, UW68805, UW72305, UW73004, UW90654
- DFSMSdss:
| v If DFSMS/MVS V1R4 level: UW65984, UW66178, UW66447, UW76512
| v If DFSMS/MVS V1R5 level: UW65985, UW66179, UW66448, UW76513
- DFSMShsm:
v If DFSMS/MVS V1R4 level: UW66207
v If DFSMS/MVS V1R5 level: UW66208
- ISPF: UW66120
| - OS/390 UNIX System Services: UW52332, UW69452, UW75982
| - SecureWay Security Server: UW76337
| - SMP/E: UR51455 and, if Japanese, UR51461 (service level 25.25)
- TSO: UW66144
– OS/390 R7 requires the following PTFs:
- BCP: UW66027
| - DFSMSdfp: UW62149, UW62253, UW64190, UW65974, UW66947,
| UW68578, UW68805, UW72305, UW73004,UW90654
| - DFSMSdss: UW65985, UW66179, UW66448, UW76513
- DFSMShsm: UW66208
- ISPF: UW66120
| - OS/390 UNIX System Services: UW68481, UW75983
| - SecureWay Security Server: UW76337
| - SMP/E: UR52320 (service level 27.19)
- TSO: UW66144
– OS/390 R8 requires the following PTFs:
- BCP: UW66028
- The same DFSMSdfp, DFSMSdss, and DFSMShsm PTFs as for OS/390
R7 (above)
- ISPF: UW66121
| - OS/390 UNIX System Services: UW68480, UW75984
| - SecureWay Security Server: UW76338
| - SMP/E: UR52320 (service level 27.19)
- TSO: UW66144
– OS/390 R9 requires the following PTFs:
- BCP: UW66028
- The same DFSMSdfp, DFSMSdss, and DFSMShsm PTFs as for OS/390
R7 (above)
| - OS/390 UNIX System Services: UW68482, UW75985

Chapter 3. Preparing the Driving System 55

| - SecureWay Security Server: UW76338
| - SMP/E: UR52320 (service level 27.19)
- TSO: UW66144
| – OS/390 R10 requires the following PTFs:
| - DFSMSdfp: UW72306
| - DFSMSdss: UW76514
| - OS/390 UNIX System Services: UW75986
| - SecureWay Security Server: UW76339
| - SMP/E: UR52320 (service level 27.19)
| - TSO: UW66144

The following additional requirements apply:

v In order to install into the HFS, the user ID that you use must:
– Be a superuser (UID=0) or have read access to the BPX.SUPERUSER
resource in the RACF facility class.
– Have read access to facility class resources BPX.FILEATTR.APF and
BPX.FILEATTR.PROGCTL (or BPX.FILEATTR.* if you choose to use a
generic name for both resources).
In order to define these facility class resources, you can use the following
commands (which are also provided in SYS1.SAMPLIB member BPXISEC1
| and in the z/OS UNIX Customization Wizard at
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/wizards.html):
SETROPTS CLASSACT(FACILITY) RACLIST(FACILITY)
RDEFINE FACILITY BPX.FILEATTR.APF UACC(NONE)
RDEFINE FACILITY BPX.FILEATTR.PROGCTL UACC(NONE)

PERMIT BPX.FILEATTR.APF CLASS(FACILITY) ID(your_userid) ACCESS(READ)

PERMIT BPX.FILEATTR.PROGCTL CLASS(FACILITY) ID(your_userid) ACCESS(READ)
SETROPTS RACLIST(FACILITY) REFRESH

Or, if you choose to use a generic facility:

SETROPTS CLASSACT(FACILITY) GENERIC(FACILITY) RACLIST(FACILITY)
RDEFINE FACILITY BPX.FILEATTR.* UACC(NONE)

PERMIT BPX.FILEATTR.* CLASS(FACILITY) ID(your_userid) ACCESS(READ)

SETROPTS RACLIST(FACILITY) REFRESH
v An SMP/E UTILITY entry for the binder is required. You can specify any of these
program names in the UTILITY entry: IEWBLINK, HEWL, IEWL, LINKEDIT, or
HEWLH096. (The linkage editor, which uses the names HEWLKED, HEWLF064,
IEWLF440, IEWLF880, and IEWLF128, cannot be used.)

Before you install Wave 1, you must activate the OMVS address space (in either
minimum or full function mode) on the driving system. To activate OMVS, complete
the required customization (for example, SMS and RACF setup) as described in
z/OS UNIX System Services Planning.

You must install Wave 1 to a system that already has the HFS data sets installed
for two reasons:
v Because some of the Wave 1 elements (notably Language Environment and
Communications Server) contain SMP/E VER DELETE statements for their prior
levels that include HFS FMIDs, installation of these elements will attempt to
access the HFS in order to DELETE the prior FMIDs if they were installed.

56 z/OS V1R1.0 Planning for Installation

 v Wave 1 contains some FMIDs that install into the HFS, including
Communications Server and z/OS UNIX System Services.
If you have already installed HFS FMIDs on your system, you may combine Waves
1 and 2. If you have previously installed these HFS FMIDs that will be VER
DELETEd, you must ensure that the target system’s HFS is available (OMVS active
and the target file systems mounted) for processing during Wave 1.

Driving System Wave 2

In Wave 2 you install elements and features that use shell and utility commands
now or might use them in the future.

You can use either of the following as the driving system for installing Wave 2:
v A copy of the target system that you installed in Wave 1.
| v The same level of OS/390 that is specified for Wave 1 (R6 or later), as well as
| the additional requirements specified. See “Driving System Wave 1” on page 54.

Before you install Wave 2, you must activate the OMVS address space in full
function mode on the driving system. To activate OMVS, complete the required
customization (for example, SMS and RACF setup) as described in z/OS UNIX
System Services Planning.

If driving system requisites for Wave 2 are satisfied before starting Wave 1, you can
combine Waves 1 and 2. But if you do this, be aware that several Wave 2 elements
have dependencies on the Wave 1A elements, so be sure to install the elements in
Wave 1A prior to or concurrently with (not after) the elements in Wave 2.

Driving System Wave 3

In Wave 3 you install the z/OS level of JES2 or JES3. Wave 3 is optional and can
be combined with Wave 1 or Wave 2.

The driving system requirements for Wave 3 are the same as for Wave 1. See
“Driving System Wave 1” on page 54.

Identifying Driving System Requirements to Install Subsystems

The driving system software required to install subsystems (DB2, CICS, IMS, and
NCP) using ServerPac is the same as the software in “Requirements to Load Data
Sets from the Installation Tapes” on page 48.

To use an OS/390 or z/OS release as the driving system for installing subsystems,
you might need to apply PTFs to the prior release. Refer to “Chapter 5. Ensuring
| Coexistence” on page 71 for SMP/E PTFs, and the subsystem program directories
for subsystem PTFs. Additionally, turn to the subsystem PSP buckets for any
updates. For ServerPac, the upgrade is ZOSV1R1 and the subset is SERVERPAC.
For SystemPac dump-by-data-set orders, the upgrade is CUSTOMPAC and the
subset is SYSPAC/DBD.

Identifying Driving System Hardware Requirements

In addition to the hardware needed to run a z/OS driving system and the DASD
required to install the software, you need:
v A TSO terminal, preferably a color terminal if you’re doing a ServerPac
installation because the ServerPac Installation Dialog uses color to identify key
information on panels.

Chapter 3. Preparing the Driving System 57

 v A tape device capable of reading one of the following:
– 3480 tape cartridges. If you choose 3480 compressed tapes, you must have
the Improved Data Recording Capability (IDRC) compression function on your
tape drives.
– 3490 enhanced capacity cartridges (for ServerPac and SystemPac orders
only).
– 3590 tape cartridges (for SystemPac orders only).
– 6250 reel tape.
v Sufficient central storage:
– For ServerPac and dump-by-data-set SystemPac installations, at least 94 MB
of central storage is required for test systems on which there is one interactive
TSO/E user and only the RESTFS job will run, or at least 42 MB of central
storage for systems supporting other workloads (plus whatever central storage
is needed to support the system’s normal workload).
– For CBPDO installations, the job samples use REGION=0M. A region value
equal to 0K or 0M gives the job all the storage available below and above 16
megabytes. Be aware that this can affect the performance of other jobs
running in the system. If you do not choose to run with a region size of 0M,
refer to z/OS SMP/E Reference for more information on how to determine
region sizes.

58 z/OS V1R1.0 Planning for Installation

 Chapter 4. Preparing the Target System
As described in the previous chapter, the target system is the system software
libraries and other data sets that you are installing. This chapter helps you identify
the software and hardware you will need for your target system.

Choosing Software Products to Install and Identifying Requisites

This task consists of:
v Choosing the z/OS base and optional features
v Identifying functional requisites for z/OS elements and features
v Choosing IBM products that you want to run with z/OS
v Choosing ISV products that you want to run with z/OS.

Choosing the z/OS Base and Optional Features

Because the base elements and optional features of z/OS are integrated into a
single package with compatible service levels, you must install, with few
exceptions, the entire z/OS product. The exceptions are:
v Elements and features that are already installed do not have to be reinstalled.
This would be the case (1) if you use the CBPDO installation method to migrate
to the current z/OS release and (2) an element or feature has not changed (its
FMID did not change), or an element or feature is nonexclusive and you’ve
already installed its functionally-equivalent stand-alone product version. To find
out whether any of your elements or features are in this situation, refer to the
migration tables in “Chapter 6. Preparing for Migration” on page 83.

| Note: In z/OS V1R1, only one base element changed (BCP) and two base
| elements are new (ILM and msys for Setup). For this reason, the z/OS
| V1R1 Upgrade Package for OS/390 R10 is provided for those migrating
| from OS/390 R10. The Upgrade Package consists only of the three base
| elements. All the other base elements and optional features are
| unchanged from OS/390 R10; there’s no need to reinstall them.
v Unpriced features that you didn’t order do not have to be installed.
v JES2, JES3, and SDSF do not have to be installed in the following cases:
– You don’t have to install JES2 if you are a JES3 customer. CBPDO installers
would just not install JES2. ServerPac and SystemPac installers can use jobs
provided by IBM to remove JES2 (and SDSF) during the final part of
installation.
Another reason why you don’t have to install JES2 is if you would rather use
the JES2 that you already have installed. However, you should migrate to
z/OS V1R1 JES2 as soon as possible to benefit from the new function in
z/OS V1R1 JES2 (as compared to OS/390 R8-R9 and earlier JES2) and to
enable other elements and features to benefit from the new level. See “Using
Your Existing JES2 or JES3 with z/OS V1R1” on page 65 for details about
using your older JES2.
– You don’t have to install JES3 if you are a JES2 customer. CBPDO installers
would just not install JES3. ServerPac and SystemPac installers can use jobs
provided by IBM to remove JES3 during the final part of installation.
Another reason why you don’t have to install JES3 is if you would rather use
the JES3 that you already have installed. However, you should migrate to
z/OS V1R1 JES3 as soon as possible to benefit from the new function in
z/OS V1R1 JES3 (as compared to OS/390 R9 and earlier JES3) and to

© Copyright IBM Corp. 1996, 2001 59

 enable other elements and features to benefit from the new level. See “Using
Your Existing JES2 or JES3 with z/OS V1R1” on page 65 for details about
using your older JES3.
– You don’t have to install SDSF if you are a JES3 customer. CBPDO installers
would just not install SDSF. ServerPac and SystemPac installers can use a
job provided by IBM to remove SDSF (and JES2) during the final part of
installation.

Failure to install the entire z/OS product, except for the exceptions described
above, could result in an unserviceable system until you install the entire
product.

You can use the Planning and Migration Assistant (part of SMP/E) to help you
determine what software is already on a system from which you’re migrating.

z/OS Alternate Base

Customers may have the ability to replace some of the z/OS base functions with a
commercially available product which provides similar functions. Contact an IBM
representative for qualification and pricing information. All z/OS integrated testing
results and performance claims will be voided with such replacement.

The mechanism IBM uses for this accommodation is an alternate base

configuration. One alternate base is defined and is supported by the price file and
the configurator. This alternate base, which contains the base elements with IP
Services (the component of base element Communications Server that provides
TCP/IP networking) disabled, is available for customers who have a commercially
available product that provides similar functions. In addition to not supporting IP
Services, the alternate base configuration does not support the following z/OS
optional features: Communications Server Security Level 1, Communications Server
Security Level 2, Communications Server Security Level 3, and Communications
Server NPF.

Identifying Functional Requisites for z/OS Elements and Features

The z/OS base elements represent an IPLable target system and satisfy most of
the dependencies of the z/OS elements and features. But some elements and
features require other features or IBM products that are not part of the z/OS base.
Moreover, some elements and features have optional dependencies on other
features or on IBM products that help you take full advantage of z/OS capabilities.
For a list of required and optional dependencies, see “Appendix B. Software
Requirements for z/OS Elements and Features” on page 201.

Choosing IBM Products That You Want to Run with z/OS

For a list of products available for ordering with z/OS, you can do any of the
following:
v Use the product catalogs on the Web (when available).
v Access the software configurator used in your country, select the z/OS
environment, and then select ServerPac, CBPDO, or SystemPac.
v Refer to “Appendix C. Minimum Levels of IBM Software Products That Run with
z/OS” on page 217.

Many of these products can be ordered as part of your z/OS ServerPac order, z/OS
SystemPac order, separate CBPDO order, or separate ProductPac order.

60 z/OS V1R1.0 Planning for Installation

 If you’re migrating to z/OS V1R1 from an OS/390 release, you can find out which
products have new levels by using the ShopzSeries Web application or by using the
SMP/E base element’s Planning and Migration Assistant. Both tools use data found
on your system as well as the latest IBM software product catalog. For
ShopzSeries, go to:
https://inetsd01.boulder.ibm.com/ShopzSeries/ShopzSeries.jsp

Choosing ISV Products That You Want to Run with z/OS

| For a directory of independent software vendors (ISVs) and products that support
| z/OS and OS/390, see:
| http://www.ibm.com/software/solutions/isv/igssg.nsf/LanguageSelector/?OpenForm

| For information about compatibility between ISV products and z/OS, go to the
| following Web address. It includes ISV-provided compatibility information for IBM’s
| new hardware architecture. This information is voluntary and is provided at the
| discretion of the ISVs. The list of ISVs represented will continue to evolve as
| vendors assess their products for z/Architecture support.
| http://www.ibm.com/eserver/zseries/solutions/s390da/osnp.html

| Note that you can use SystemPac to get some ISV products on system delivery
vehicles with IBM products. For a list of selectable ISVs with SystemPac, see:
http://www.ibm.com/ca/custompac/

Ordering z/OS and Related IBM Products

You can order software products by using the self-service Web application
ShopzSeries, by using IBMLink, or by contacting an IBM representative. You can
find ShopzSeries at:
https://inetsd01.boulder.ibm.com/ShopzSeries/ShopzSeries.jsp

When ordering upgrades to software products for which you’re currently licensed,
you can generate an SMP/E report of installed software to be upgraded, and upload
the report to ShopzSeries. ShopzSeries selects upgrades and performs technical
requisite checking. ShopzSeries then lets you submit the order and track it through
delivery.

IBM refreshes ServerPac and SystemPac monthly. However, the ServerPac and
SystemPac checklists might not contain the most current releases of all products
that run on z/OS. If the release of the product you want is not available in
ServerPac or SystemPac, IBM recommends that you:
1. Order ServerPac or SystemPac, omitting products not at the appropriate level.
2. Order CBPDO or ProductPac with those products you omit from ServerPac or
SystemPac.
3. Install the ServerPac or SystemPac order, and then install the products from the
CBPDO or ProductPac.

Consider selecting distribution tapes that have the greatest capacity, provided you
have the hardware capability on your cartridge drive. 3490 enhanced capacity tapes
are the most dense, followed by 3480 compressed tapes and then 3480 standard
tapes. Reducing the number of tapes you receive reduces the number of tapes you
have to handle and reduces the processing time required to read the tapes. For
comparison, the quantities of tape cartridges required to fulfill an average
ServerPac order are:
v 3480 standard tape: about 35 cartridges

Chapter 4. Preparing the Target System 61

 v 3480 compressed tape: about 18 cartridges
v 3490 enhanced capacity tape: about 8 cartridges

| Ordering the z/OS V1R1 Upgrade Package for OS/390 V2R10

| The z/OS V1R1 Upgrade Package for OS/390 V2R10 is a deliverable provided
| exclusively for those migrating from OS/390 R10 to z/OS V1R1. Its purpose is to
| provide a quick and easy upgrade to the first release of z/OS. It consists of two new
| base elements (ILM and msys for Setup) and one updated base element (BCP). All
| the other base elements and optional features are unchanged from OS/390 R10;
| there’s no need to reinstall them.

| You need to obtain a license for z/OS V1R1, specifying the priced and unpriced
| optional features that were in use for OS/390 V2R10. You can then order the
| Upgrade Package (an unpriced optional feature), which provides the additional new
| z/OS V1R1 code in CBPDO format. The Upgrade Package is only for use by
| OS/390 V2R10 licensees, and for use in migrating to z/OS V1R1. The Upgrade
| Package installs like a monthly RSU service upgrade.
|

| Important service consideration

| Although you may specify the CBPDO product-only option when ordering the
| Upgrade Package, this will restrict the delivery of service to just the Upgrade
| Package (that is, service for elements BCP, msys for Setup, and ILM). It is
| highly recommended that you upgrade service for the entire OS/390 R10
| product at the time you install the Upgrade Package. This will ensure that you
| are at the minimum service level that was integration tested by IBM.
| Therefore, you should choose the CBPDO selective service option when
| ordering the Upgrade Package. This will provide you with service for OS/390
| R10, the Upgrade Package, and other products in your ordering profile.
|
|
|
Identifying Hardware Requirements for the Target System
This task consists of:
v Identifying processor requirements.
v Identifying DASD space requirements.
v Identifying I/O device requirements.
v Identifying additional hardware needed by z/OS elements and features. See
“Appendix D. Hardware Requirements for z/OS Elements and Features” on
page 229.

Note: For general information about requirements for a Parallel Sysplex

configuration, see the zSeries Parallel Sysplex Customization Wizard at:
| http://www.ibm.com/servers/eserver/zseries/zos/bkserv/wizards.html

Identifying Processor Requirements

| z/OS V1R1 takes advantage of architectural enhancements that were introduced
| with the S/390 Multiprise 3000 Server and with G5 of the S/390 servers. The
| architectural enhancements provide performance, function, and reliability
| improvements. z/OS V1R1 runs only on servers that implement the enhancements.
| The IBM servers are:
| v IBM ^ zSeries 900 (z900)
| v IBM S/390 Parallel Enterprise Server – G5 and G6
| v IBM S/390 Multiprise 3000 (all models)

62 z/OS V1R1.0 Planning for Installation

| The architectural enhancements required by z/OS V1R1 can be found at:
| http://www.ibm.com/s390/os390/plug1.html

| Processor Storage
| When z/OS runs on a z900 server, z/OS must be in 64-bit (z/Architecture) mode, as
| specified by the ARCHLVL statement of parmlib member LOADxx (or by default).
| Expanded storage is not supported in z/Architecture. Thus, you must configure your
| LPAR to use only central storage (and not expanded storage). You can still use
| local page data sets, but because you can have more real storage in z/Architecture,
| less paging is likely to be needed.

The minimum processor storage required to IPL z/OS depends on a number of

factors, including:
v The number of devices in the I/O configuration
v The amount of storage configured
v The number of address spaces created
v The types of applications supported
v The products and subsystems supported in the IPLed system

| In studies at IBM, OS/390 R8, R9, and R10 systems, and a z /OS V1R1 system,
were IPLed to the point of completing JES initialization. In each case, 24 MB of
processor storage was required to IPL. These systems had I/O configurations
defined with the following devices:
Device Quantity
3270 32
3390 1152
3490 16

PSP Hardware Upgrade Identifiers

For the latest hardware dependencies related to z/OS, including any APARs
required for specific processor models, obtain current PSP information (from PSP
“buckets”). You can obtain PSP information using IBMLink or Information/Access, or
request it from your IBM Support Center.

The PSP hardware upgrade identifiers are:

| v For the z900 server, the PSP upgrade identifier is 2064DEVICE.
v For the S/390 Parallel Enterprise Server, the PSP upgrade identifier is
9672DEVICE.
v For the S/390 Multiprise 3000, the PSP upgrade identifier is 7060DEVICE.

Identifying DASD Space Requirements

The DASD required for z/OS includes:
v All elements
v All features that support dynamic enablement, regardless of your order
v All unpriced features that you ordered.

The storage requirements for z/OS are shown in Table 5. Products that run on z/OS
will require additional storage.
Table 5. DASD storage requirements for all z/OS V1R1 elements and features
Data sets or storage 3390 cylinders
| Target data sets listed in the space table in z/OS V1R1.0 Program 4900
Directory

Chapter 4. Preparing the Target System 63

 Table 5. DASD storage requirements for all z/OS V1R1 elements and features (continued)
Data sets or storage 3390 cylinders
Distribution data sets listed in the space table in z/OS V1R1.0 4684
Program Directory
HFS root (/) file system (primary, secondary) 950, 140
HFS /etc file system (primary, secondary) 50, 10
SMP/E data sets (excluding SMPPTS) listed in the space table in 1023
z/OS V1R1.0 Program Directory

The size of the SMPPTS data set depends on factors including the
number of products previously ordered, the number of products and
optional unpriced features in this order, and the date the order was
placed. For ServerPac and SystemPac (dump-by-data-set format),
the installation dialog specifies the expected size.
SMPTLIB data sets allocated during SMP/E RECEIVE processing 5802
for z/OS FMIDs shipped on a CBPDO (but note that optional
features and national language FMIDs require additional storage)

Identifying I/O Device Requirements

| Use of the 2105 Enterprise Storage Server with z/OS requires the 2105 microcode
| to be at EC fix level F25584 or later. This EC level fixes a problem caused by z/OS
| exploitation of the SII/RND CCW commands.

For a description of the I/O devices supported by z/OS, see:

v z/OS DFSMS Introduction
v GDDM General Information
v z/OS MVS Planning: Operations (for devices that can be used as consoles)

z/OS supports ESA/390, ESCON, and FICON devices.

For a table summary of device information, including information about dynamic,

4-digit, and above-16-megabyte UCB device support, see z/OS MVS Device
Validation Support.

Identifying Service Needed for the Target System

Before you IPL the target system for the first time, you should determine whether
your target system software is at the appropriate service level, and apply fixes if it is
not. This section explains the additional service that you might need to apply.

See “Service” on page 28 for background information on the service that is shipped
with ServerPac, CBPDO, and SystemPac orders. See “Maintenance after
Installation” on page 31 for guidance on applying maintenance to your z/OS system
after you have finished installing it.

If You Are Installing a ServerPac Order...

If you install your ServerPac order shortly after it arrives, you should not need to
install additional RSU service. It should already be included in your order.

But if more than a few weeks have passed since your order arrived:
v Consult ServerPac: Installing Your Order, in the topic about service included in
your order, to find the service level of the system as shipped.

64 z/OS V1R1.0 Planning for Installation

 v Order a service package, such as an ESO, RefreshPac, or service-only CBPDO,
using a starting service level one month later than the level identified in
ServerPac: Installing Your Order.

If You Are Installing a CBPDO Order...

If you ordered z/OS as a CBPDO package:
| v Install all PTFs with a SOURCEID of ZOSV1R1. In addition, install all PTFs with
a SOURCEID of HIPER or PRP provided they are not in a PTF-in-error (PE)
chain.
v Consult Memo to Users Extension to find the service level of the system as
shipped.
v If more than a few weeks have passed since your order arrived, there should be
a service package available; order and apply it in accordance with the guidelines
in “Maintenance after Installation” on page 31. Use the service delivery vehicle
that you prefer, such as CBPDO, ESO, or SUF.

If You Are Installing a SystemPac Order...

IBM strongly recommends that you select, during order entry, the optional follow-on
services (SFSs) that come with the SystemPac. SFSs contain critical service
information: PTFs that resolve PEs and HIPERs that are discovered after your
system is built. The SFSs you get are tailored to the image of the SMP/E CSI of the
system that IBM shipped to you earlier. By installing repeating SFSs (at most 90
days apart, maximum of three), you stabilize the system you installed, thus enabling
you to have a system with higher availability for your applications.

SFSs can be installed via the CustomPac Installation Dialog or via batch JCL.

Using Your Existing JES2 or JES3 with z/OS V1R1

We recommend that you migrate to the JES2 or JES3 that comes
comprehensively-tested with z/OS V1R1 at the same time you migrate to the rest of
z/OS V1R1, or as soon as possible thereafter. In this way, you benefit directly from
the new function in the z/OS V1R1 level of JES2 or JES3 (as compared to OS/390
R8-R9 and earlier JES2, and OS/390 R9 and earlier JES3) and enable other
elements and features to benefit from this level. However, because such a migration
is not always practical, certain prior levels of JES2 and JES3 are supported with
z/OS V1R1 so that you can stage your migration to z/OS V1R1 (that is, migrate
your JES2 or JES3 later).

The rest of this section describes the levels of JES2 and JES3 that are supported,
the service they require, and other details required to use your current JES2 or
JES3 with z/OS V1R1 until you can migrate to z/OS V1R1 JES2 or JES3.

Allowable JES-BCP Combinations

The JES levels supported by a given z/OS release are the same as the JES levels
that may coexist in the same multi-access spool (MAS) or multisystem complex with
the JES delivered in that z/OS release. That is, the JES levels that may run on the
latest z/OS release (when run on either a single system or on individual systems
participating in a multisystem configuration) are the four most recent JES levels.

| Thus, the JES releases you can use with the z/OS V1R1 BCP are:
| v JES2:
| – OS/390 R6 JES2

Chapter 4. Preparing the Target System 65

| – OS/390 R7 JES2
| – OS/390 R8-R9 JES2 (both are functionally equivalent)
| – OS/390 R10 JES2 - z/OS V1R1 JES2 (both are functionally equivalent)
| v JES3:
| – OS/390 R6-R7 JES3 (both are functionally equivalent)
| – OS/390 R8 JES3
| – OS/390 R9 JES3
| – OS/390 R10 JES3 - z/OS V1R1 JES3 (both are functionally equivalent)

For an explanation of the coexistence policy as it pertains to JES2 and JES3, see
“Coexistence Policy” on page 72.

JES Data Compatibility

| Data created by one JES level can be used and manipulated by a later level, and
| vice versa. The spool and queue control constructs are compatible between any
| two supported releases of JES2 or JES3 for at least n-5 releases of the operating
| system, where n is the current release. (This is not n-5 JES FMIDs.) Thus, you are
| assured that data created by OS/390 R6, R7, R8, R9, or R10 JES2 can be used
| and manipulated by z/OS V1R1 JES2, and data created by OS/390 R6, R7, R8,
| R9, or R10 JES3 can be used and manipulated by z/OS V1R1 JES3.

Note that this statement of data compatibility has nothing to do with determining
which levels of JES can access the data at the same time; this is governed by the
coexistence policy (see “Coexistence Policy” on page 72). Also note that there is no
guarantee that you will be able to move back to an earlier release if you have used
new functionality in the later release.

Service Required to Use Your Existing JES2 or JES3

In order to use your existing JES2 or JES3 with z/OS V1R1, apply the same PTFs
that are required for coexistence service. See “JES2 Coexistence Service” on
page 81 or “JES3 Coexistence Service” on page 81. Apply the PTFs before you IPL
z/OS.

ServerPac and SystemPac Delivery of JES2, JES3, and SDSF

Only the latest levels of JES2, SDSF, and JES3 are delivered in ServerPac and
SystemPac (and CBPDO). In ServerPac and SystemPac, JES2 and SDSF are
distributed in separate target and DLIB zones from z/OS; JES3 is also distributed in
separate target and DLIB zones from z/OS. Optional jobs are provided in the
CustomPac Installation Dialog (used by ServerPac and SystemPac) so that when
you install z/OS you can merge JES2 and SDSF, or JES3, into the z/OS zone. This
zone structure allows you to use the new JES2 and SDSF, or JES3, or your existing
levels of JES2 and SDSF, or JES3.

With ServerPac or SystemPac, JES2 customers can use a ServerPac or

SystemPac job (during installation) to delete the JES3 zone and data sets. Similarly,
JES3 customers can use a ServerPac or SystemPac job (during installation) to
delete JES2 and SDSF. If you intend to run any of these jobs, you cannot run the
ServerPac or SystemPac job to merge the JES zone you intend to delete.

z/OS V1R1 SDSF comes assembled with the latest JES2 macros; JES2 and JES3
come as shipped by IBM. (See z/OS V1R1.0 Program Directory for information on
the macro levels that are used by IBM to create and service JES2 and JES3.)

66 z/OS V1R1.0 Planning for Installation

Placing Your Existing JES2 or JES3 in a Separate Zone
To use your existing JES2 or JES3, you must consider SMP/E zone structure and
SMP/E SYSLIB concatenation, and their impact on:
v Integrity of other load modules in the z/OS environment
v Your maintenance procedures
v Your ability to upgrade from your existing JES to the latest z/OS level of JES
v Your ability to upgrade to a new z/OS level while continuing to use your existing
level of JES

We recommend that you not install an earlier level of JES2 or JES3 in the same
zones as z/OS. If you intend to use a previously-installed level of JES, you should
place it in separate SMP/E target and DLIB zones. In this way, you are
well-positioned to:
v Ensure integrity of both the JES and non-JES load modules
v Eliminate manual post-install assemblies for maintenance (especially for SDSF
users)
v Upgrade your existing JES to z/OS V1R1 JES
v Continue to run your existing JES while upgrading z/OS to a later level

Use the following procedure to separate your existing JES2 or JES3 from its
existing SMP/E environment. Use this procedure only if your existing JES is not
already in a separate zone.
1. Follow the installation procedures in the program directory supplied with your
level of JES2, using any corrections listed in the PSP upgrade and subset it
identifies for the JES2 component.
2. ACCEPT (or RESTORE) all unaccepted service and USERMODS for JES2 or
JES3.
3. Use the SMP/E BUILDMCS command to create an SMP/E installable image of
your existing JES
The BUILDMCS command builds an SMP/E installable image from information
in the target and distribution zones and the code in the distribution libraries.
Therefore all code must be ACCEPTed or RESTOREd (and then re-APPLYed).
4. Define new SMP/E zones for JES2 or JES3
5. Allocate separate target and distribution libraries for JES2 or JES3.
z/OS levels of JES2 and JES3 provide sample allocation jobs which can be
used to allocate that level of the libraries or as a model for non-z/OS levels of
JES.
6. Define SMP/E DDDEFs for the new target and distribution libraries for JES2
and JES3.
z/OS levels of JES2 and JES3 provide sample DDDEF jobs which can be
used to define those levels of the libraries or as a model for non-z/OS levels of
JES.
7. If you do source-code maintenance (++SRC/++SRCUPD) rather than
object-code maintenance (++MOD) for JES, define the SYSLIB macro
concatenation for new zones.
The macro concatenation to be used for assemblies in the new zone must be
defined to SMP/E. You have three choices of which macro libraries to use:
v Use the z/OS V1R1 macro libraries and your existing JES macro libraries.
v Continue to use the BCP, DFSMSdfp, and Communications Server–SNA
Services macro libraries that your existing JES2 or JES3 is using.

Chapter 4. Preparing the Target System 67

 v Use the macro levels that are used by IBM to create and service JES2 and
JES3. See the z/OS V1R1.0 Program Directory for additional considerations
for this option.

IBM recommends that you use the same level of macros for all production
systems in your complex using the existing JES level. That is, the JES2 used
on all systems in a JES2 MAS environment should be assembled with the
same operating system macros (the lowest level BCP, DFSMS/MVS, and
VTAM macros should be used). You must never assemble JES2 with macro
levels lower than those it was originally assembled with by IBM (higher is
acceptable). If you follow this recommendation you can use the same load
libraries on all systems. You can use different libraries for assemblies (and
different target libraries) during migration or testing. Once all systems have
migrated to z/OS V1R1, you should consider reassembling using the z/OS
V1R1 macros. If you reassemble one module, you must reassemble the entire
element. (Sample SMP/E USERMODS are provided.) For more information on
assembling JES2 or JES3, see the post-installation steps in the z/OS V1R1.0
Program Directory.

If you do object-code maintenance (++MOD) rather than source-code

maintenance (++SRC/++SRCUPD) for JES, the only assembling you need to
be concerned with is assembling your exit routines. You need to make sure
that:
v You use the same SPLEVEL to assemble your exit routines that IBM used
to assemble JES.
v The release level used to assemble your exit routines isn’t below the
release level used to assemble JES. (For example, you can’t use OS/390
R6 BCP macros to assemble z/OS V1R1 JES2 exit routines.)
8. RECEIVE, APPLY and ACCEPT the SMP/E installable image built by the
BUILDMCS command into the new separate zones.
9. If you chose to do the RESTORE in Step 1, reAPPLY any service that was
RESTOREd.
10. Make the necessary updates to use the copy of JES2 or JES3 in the new
libraries:
v Update the catalog(s) with the names of the existing JES new data sets
v Update PROGxx (or LNKLSTxx and IEAAPFxx) members of parmlib
v Update the JES2/JES3 cataloged procedure, if STEPLIBs are used
v Add the JES parmlib to the system’s parmlib concatenation, or copy the
IPCS parmlib members from the JES parmlib to the system parmlib.
v If you are using JES3, add the modules in the SIATLPA library to LPA or
dynamic LPA by updating an LPALSTxx or PROGxx member of parmlib. (If
you choose to use dynamic LPA for JES3 modules, the SET PROG
command used to add them must complete before JES3 initialization
begins.)

Using z/OS V1R1 SDSF with Your Existing JES2

To use z/OS V1R1 SDSF with your existing JES2, you have to copy the new SDSF
from the JES2 zone (as distributed in ServerPac and SystemPac) using the
BUILDMCS command. No extra steps are required to use z/OS V1R1 SDSF with
the new JES2.

68 z/OS V1R1.0 Planning for Installation

 Use the following procedure to copy z/OS V1R1 SDSF from the distributed JES2
zone to your existing JES2 SMP/E environment. Use this procedure only if you
want to use z/OS V1R1 SDSF with your existing JES2.
1. ACCEPT (or RESTORE) all service and USERMODS for SDSF (if any service
or customization was performed)
2. Use the SMP/E BUILDMCS command to create an SMP/E installable image of
the new SDSF
3. Allocate separate target and distribution libraries for SDSF; a sample job is
provided.
4. Define SMP/E DDDEFs for the new target and distribution libraries for SDSF; a
sample job is provided.
5. Add the SDSF macro library to the SYSLIB macro concatenation of your
existing JES2 zone.
SDSF needs the SISFSRC macro library in the target zone SYSLIB
concatenation for assemblies. SDSF needs the AISFSRC macro library in the
DLIB zone SYSLIB concatenation for assemblies.
6. RECEIVE, APPLY and ACCEPT the SMP/E installable image built by the
BUILDMCS command into your existing JES2 SMP/E zone.
SDSF will be assembled during the APPLY. Therefore, make sure that different
load libraries are used in this zone than the ones that were distributed with
ServerPac or SystemPac.
7. If you chose to do the RESTORE in Step 1, reAPPLY any service that was
RESTOREd.
8. Make the necessary updates to use the copy of SDSF in the new libraries:
v Update the catalog(s) with the names of the new SDSF data sets
v Add the modules in the SISFLPA library to LPA or dynamic LPA by updating
an LPALSTxx or PROGxx member of parmlib.
v Add the new SISFLINK library to the Link List in a LNKLSTxx or PROGxx
member of SYS1.PARMLIB
v Add the new SISFLINK and SISFLOAD libraries to the APF List in a PROGxx
or IEAAPFxx member of SYS1.PARMLIB
v Update the TSO logon cataloged procedures to include new SDSF libraries.
9. Automate SDSF reassembly during installation of JES2 service.
SDSF provides sample UCLIN jobs that cause SMP/E to reassemble SDSF
whenever maintenance affects JES2 macros. There is a sample job for each
JES2 environment provided in the SISFJCL library.

Migrating Your Existing JES2 or JES3 to z/OS V1R1 Level

To migrate from your existing JES2 or JES3 to z/OS V1R1 JES2 or JES3, follow
these steps:
1. Customize the z/OS V1R1 JES2 or JES3, reworking USERMODS and exits,
and making sure service is not regressed.
2. Update operational procedures to use z/OS V1R1 JES2 or JES3.
To use the libraries for z/OS V1R1 JES2 or JES3:
a. Update the catalog(s) with the names of the existing JES2 or JES3 new
data sets.
b. Update PROGxx (or LNKLSTxx and IEAAPFxx) members of parmlib.
c. Update the JES2 or JES3 cataloged procedure, if STEPLIBs are used.

Chapter 4. Preparing the Target System 69

 d. Add the new SIATPARM or SHASPARM data set to the parmlib
concatenation, or copy the IPCS parameter members from SIATPARM or
SHASPARM to a parmlib already in the concatenation.
e. If you are using JES3, add the modules in the SIATLPA library to LPA or
dynamic LPA by updating an LPALSTxx or PROGxx member of parmlib. (If
you choose to use dynamic LPA for JES3 modules, the SET PROG
command used to add them must complete before JES3 initialization
begins.)
3. When you are sure z/OS V1R1 JES2 or JES3 works, remove the zone(s) that
hold your existing JES, deleting the old libraries, removing pointers to old JES
data sets from your parmlib members, catalog(s), and IPCS settings.
4. If you plan to migrate to subsequent releases of JES2 or JES3 when you
migrate to the next level of z/OS, then IBM recommends you run the job
provided in ServerPac or SystemPac to merge the JES2 (and SDSF) or JES3
elements into the z/OS zone. If you plan continue to stagger your z/OS and JES
migrations, you should not run this job.

See also “Migration Actions for JES2” on page 147.

70 z/OS V1R1.0 Planning for Installation

Chapter 5. Ensuring Coexistence
Coexistence 2 occurs when two or more systems at different software levels in a
multisystem configuration share resources at the same time. For example, two
different JES releases could share a spool, two different service levels of
DFSMSdfp could share catalogs, multiple levels of SMP/E could process SYSMODs
packaged to exploit the latest enhancements, or an older level of the system could
use the updated system control files of a newer level (even if new function has
been exploited in the newer level).

Multisystem configurations involving Parallel Sysplex implementations inherently

involve the sharing of resources. For other types of multisystem configurations, it is
also possible to have resource sharing. Examples of multisystem configurations
where resource sharing can occur include:
v A single processor that is time-sliced to run different levels of the system, such
as during different times of the day
v A single processor running multiple images by means of logical partitions
(LPARs)
v Multiple images running on several different processors
v Parallel Sysplex or non-Parallel Sysplex configurations

Note: The term coexistence does not refer to z/OS residing on a single system
along with VSE/ESA, VM/ESA, or z/VM in an LPAR or as a VM guest.

Certain OS/390 systems can coexist with z/OS V1R1 systems. This is important
because it gives you flexibility to migrate systems in a multisystem configuration to
z/OS V1R1 using rolling IPLs rather than requiring a systems-wide IPL. (For more
information about rolling IPLs, see “Rolling z/OS across a Multisystem
Configuration” on page 161.) Coexistence PTFs, installed on the earlier-level
systems, are the primary means for allowing earlier-level systems to coexist with
later-level systems.

Even though it is possible for certain OS/390 systems to coexist with z/OS V1R1
systems, you should complete the migration of all earlier-level systems to z/OS
V1R1 as soon as you can. Keep in mind that the objective of coexistence PTFs is
to allow existing functions to continue to be used on the earlier-level systems when
run in a mixed environment that contains later-level systems. Coexistence PTFs are
not aimed at allowing new functions provided in later releases to work on
earlier-level systems.

This chapter helps you ensure that earlier-level systems will successfully coexist
with z/OS V1R1. Use this chapter as follows:
1. Read IBM’s coexistence policy (“Coexistence Policy” on page 72) to understand
which OS/390 and z/OS releases may coexist in a multisystem configuration
and to understand important information regarding coexistence and release
migrations in the future.
2. Determine which coexistence service (PTFs) to apply. You apply the service on
“other” systems in your multisystem configuration, that is, on systems that will
coexist with your new z/OS V1R1 system. Topics that describe the coexistence
service for systems that fall within the allowable coexistence period are:

2. In some documentation you might find the terms “compatibility” or “toleration” used instead of “coexistence”.

© Copyright IBM Corp. 1996, 2001 71

 v “OS/390 R6 Coexistence Service” on page 74
v “OS/390 R7 Coexistence Service” on page 76
v “OS/390 R8 Coexistence Service” on page 78
v “OS/390 R9 Coexistence Service” on page 79
| v “OS/390 R10 Coexistence Service” on page 80

Note: There is a case in which you might require coexistence service even
though you have a single-system configuration, not a multisystem
configuration. If your system shares data or data structures (such as user
catalogs) as you shift a single image from production to test and back
again, the later-level release might make changes that are incompatible
with the earlier-level release. In this case, coexistence service on the
earlier-level release can allow it to tolerate changes made by the
later-level release. As a general reminder, always plan to have a backout
path when installing new software by identifying and installing any
service required to support backout.
3. Determine which fallback service (PTFs) to apply. You apply the service on the
system that you are migrating to z/OS V1R1, in the event that you have to back
off (fall back) to the prior level of this system. Fallback would be necessary if,
during testing of your new z/OS V1R1 system, you experience severe problems
that can only be resolved by backing out the new release. The PTFs make
fallback safe in spite of all the changes that occurred during testing.

Note: Keep in mind that new functions can require that all systems be at z/OS
V1R1 level before the new functions can be used. Therefore, be careful
not to exploit new functions until you are fairly confident that you will not
need to back out your z/OS V1R1 systems, as fallback maintenance is
not available in these cases. You should consult the appropriate z/OS
element or feature documentation to determine the requirements for
using a particular new function.
4. Determine what service to apply to JES2 or JES3. See “JES2 Coexistence
Service” on page 81 or “JES3 Coexistence Service” on page 81.
5. Refer to PSP buckets for any last-minute items that didn’t make it into this book.

Coexistence Policy
To give you optimum compatibility and flexibility as you migrate systems in a
multisystem configuration to z/OS V1R1, the z/OS coexistence policy allows certain
earlier-level releases to coexist with z/OS V1R1. This policy lets you, for example,
do rolling IPLs to migrate to z/OS V1R1; you do not have to cut over all systems in
your multisystem configuration at the same time.

The coexistence policy is as follows:

| v The operating system: Normally, four consecutive releases of z/OS and its
| predecessor, OS/390, may coexist in a multisystem configuration. Thus, the
| normal period for coexistence is a maximum of two years, based on the current
| six-month release cycle.
| However, two special provisions, when taken together, make an exception to the
| general rule, such that six specific releases may coexist with z/OS V1R1. First,
| OS/390 R10 and z/OS V1R1 are being treated as a single coexistence level,
| rather than two coexistence levels, due to the unique relationship between
| OS/390 V2R10 and z/OS V1R1. Second, OS/390 R6 is coexistence-supported
| with OS/390 R10.

72 z/OS V1R1.0 Planning for Installation

| As a result, the following six releases may coexist with z/OS V1R1: OS/390 R6,
| OS/390 R7, OS/390 R8, OS/390 R9, OS/390 R10, and z/OS V1R1.
v The JESes: JES2 and JES3 are treated a bit differently than the rest of the
operating system. While the four-consecutive-release coexistence policy does
apply to both JES2 and JES3, the fact that JES installation can be staged has
been taken into account in determining which are the four consecutive releases
that may coexist. If a JES2 or JES3 release is functionally equivalent to its
predecessor (that is, its FMID did not change), then from a coexistence
standpoint this is considered the same JES release. To be specific:
| – JES2: The following JES2 releases may coexist with z/OS V1R1 JES2 in the
| same multi-access spool (MAS):
| - OS/390 R6 JES2
| - OS/390 R7 JES2
| - OS/390 R8-R9 JES2 (both are functionally equivalent)
| - OS/390 R10 JES2 - z/OS V1R1 JES2 (both are functionally equivalent)
| – JES3: The following JES3 releases may coexist with z/OS V1R1 JES3 in the
| same multisystem complex:
| - OS/390 R6-R7 JES3 (both are functionally equivalent)
| - OS/390 R8 JES3
| - OS/390 R9 JES3
| - OS/390 R10 JES3 - z/OS V1R1 JES3 (both are functionally equivalent)

IBM performs integration testing and will provide service as necessary to support
the z/OS coexistence policy.
Notes:
1. Policy applies to operating system only: The z/OS coexistence policy applies
to the elements and features of OS/390 and z/OS, not to customer-developed
applications, vendor-developed applications, or IBM products that run on
OS/390 or z/OS. For coexistence considerations that apply to IBM products that
run on OS/390 or z/OS, consult their planning and migration publications. For a
list of the IBM products, see “Appendix C. Minimum Levels of IBM Software
Products That Run with z/OS” on page 217. For information related to
application development on multiple levels of OS/390 or z/OS, see “Migrating
Your Application Development Environment” on page 138.
2. Coexistence and service lengths not the same: There is a difference
between how long IBM will ensure coexistence within a multisystem
configuration and how long a release is serviced. For information about the
latter, see “Service Policy” on page 28. You will notice that service support is
provided for three years following a release’s availability while coexistence
support is provided for two years (based on the four consecutive release
coexistence policy and a six month release cycle). This allows those who order
a release near the end of a two-year coexistence period enough time to roll out
the release across their enterprise without service expiring.
3. Coexistence in the future: Starting with z/OS V1R1 and continuing with
subsequent z/OS releases, the coexistence policy applies to all z/OS customer
configurations. It applies to single-system configurations (regardless of whether
resource sharing is present) as well as multisystem configurations. The previous
policy (before z/OS V1R1) applied only to multisystem configurations.
| 4. Migration in the future: When you migrate from z/OS V1R1 (or from any
| subsequent release), the release you migrate to is required to be within four
| consecutive releases (or within releases provided by any special provisions) to
| be fully supported. That is, migration forward and backward must be made
| within four consecutive releases.

Chapter 5. Ensuring Coexistence 73

 OS/390 R6 Coexistence Service
Apply, on OS/390 R6 systems, the coexistence service that is shown in Table 6.
Table 6. Coexistence service (PTFs) needed on OS/390 R6 systems
Element or feature, and reason service is needed OS/390 R6 PTFs
| BCP: Lets OS/390 R6 systems tolerate the automatic UW73392
restart management (ARM) support for Transactional
Services for VSAM introduced in OS/390 R9
| BCP: As of OS/390 R10, GRS (global resource UW72166
serialization) provides improvements to Parallel
Sysplex-wide contention management via PTFs for APAR
OW36418. Before a system with improved contention
management is activated, you must apply coexistence
service to all systems in the Parallel Sysplex. Note, in
addition, that for the improved contention management to
take effect, the PTFs for APAR OW36418 must be applied
to all systems in the Parallel Sysplex.
BCP: Allows the logger to do multiple reads from large UW71044
buffers for log data. This PTF does not have to be installed
on all systems within a Parallel Sysplex before z/OS V1R1
is IPLed into the sysplex.
BCP: Allows OS/390 R6 systems in a Parallel Sysplex UW63194 or, if Japanese,
configuration to participate in sysplex-wide monitoring that UW63527
may be triggered by an OS/390 R10 or later system that
supports structure full monitoring
BCP: Ensures compatibility with the RRS cascaded UW67817
transaction support introduced in OS/390 R9
BCP: As of OS/390 R10, there is new 32 KB block size UW69769
support and unit affinity support. This scheduler PTF allows
jobs that do not request the new functions to run
successfully when the jobs are submitted on OS/390 R10 or
later but routed by JES3 for execution on earlier OS/390
levels.
| BCP: Supports the coexistence of prior levels of the UW77469 or, if Japanese,
| console services components with z/OS V1R1 and later UW77472
| systems in a Parallel Sysplex configuration.
BCP: Supports the coexistence of prior levels of WLM with UW70999
OS/390 R10 and later systems in a Parallel Sysplex
configuration
BCP: Lets OS/390 systems prior to R8 tolerate Parallel UW58109
Sysplex XES functions introduced in OS/390 R8. These
functions involve system-managed rebuild and the CFRM
couple data set.
| Cryptographic Services: Allows pre-OS/390 R10 systems UW73741
to share an ICSF cryptographic key data set (CKDS) with
an OS/390 R10 or later system (once key types of
IMPORTER, EXPORTER, PINGEN, PINVER, IPINEC, or
OPINENC, which have non-CCF control vectors, are added
to the CKDS)
DFSMSdfp data management ISO/ANSI tape UW73477
DFSMSdfp HFS performance UW56092, UW59990,
UW64189
DFSMSdfp diagnose for sysplex alias UW67877

74 z/OS V1R1.0 Planning for Installation

 Table 6. Coexistence service (PTFs) needed on OS/390 R6 systems (continued)
Element or feature, and reason service is needed OS/390 R6 PTFs
| DFSMSdfp ICF catalog, to prevent access to ECS-eligible UW75735
catalogs
DFSMSdfp VSAM UW49423, UW50704,
UW54391, UW58414,
UW59981
DFSMSdfp SMS CDS sharing with OAM sysplex UW52117
modifications
DFSMSdfp SMS OAM Parallel Sysplex support UW52467
Allows FAMS users on DFSMSdfp to obtain attributes, UW56092
unload, or use TSO XMIT to transmit a PDSE data set to a
system running OS/390 R10
DFSMSdfp: Allows pre-OS/390 R10 systems to tolerate UW61953, UW62976,
records created on OS/390 R10 and later systems with UW63365 (or, if DFSMS/MVS
block sizes greater than 32 KB V1R5: UW61954, UW62977,
UW63366)
DFSMSdfp: Enables VSAM data sets to be striped across UW67758 (or, if DFSMS/MVS
multiple volumes V1R5: UW67759)
DFSMSdss VSAM extended format data sets UW45594
DFSMSdss multivolume HFS UW50590
Allows users on DFSMSdss to recall files that were UW59316
migrated to a system running OS/390 R10 or later
DFSMShsm single GRSplex serialization (SGS) UW54938
DFSMShsm: Allows pre-OS/390 R10 systems to tolerate UW68027 (or, if DFSMS/MVS
records created on OS/390 R10 and later systems with V1R5: UW68028)
block sizes greater than 32 KB
| DFSMShsm: Supports up to 64 concurrent command data UW67974 (or, if DFSMS/MVS
| set backups to either ML1 DASD or tape. This enhancement V1R5: UW73892)
increases the rate at which DFSMShsm can perform
command data set backups and allows more batch
applications to take advantage of it.
DFSMSrmm expanded CDS records UW40985
| DFSMSrmm enhancements UW70794
DFSMSrmm: Allows pre-OS/390 R10 systems to use the UW57639 (or, if DFSMS/MVS
import/export function when sharing a virtual tape server V1R5: UW57640)
(VTS) with import/export function enabled
| DFSMSrmm: Allows pre-OS/390 R10 systems to share the UW61561 (or, if DFSMS/MVS
| same DFSMSrmm control data set with OS/390 R10 and V1R5: UW61562)
later systems using the D/T3494 VTS advanced function
support
ISPF: Allows the sharing of ISPF edit recovery files between UW46845
OS/390 R6 or R7 systems and ISPF V4
| Language Environment: Allows downward compatibility, UQ24510, UQ28069,
| that is, developing applications on OS/390 R10 or later UQ39537, UQ39542,
| releases and running them on earlier releases UQ39562, UQ40409,
| UQ40467, UQ41303,
| UQ41306, UQ52707

Chapter 5. Ensuring Coexistence 75

 Table 6. Coexistence service (PTFs) needed on OS/390 R6 systems (continued)
Element or feature, and reason service is needed OS/390 R6 PTFs
SecureWay Security Server: Lets OS/390 R6 systems in a UW66592
Parallel Sysplex configuration tolerate the larger RACF
ENVR objects that OS/390 R10 and later consoles might
pass them
SDSF: Allows OS/390 R5, R6, and R7 SDSF to coexist with UQ29096
OS/390 R8-R9 JES2. (The PTF is required regardless of
whether a MAS is shared.)
SMP/E: Allows previous levels of SMP/E to tolerate changes UR51709; if Japanese feature
that later levels make to the format of data stored in SMP/E code is installed, add
data sets UR50423
z/OS UNIX System Services: Provides support to UW64382
simultaneously run Parallel Environment jobs using
different releases of OS/390

OS/390 R7 Coexistence Service

Apply, on OS/390 R7 systems, the coexistence service that is shown in Table 7.
Table 7. Coexistence service (PTFs) needed on OS/390 R7 systems
Element or feature, and reason service is needed OS/390 R7 PTFs
| BCP: Lets OS/390 R7 systems tolerate the automatic UW73392
restart management (ARM) support for Transactional
Services for VSAM introduced in OS/390 R9
| BCP: As of OS/390 R10, GRS (global resource UW72169
serialization) provides improvements to Parallel
Sysplex-wide contention management via PTFs for APAR
OW36418. Before a system with improved contention
management is activated, you must apply coexistence
service to all systems in the Parallel Sysplex. Note, in
addition, that for the improved contention management to
take effect, the PTFs for APAR OW36418 must be applied
to all systems in the Parallel Sysplex.
BCP: Allows the logger to do multiple reads from large UW71044
buffers for log data. This PTF does not have to be installed
on all systems within a Parallel Sysplex before z/OS V1R1
is IPLed into the sysplex.
BCP: Allows OS/390 R7 systems in a Parallel Sysplex UW63194 or, if Japanese,
configuration to participate in sysplex-wide monitoring that UW63527
may be triggered by an OS/390 R10 or later system that
supports structure full monitoring
BCP: Ensures compatibility with the RRS cascaded UW67817
transaction support introduced in OS/390 R9
BCP: As of OS/390 R10, there is new 32 KB block size UW69771
support and unit affinity support. This scheduler PTF allows
jobs that do not request the new functions to run
successfully when the jobs are submitted on OS/390 R10 or
later but routed by JES3 for execution on earlier OS/390
levels.
| BCP: Supports the coexistence of prior levels of the UW77475 or, if Japanese,
| console services components with z/OS V1R1 and later UW77473
| systems in a Parallel Sysplex configuration.

76 z/OS V1R1.0 Planning for Installation

 Table 7. Coexistence service (PTFs) needed on OS/390 R7 systems (continued)
Element or feature, and reason service is needed OS/390 R7 PTFs
BCP: Supports the coexistence of prior levels of WLM with UW71002
OS/390 R10 and later systems in a Parallel Sysplex
configuration
BCP: Lets OS/390 systems prior to R8 tolerate Parallel UW58109 and UW65554
Sysplex XES functions introduced in OS/390 R8. These
functions involve system-managed rebuild and the CFRM
couple data set.
| Cryptographic Services: Allows pre-OS/390 R10 systems UW73741
to share an ICSF cryptographic key data set (CKDS) with
an OS/390 R10 or later system (once key types of
IMPORTER, EXPORTER, PINGEN, PINVER, IPINEC, or
OPINENC, which have non-CCF control vectors, are added
to the CKDS)
DFSMSdfp: Allows pre-OS/390 R10 systems to tolerate UW61954, UW62977,
records created on OS/390 R10 and later systems with UW63366
block sizes greater than 32 KB
DFSMSdfp: Enables VSAM data sets to be striped across UW67759
multiple volumes
DFSMShsm: Allows pre-OS/390 R10 systems to tolerate UW68028
records created on OS/390 R10 and later systems with
block sizes greater than 32 KB
| DFSMShsm: Supports up to 64 concurrent command data UW73892
set backups to either ML1 DASD or tape. This enhancement
increases the rate at which DFSMShsm can perform
command data set backups and allows more batch
applications to take advantage of it.
DFSMSrmm: Allows pre-OS/390 R10 systems to use the UW57640
import/export function when sharing a virtual tape server
(VTS) with import/export function enabled
| DFSMSrmm: Allows pre-OS/390 R10 systems to share the UW61562
same DFSMSrmm control data set with OS/390 R10 and
later systems using the D/T3494 VTS advanced function
support
ISPF: Allows the sharing of ISPF edit recovery files between UW46845
OS/390 R6 or R7 systems and ISPF V4
| Language Environment: Allows downward compatibility, UQ23919, UQ28066,
| that is, developing applications on OS/390 R10 or later UQ39533, UQ39538,
| releases and running them on earlier releases UQ39548, UQ40402,
| UQ40463, UQ41302,
| UQ52702
SecureWay Security Server: Lets OS/390 R7 systems in a UW66592
Parallel Sysplex configuration tolerate the larger RACF
ENVR objects that OS/390 R10 and later consoles might
pass them
SDSF: Allows OS/390 R5, R6, and R7 SDSF to coexist with UQ29096
OS/390 R8-R9 JES2. (The PTF is required regardless of
whether a MAS is shared.)
z/OS UNIX System Services: Provides support to UW64383
simultaneously run Parallel Environment jobs using
different releases of OS/390

Chapter 5. Ensuring Coexistence 77

 OS/390 R8 Coexistence Service
Apply, on OS/390 R8 systems, the coexistence service that is shown in Table 8.
Table 8. Coexistence service (PTFs) needed on OS/390 R8 systems
Element or feature, and reason service is needed OS/390 R8 PTFs
| BCP: Lets OS/390 R8 systems tolerate the automatic UW73393
restart management (ARM) support for Transactional
Services for VSAM introduced in OS/390 R9
| BCP: As of OS/390 R10, GRS (global resource UW72167
serialization) provides improvements to Parallel
Sysplex-wide contention management via PTFs for APAR
OW36418. Before a system with improved contention
management is activated, you must apply coexistence
service to all systems in the Parallel Sysplex. Note, in
addition, that for the improved contention management to
take effect, the PTFs for APAR OW36418 must be applied
to all systems in the Parallel Sysplex.
BCP: Allows the logger to do multiple reads from large UW71045
buffers for log data. This PTF does not have to be installed
on all systems within a Parallel Sysplex before z/OS V1R1
is IPLed into the sysplex.
BCP: Allows OS/390 R8 systems in a Parallel Sysplex UW63195 or, if Japanese,
configuration to participate in sysplex-wide monitoring that UW63528
may be triggered by an OS/390 R10 or later system that
supports structure full monitoring
BCP: Ensures compatibility with the RRS cascaded UW67818
transaction support introduced in OS/390 R9
BCP: As of OS/390 R10, there is new 32 KB block size UW69770
support and unit affinity support. This scheduler PTF allows
jobs that do not request the new functions to run
successfully when the jobs are submitted on OS/390 R10 or
later but routed by JES3 for execution on earlier OS/390
levels.
| BCP: Supports the coexistence of prior levels of the UW77470 or, if Japanese,
| console services components with z/OS V1R1 and later UW77474
| systems in a Parallel Sysplex configuration.
BCP: Supports the coexistence of prior levels of WLM with UW71000
OS/390 R10 and later systems in a Parallel Sysplex
configuration
| Cryptographic Services: Allows pre-OS/390 R10 systems UW73741
to share an ICSF cryptographic key data set (CKDS) with
an OS/390 R10 or later system (once key types of
IMPORTER, EXPORTER, PINGEN, PINVER, IPINEC, or
OPINENC, which have non-CCF control vectors, are added
to the CKDS)
DFSMSdfp: Allows pre-OS/390 R10 systems to tolerate UW61954, UW62977,
records created on OS/390 R10 and later systems with UW63366
block sizes greater than 32 KB
DFSMSdfp: Enables VSAM data sets to be striped across UW67759
multiple volumes
DFSMShsm: Allows pre-OS/390 R10 systems to tolerate UW68028
records created on OS/390 R10 and later systems with
block sizes greater than 32 KB

78 z/OS V1R1.0 Planning for Installation

 Table 8. Coexistence service (PTFs) needed on OS/390 R8 systems (continued)
Element or feature, and reason service is needed OS/390 R8 PTFs
| DFSMShsm: Supports up to 64 concurrent command data UW73892
set backups to either ML1 DASD or tape. This enhancement
increases the rate at which DFSMShsm can perform
command data set backups and allows more batch
applications to take advantage of it.
DFSMSrmm: Allows pre-OS/390 R10 systems to use the UW57640
import/export function when sharing a virtual tape server
(VTS) with import/export function enabled
| DFSMSrmm: Allows pre-OS/390 R10 systems to share the UW61562
same DFSMSrmm control data set with OS/390 R10 and
later systems using the D/T3494 VTS advanced function
support
| Language Environment: Allows downward compatibility, UQ39534, UQ39539,
| that is, developing applications on OS/390 R10 or later UQ39549, UQ40403,
| releases and running them on earlier releases UQ40464, UQ41303
SecureWay Security Server: Lets OS/390 R8 systems in a UW66593
Parallel Sysplex configuration tolerate the larger RACF
ENVR objects that OS/390 R10 and later consoles might
pass them
z/OS UNIX System Services: Provides support to UW64384
simultaneously run Parallel Environment jobs using
different releases of OS/390

OS/390 R9 Coexistence Service

Apply, on OS/390 R9 systems, the coexistence service that is shown in Table 9.
Table 9. Coexistence service (PTFs) needed on OS/390 R9 systems
Element or feature, and reason service is needed OS/390 R9 PTFs
| BCP: As of OS/390 R10, GRS (global resource UW72167
serialization) provides improvements to Parallel
Sysplex-wide contention management via PTFs for APAR
OW36418. Before a system with improved contention
management is activated, you must apply coexistence
service to all systems in the Parallel Sysplex. Note, in
addition, that for the improved contention management to
take effect, the PTFs for APAR OW36418 must be applied
to all systems in the Parallel Sysplex.
BCP: Allows the logger to do multiple reads from large UW71045
buffers for log data. This PTF does not have to be installed
on all systems within a Parallel Sysplex before z/OS V1R1
is IPLed into the sysplex.
| BCP: As of OS/390 R10, there is new 32 KB block size UW69770
| support and unit affinity support. This scheduler PTF allows
| jobs that do not request the new functions to run
| successfully when the jobs are submitted on OS/390 R10 or
| later but routed by JES3 for execution on earlier OS/390
| levels.
| BCP: Supports the coexistence of prior levels of the UW77470 or, if Japanese,
| console services components with z/OS V1R1 and later UW77474
| systems in a Parallel Sysplex configuration.

Chapter 5. Ensuring Coexistence 79

 Table 9. Coexistence service (PTFs) needed on OS/390 R9 systems (continued)
Element or feature, and reason service is needed OS/390 R9 PTFs
BCP: Supports the coexistence of prior levels of WLM with UW71003
OS/390 R10 and later systems in a Parallel Sysplex
configuration
| Cryptographic Services: Allows pre-OS/390 R10 systems UW73742
to share an ICSF cryptographic key data set (CKDS) with
an OS/390 R10 or later system (once key types of
IMPORTER, EXPORTER, PINGEN, PINVER, IPINEC, or
OPINENC, which have non-CCF control vectors, are added
to the CKDS)
| DFSMSdfp: Allows pre-OS/390 R10 systems to tolerate UW61954, UW62977,
| records created on OS/390 R10 and later systems with UW63366
block sizes greater than 32 KB
DFSMSdfp: Enables VSAM data sets to be striped across UW67759
multiple volumes
DFSMShsm: Allows pre-OS/390 R10 systems to tolerate UW68028
records created on OS/390 R10 and later systems with
block sizes greater than 32 KB
| DFSMShsm: Supports up to 64 concurrent command data UW73892
set backups to either ML1 DASD or tape. This enhancement
increases the rate at which DFSMShsm can perform
command data set backups and allows more batch
applications to take advantage of it.
DFSMSrmm: Allows pre-OS/390 R10 systems to use the UW57640
import/export function when sharing a virtual tape server
(VTS) with import/export function enabled
| DFSMSrmm: Allows pre-OS/390 R10 systems to share the UW61562
same DFSMSrmm control data set with OS/390 R10 and
later systems using the D/T3494 VTS advanced function
support
| Language Environment: Allows downward compatibility, UQ39535, UQ39540,
| that is, developing applications on OS/390 R10 or later UQ39550, UQ40404,
| releases and running them on earlier releases UQ41304
SecureWay Security Server: Lets OS/390 R9 systems in a UW66593
Parallel Sysplex configuration tolerate the larger RACF
ENVR objects that OS/390 R10 and later consoles might
pass them

| OS/390 R10 Coexistence Service

| Apply, on OS/390 R10 systems, the coexistence service that is shown in Table 10.
| Table 10. Coexistence service (PTFs) needed on OS/390 R10 systems
| Element or feature, and reason service is needed OS/390 R10 PTFs
| BCP: Supports the coexistence of prior levels of the UW77471 or, if Japanese,
| console services components with z/OS V1R1 and later UW77476
| systems in a Parallel Sysplex configuration.
|

80 z/OS V1R1.0 Planning for Installation

|
JES2 Coexistence Service
The following PTFs are required for prior levels of JES2 to run with z/OS V1R1
JES2 in a multi-access spool (MAS):
On this release: Install these PTFs:
OS/390 R6 JES2 UW53872, UW58022, and UW69010
OS/390 R7 JES2 UW69011
OS/390 R8-R9 JES2 UW69012

JES3 Coexistence Service

The following PTFs are required for prior levels of JES3 to run with z/OS V1R1
JES3 in a multisystem complex:
On this release: Install these PTFs:
OS/390 R6-R7 JES3 UW58820, UW59644, UW66541, UW69090,
UW70365, UW90673
OS/390 R8 JES3 UW66542, UW69091, UW70366, UW90674
OS/390 R9 JES3 UW66543, UW69092, UW70367

Chapter 5. Ensuring Coexistence 81

82 z/OS V1R1.0 Planning for Installation
 Chapter 6. Preparing for Migration
A migration is a move to a changed operating environment, usually from an older
level of a product to a more current one. This chapter helps you decide what to
migrate first: software (to z/OS) or hardware (to the z900 server). It then uses
migration tables to identify, for each z/OS element and feature, whether you need to
take any software migration actions based on the OS/390 release from which you’re
migrating. Finally, it identifies any miscellaneous migration actions that might be
necessary.

Migrating in the future

When you migrate from z/OS V1R1 (or from any subsequent release), the
release you migrate to is required to be within four consecutive releases (or
within releases provided by any special provisions) to be fully supported. That
is, migration forward and backward must be made within four consecutive
releases. This applies to release migrations for:
v Single-system configurations
v Individual systems within a multisystem configuration
v Cases where a simultaneous IPL is used to migrate all systems in a
multisystem configuration at the same time

You should take this into account to ensure that you are appropriately
positioned for future software migrations. Because each release can normally
be ordered for only a six month period, it is important that you order the
required releases while they are available.

| Planning for z/OS on a z900 Server

| Only when you run z/OS on a z900 server can you achieve all that these two
| systems have to offer, that is, 64-bit real storage support, the Intelligent Resource
| Director (to dynamically manage resources across LPARs), and Workload License
| Charging. In order for you to migrate to this environment, you’ll have to upgrade
| software (OS/390 to z/OS), hardware (to the z900 server), and architecture (S/390
| to z/Architecture). This section presents recommendations for achieving this
| migration.

| As you will see, there is a lot of migration flexibility when migrating to z/OS on a
| z900 server. The optimal migration path depends on your choice of migrating
| hardware or software first, how much change you are willing to make at once, and
| other considerations such as those described below. As a result, different customers
| will choose different paths.

| Factors to consider when deciding whether to upgrade your software or hardware

| first are:
| v Existing plans and commitments.
| v Timing of capacity requirements and new functions (hardware and software).
| v Once a z900 server is installed, how soon you need to exploit the new
| architecture.
| v The level of existing software.
| v The level of existing hardware.
| v Your test environment.

© Copyright IBM Corp. 1996, 2001 83

| v Your disaster recovery environment.
| v The cost of software when running z/OS on a G5, G6 or Multiprise 3000 server.
| For many customers there will be little or no impact. However, anyone planning a
| migration should assess if there will be an impact to running the new version of
| the operating system.

| Also consider how much change (risk) you want to make (accept) at any given
| upgrade. Some factors to consider are:
| v The ability to schedule multiple upgrade windows. If scheduling upgrades is not a
| problem for your applications, you might want to minimize the amount of change
| (risk) and make several small hardware or software changes. However, if
| because of testing, application availability, or other factors you get only two
| upgrade windows a year, you might want to limit those to one hardware and one
| software change.
| v The ability to back out from a given change. While planning for backout from a
| processor change or a new operating system level is normal, you don’t normally
| plan to do both at the same time. Furthermore, there can be an implied
| architectural level change when z/OS runs on a z900 server.
| v How important it is to you to have similar test and production environments, and
| a similar disaster recovery environment (for example, in terms of the architecture
| level supported).

| We recommend the following:

| v If you are currently running OS/390 R5 or earlier, you are running on an
| unsupported level. In addition, OS/390 R5 and earlier releases are not
| coexistence-supported with releases after OS/390 R8. So take the following
| steps:
| 1. Migrate your software to OS/390 R10 by contracting to have IBM Global
| Services assess whether a direct migration to OS/390 R10 is possible and, if
| it is, have them help you through the migration. (If a direct migration is not
| possible, contact your IBM representative to understand what other
| alternatives might be available.) Assuming a direct migration to OS/390 R10
| is assessed as possible, order OS/390 R10 via a ServerPac or SystemPac.
| (CBPDO could be used instead but is not recommended because of the large
| number of elements that need to be installed.)
| 2. Order, install, and migrate to a z900 server. Initially, use the z900 server with
| OS/390 R10 in ESA/390 (31-bit) mode, then migrate to 64-bit real
| addressing.
| 3. Use the z/OS V1R1 Upgrade Package for OS/390 V2R10 to install and
| migrate from OS/390 R10 to z/OS V1R1. (Should you decide to migrate from
| OS/390 R10 to a release later than z/OS V1R1, you would order that z/OS
| release via the standard ServerPac, SystemPac, or CBPDO ordering
| deliverables because the Upgrade Package is only available for migrations
| from OS/390 R10 to z/OS V1R1.)

| By migrating to OS/390 R10 first, you minimize the risk of migrating to a new
| level of the operating system and a new architecture at the same time. OS/390
| R10 supports both architectures (ESA/390 and z/Architecture). Thus, by using
| OS/390 R10 as a migration step to z/OS and by placing your test image on a
| z900, running OS/390 R10 gives you the flexibility to test your applications and
| ISV products with either architecture while having the ability to fall back to
| ESA/390 if a problem is encountered. This full bimodality of OS/390 R10 is
| provided as a migration bridge to z/OS on a z900 server. (Note: If the test image

84 z/OS V1R1.0 Planning for Installation

| is running OS/390 R10 or z/OS on a G5, G6, or Multiprise 3000 server rather
| than a z900 server, your test environment is limited to ESA/390 architecture and
| 31-bit mode.)

| Finally, this approach takes advantage of the unique structure of the Upgrade
| Package, allowing you to quickly migrate from OS/390 R10 to z/OS V1R1 without
| having to completely replace all your software and without having to recustomize
| your entire operating system.

| Note: If you were to migrate directly to z/OS in step 1 instead of migrating to

| OS/390 R10 first, you would have additional risk (and further effort and
| expense as a result of the additional assessment work) because you
| would be migrating to an even later release outside the supported
| coexistence policy. To avoid this risk, take an intermediate migration step
| to a release that is coexistence-supported with the release you are
| migrating from, or consider OS/390 R10 under IBM contracted services
| (as outlined above), then upgrade to a z900 server, followed by the
| upgrade to z/OS.
| v If you already plan to migrate to OS/390 R10 by the second quarter of 2001,
| or you need to upgrade your operating system software (in production) by
| the second quarter of 2001 and you also have the goal of migrating to z/OS
| as quickly as possible, do the following:
| 1. Order, install, and migrate to OS/390 R10.
| 2. Order, install, and migrate to a z900 server. Initially, use the z900 server with
| OS/390 R10 in ESA/390 (31-bit) mode, then migrate to 64-bit real
| addressing.
| 3. Use the z/OS V1R1 Upgrade Package for OS/390 V2R10 to install and
| migrate to z/OS V1R1. (Should you decide to migrate from OS/390 R10 to a
| release later than z/OS V1R1, you would order that z/OS release via the
| standard ServerPac, SystemPac, or CBPDO ordering deliverables because
| the Upgrade Package is only available for migrations from OS/390 R10 to
| z/OS V1R1.)

| This path enables those with existing plans and commitments to meet them
| without wasting any effort. Furthermore, it minimizes the risk of migrating to new
| levels of the operating system and new architecture at the same time. Finally, it
| takes advantage of the unique structure of the Upgrade Package, allowing you to
| migrate to z/OS without having to completely replace all your software and
| without having to recustomize your entire operating system.

| While you can run z/OS V1R1 in a mixed hardware environment that includes
| G5, G6, Multiprise 3000, and z900 servers, if you are concerned about having
| your test and production environments as similar as possible (for example,
| capable of supporting similar architecture and addressing mode), you might
| consider placing your test image on a z900 server during step 2 above. OS/390
| R10 supports both architectures (ESA/390 and z/Architecture). Thus, by using
| OS/390 R10 as a migration step to z/OS and by placing your test image on a
| z900, running OS/390 R10 gives you the flexibility to test your applications and
| ISV products with either architecture while having the ability to fall back to
| ESA/390 if a problem is encountered. This full bimodality of OS/390 R10 is
| provided as a migration bridge to z/OS on a z900 server. (Note: If the test image
| is running OS/390 R10 or z/OS on a G5, G6, or Multiprise 3000 server rather
| than a z900 server, your test environment is limited to ESA/390 architecture and
| 31-bit mode.)

Chapter 6. Preparing for Migration 85

| v If you are currently running OS/390 R6, R7, R8, or R9 and want to upgrade
| your processor to take advantage of the additional processing capabilities
| of the z900 server (such as more MIPS and channels) before upgrading
| your operating system, do the following:
| 1. Order, install, and migrate to a z900 server. OS/390 R6 through OS/390 R9
| are fully supported on the z900 server. The system remains in 31-bit mode.
| 2. Upgrade to z/OS via ServerPac or SystemPac. (CBPDO could be used
| instead but is not recommended because of the large number of elements
| that must be installed).
| There is no need to go through OS/390 R10. However, because z/OS is
| required to run in 64-bit mode on a z900 server, there is an implied
| architectural level change when first migrating to z/OS on a z900 server. If
| you wish to avoid changing your operating system and architectural level at
| the same time, take the intermediate step of migrating to OS/390 R10,
| following by a migration to z/OS V1R1 using the z/OS V1R1 Upgrade
| Package for OS/390 V2R10. (Should you decide to migrate from OS/390 R10
| to a release later than z/OS V1R1, you would order that z/OS release via the
| standard ServerPac, SystemPac, or CBPDO ordering deliverables because
| the Upgrade Package is only available for migrations from OS/390 R10 to
| z/OS V1R1.)

| This path enables you to initially take advantage of the z900 capabilities that
| OS/390 can support, while providing a single software migration to get to z/OS to
| be in position to exploit 64-bit real addressing, IRD, and ILM. Furthermore, this
| path minimizes the number of testing and upgrade periods.
| v If you are currently running OS/390 R6, R7, R8, or R9 but not on a
| processor that implements ESA/390 architectural enhancements (listed
| below), and you also have the goal of migrating to z/OS as quickly as
| possible, do the following:
| 1. Order, install, and migrate to a z900 server. You must do this first because
| the hardware you currently have is not supported by z/OS (or OS/390 R10).
| 2. Upgrade to z/OS via ServerPac or SystemPac. (CBPDO could be used
| instead but is not recommended because of the large number of elements
| that must be installed). There is no need to go through OS/390 R10.

| This path enables you to upgrade your hardware once to support z/OS and be in
| position to exploit 64-bit real addressing, IRD, Workload License Charges, and
| ILM.

| Because z/OS must run in 64-bit mode on a z900 server, there is an implied
| architectural level change when first migrating to z/OS on a z900 server. If you
| wish to avoid changing your operating system and architectural level at the same
| time, take an intermediate migration step of migrating to OS/390 R10 (as outlined
| previously) followed by an upgrade to z/OS.

| The processors that are supported by z/OS are:

| – IBM ^ zSeries 900 (z900)
| – IBM S/390 Parallel Enterprise Server – G5 and G6
| – IBM S/390 Multiprise 3000 (all models)

| The processors that implement the ESA/390 architectural enhancements and are
| supported by OS/390 R10 are:
| – IBM S/390 Parallel Enterprise Server R2 and R3 models, as well as G3 and
| above

86 z/OS V1R1.0 Planning for Installation

| – IBM S/390 Multiprise – 2000 and 3000 (all models)
| – IBM S/390 Integrated Server (all models)
| – IBM PC Server System/390 (all models)
| – IBM RS/6000 and System/390 Server-on-Board (all models)
| v If you are currently running OS/390 R6, R7, R8, or R9 on a G5, G6, or
| Multiprise 3000 server and want to take advantage of the new hardware
| capabilities very soon after a z900 server is installed, or if you plan an
| operating system upgrade (such as an annual upgrade) soon, do the
| following:
| 1. Order, install, and migrate to z/OS via a ServerPac or SystemPac. (CBPDO
| could be used instead but is not recommended because of the large number
| of elements that must be installed).
| 2. Prepare for ILM and IRD by customizing the system and exploiting WLM,
| system logger, and OCSF.
| 3. Order, install, and migrate to a z900 server.
| This path enables you to have a single software migration and use that system to
| customize the required components needed by ILM and IRD, so that you are in
| position to exploit these functions after the migration to the z900 server is
| complete.

| As is the case with the hardware-first migration path, there is an implied

| architectural level change when first migrating to z/OS on a z900 server. If you
| wish to avoid changing your operating system and architectural level at the same
| time, take an intermediate migration step of migrating to OS/390 R10 (as outlined
| previously), then upgrading to a z900 server, followed by upgrading to z/OS.

| Disaster recovery environments should mirror as closely as possible their

| associated production environments. Therefore, plans for your disaster recovery
| systems should include upgrading the hardware so that it too is capable of
| supporting the new architecture once your production environment is running
| OS/390 R10 in 64-bit real mode or z/OS on a z900 server.

How to Use the Migration Tables

| The following migration paths to z/OS V1R1 are supported. This chapter has a
| migration table for each path.
| v From OS/390 R6 to z/OS V1R1
| v From OS/390 R7 to z/OS V1R1
| v From OS/390 R8 to z/OS V1R1
| v From OS/390 R9 to z/OS V1R1
| v From OS/390 R10 to z/OS V1R1

Each migration table identifies:

v Whether you have any migration actions to perform. Note that dynamically
enabling any priced features that were not previously enabled is not considered a
migration action.
v Whether, if you’re installing with CBPDO, you must install a particular element or
feature or can continue to run the stand-alone level that you previously installed.
This applies to CBPDO installers only because with CBPDO each FMID is
installed separately; thus you can avoid reinstalling FMIDs that you have already
installed.
v Where you can find appropriate migration information and, for CBPDO installers,
appropriate installation information.

Chapter 6. Preparing for Migration 87

 The tables identify this information through the following phrases:
v “Installation (if CBPDO) is required”.
This means that, if you are a CBPDO installer, you must install the current z/OS
level. Exploiting new function, however, might require you to take migration
actions.
v “Functionally equivalent, no installation (if CBPDO) is required”.
This means that no migration actions are required. It does not imply that you
have no service to install to bring the element, feature, or product to the correct
service level. Often, if you choose the CBPDO method, you will have to install
service even in the “functionally equivalent” case to get to the integration-tested
level.
v “Functionally equivalent but installation (if CBPDO) is required”.
This means that no migration actions are required. However, if you are a CBPDO
installer, you must install the current z/OS level. Exploiting new function,
however, might require you to take migration actions.
v “Not functionally equivalent, no migration actions, installation (if CBPDO) is
required”.
This means you have no migration actions; however, CBPDO installers must
install the current z/OS level. Exploiting new function, however, might require you
to take migration actions.
v “Not functionally equivalent, migration actions and installation (if CBPDO) are
both required”.
This means you have migration actions to perform and, if you’re installing with
CBPDO, you must install the current z/OS level.
Notes:
1. The phrase “functionally equivalent” assumes that appropriate small
programming enhancements (SPEs) and PTFs have been added to the earlier
levels of the element, feature, or stand-alone product.
2. The phrase “installation is required” means that the product, element, or feature
has a new FMID.
3. The phrase “not applicable” indicates that no migration or installation actions
apply to a migration from one level to another.

If you are already running the z/OS V1R1 level of a nonexclusive element or
feature, you have no migration actions for that element or feature.

The following example shows how to use the tables. Suppose you are currently
running OS/390 R8 SDSF. First, you would find the SDSF entry in the table:

88 z/OS V1R1.0 Planning for Installation

 Example
Table 11. Migrating from OS/390 R8 to z/OS V1R1
Element or feature If you are migrating through Look for migration (M) and
the following paths: installation (I) information in
the following:
SDSF OS/390 R8 SDSF—> z/OS M: z/OS SDSF Operation and
V1R1 Customization.

Not functionally equivalent, I (if CBPDO): z/OS V1R1.0

migration actions and Program Directory.
installation (if CBPDO) are
both required if you use
JES2.

Then, for migration actions on the path from OS/390 R8 SDSF to z/OS V1R1, you
would turn to the book identified by M, z/OS SDSF Operation and Customization.
Finally, to install z/OS V1R1 if you are using the CBPDO installation method, you
would turn to the book identified by I, z/OS V1R1.0 Program Directory. (If you were
installing using ServerPac or SystemPac, you would install all of z/OS as a unit,
and installation of an individual element or feature would not be an issue.)

| Migrating from OS/390 R6 to z/OS V1R1

| Table 12 helps you migrate from the OS/390 R6 levels of elements, features, and
| products and points to books that contain appropriate migration and installation
| information.
| Table 12. Migrating from OS/390 R6 to z/OS V1R1
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| AET OS/390 R6 AET—> z/OS V1R1 Not applicable.

| Removed from OS/390 as of OS/390 R8.

| BCP OS/390 R6 BCP—> z/OS V1R1 M: z/OS MVS Migration and z/OS UNIX
| System Services Planning.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| BDT OS/390 R6 BDT—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BDT File-to-File OS/390 R6 BDT File-to-File—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BDT SNA NJE OS/390 R6 BDT SNA NJE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.

Chapter 6. Preparing for Migration 89

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| BookManager BookServer OS/390 R6 BookManager M: “Migration Actions for BookManager
| BookServer—> z/OS V1R1 BookServer” on page 138.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| BookManager BookServer for World Not applicable.
| Wide Web for MVS/ESA V2.2—> z/OS
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager BUILD OS/390 R6 BookManager BUILD—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager READ OS/390 R6 BookManager READ—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| C/C++ IBM Open Class Library OS/390 R6 C/C++ IBM Open Class M: “Migration Actions for C/C++” on
| Library—> z/OS V1R1 page 142 and z/OS C/C++ Compiler and
| Run-Time Migration Guide.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| C/C++ with Debug Tool OS/390 R6 C/C++—> z/OS V1R1 M: “Migration Actions for C/C++” on
| page 142 and z/OS C/C++ Compiler and
| Except for Debug Tool: Not functionally Run-Time Migration Guide.
| equivalent, migration actions and
| installation (if CBPDO) are both required. I (if CBPDO): z/OS V1R1.0 Program
| For Debug Tool: Functionally equivalent, Directory.
| no installation (if CBPDO) is required.
| C/C++ without Debug Tool OS/390 R6 C/C++—> z/OS V1R1 M: “Migration Actions for C/C++” on
| page 142 and z/OS C/C++ Compiler and
| Not functionally equivalent, migration Run-Time Migration Guide.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Communications Server OS/390 R6 eNetwork Communications M: z/OS Communications Server: IP
| Server—> z/OS V1R1 Migration and z/OS Communications
| Server: SNA Migration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.

90 z/OS V1R1.0 Planning for Installation

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Communications Server NPF No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R6 TCP/IP NPF—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Functionally equivalent but installation (if
| CBPDO) is required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 1 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R6 TCP/IP Kerberos I (if CBPDO): z/OS V1R1.0 Program
| Non-DES—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 2 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R6 TCP/IP Kerberos DES—> I (if CBPDO): z/OS V1R1.0 Program
| z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 3 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| IP Security - TDES—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| Cryptographic Services No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required.
| OS/390 R6 ICSF—> z/OS V1R1 M: z/OS ICSF Administrator’s Guide and
| z/OS ICSF System Programmer’s Guide.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| DCE Application Support OS/390 R6 DCE Application M: z/OS DCE Application Support
| Support—> z/OS V1R1 Configuration and Administration Guide.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.

Chapter 6. Preparing for Migration 91

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| DCE Base Services OS/390 R6 DCE Base Services—> M: z/OS DCE Planning.
| z/OS V1R1
| I (if CBPDO): z/OS V1R1.0 Program
| Not functionally equivalent, migration Directory.
| actions and installation (if CBPDO) are
| both required.
| DCE User Data Privacy CDMF OS/390 R6 DCE User Data Privacy Use the DCE Base Services base
| CDMF—> z/OS V1R1 element.

| DCE User Data Privacy CDMF was

| removed as an optional feature as of
| OS/390 R9. The function was merged
| into the DCE Base Services base
| element.
| DCE User Data Privacy OS/390 R6 DCE User Data Privacy Use the DCE Base Services base
| DES/CDMF DES/CDMF—> z/OS V1R1 element.

| DCE User Data Privacy DES/CDMF was

| removed as an optional feature as of
| OS/390 R9. The function was merged
| into the DCE Base Services base
| element.
| DFSMSdfp OS/390 R6 DFSMSdfp—> z/OS V1R1 M: z/OS DFSMS Migration.

| DFSMS/MVS DFSMSdfp V1R5—> z/OS I (if CBPDO): z/OS V1R1.0 Program

| V1R1 Directory.

| Not functionally equivalent, migration

| actions and installation (if CBPDO) are
| both required.
| DFSMSdss OS/390 R6 DFSMSdss—> z/OS V1R1 M: z/OS DFSMS Migration.

| DFSMS/MVS DFSMSdss V1R5—> z/OS I (if CBPDO): z/OS V1R1.0 Program

| V1R1 Directory.

| Not functionally equivalent, migration

| actions and installation (if CBPDO) are
| both required.
| DFSMShsm OS/390 R6 DFSMShsm—> z/OS V1R1 M: z/OS DFSMS Migration.

| DFSMS/MVS DFSMShsm V1R5—> I (if CBPDO): z/OS V1R1.0 Program

| z/OS V1R1 Directory.

| Not functionally equivalent, migration

| actions and installation (if CBPDO) are
| both required.
| DFSMSrmm OS/390 R6 DFSMSrmm—> z/OS V1R1 M: z/OS DFSMS Migration.

| DFSMS/MVS DFSMSrmm V1R5—> I (if CBPDO): z/OS V1R1.0 Program

| z/OS V1R1 Directory.

| Not functionally equivalent, migration

| actions and installation (if CBPDO) are
| both required.

92 z/OS V1R1.0 Planning for Installation

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| DFSORT OS/390 R6 DFSORT—> z/OS V1R1 M: DFSORT Installation and
| Customization R14.
| DFSORT V1R13—> z/OS V1R1
| I (if CBPDO): z/OS V1R1.0 Program
| Not functionally equivalent, migration Directory and DFSORT Installation and
| actions and installation (if CBPDO) are Customization R14.
| both required.
| DFSORT V1R14—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Distributed File Service OS/390 R6 Distributed File Service—> M: z/OS Distributed File Service
| z/OS V1R1 Customization and z/OS Distributed File
| Service SMB Administration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| Encina Toolkit Executive OS/390 R6 Encina Toolkit I (if CBPDO): z/OS V1R1.0 Program
| Executive—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| EREP OS/390 R6 EREP —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ESCON Director Support OS/390 R6 ESCON Director Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| FFST OS/390 R6 FFST —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM OS/390 R6 GDDM—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM-PGF OS/390 R6 GDDM-PGF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM-REXX OS/390 R6 GDDM-REXX—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| HCD OS/390 R6 HCD—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.

Chapter 6. Preparing for Migration 93

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| HCM OS/390 R6 HCM—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory and z/OS HCM User’s Guide.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HLASM OS/390 R6 HLASM—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HLASM V1R4—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| HLASM Toolkit OS/390 R6 HLASM Toolkit—> z/OS I (if CBPDO): z/OS V1R1.0 Program
| V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| HLASM Toolkit in HLASM V1R4—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| IBM HTTP Server OS/390 R6 Domino Go Webserver—> M: z/OS HTTP Server Planning,
| z/OS V1R1 Installing, and Using.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and z/OS HTTP Server
| both required. Planning, Installing, and Using.
| IBM HTTP Server Export OS/390 R6 Domino Go Webserver Not applicable.
| Secure Export Security—> z/OS V1R1

| IBM HTTP Server Export Secure,

| formerly named Domino Go Webserver
| Export Security, was removed from
| OS/390 as of OS/390 R10. It is no longer
| needed; the equivalent level of security is
| provided by base element Cryptographic
| Services.
| IBM HTTP Server France OS/390 R6 Domino Go Webserver Not applicable.
| Secure France Secure—> z/OS V1R1

| IBM HTTP Server France Secure,

| formerly named Domino Go Webserver
| France Secure, was removed from
| OS/390 as of OS/390 R10. It is no longer
| needed; the equivalent level of security is
| provided by base element Cryptographic
| Services.

94 z/OS V1R1.0 Planning for Installation

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| IBM HTTP Server NA Secure No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory and z/OS HTTP Server
| Installation (if CBPDO) is required if the Planning, Installing, and Using.
| feature is ordered.
| OS/390 R6 Domino Go Webserver M: z/OS HTTP Server Planning,
| North America Secure—> z/OS V1R1 Installing, and Using.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and z/OS HTTP Server
| both required. Planning, Installing, and Using.
| ICKDSF OS/390 R6 ICKDSF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ILM No prior product—> z/OS V1R1 M: “Migration Actions for ILM” on
| page 143.
| Migration actions and installation (if
| CBPDO) are both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Infoprint Server IP PrintWay feature of PSF/MVS V2R2 M: “Migration Actions for Infoprint Server”
| or PSF V3R1—> z/OS V1R1 on page 144 and z/OS Infoprint Server
| Migration.
| NetSpool feature of PSF/MVS V2R2 or
| PSF V3R1—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| OS/390 R6 Print Server—> z/OS V1R1

| Not functionally equivalent, migration

| actions and installation (if CBPDO) are
| both required.
| ISPF OS/390 R6 ISPF—> z/OS V1R1 M: For host-based services: z/OS ISPF
| Planning and Customizing. For
| Not functionally equivalent, migration client-server services: z/OS ISPF User’s
| actions and installation (if CBPDO) are Guide.
| both required.
| I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| JES2 OS/390 R6 JES2—> z/OS V1R1 M: “Migration Actions for JES2” on
| page 147 and z/OS JES2 Migration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required if you use JES2. Directory.
| JES3 OS/390 R6 JES3—> z/OS V1R1 M: z/OS JES3 Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required if you use JES3.
| LAN Server OS/390 R6 LAN Server—> z/OS V1R1 The OS/2 Front End Processor
| configurations from previous releases of
| OS/390 R9 was the last release to LAN Server are still supported on z/OS
| include both the workstation and host V1R1 for customers who want to migrate
| components. OS/390 R10 and z/OS to z/OS V1R1 prior to migrating off LAN
| V1R1 have only the host component. Server. See S/390 File and Print Serving,
| After z/OS V1R1, neither component will SG24-5330, for alternative solutions and
| be available. migration guidance.

Chapter 6. Preparing for Migration 95

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Language Environment To z/OS V1R1 from pre-Language M: “Migration Actions for Language
| Environment run-time libraries: Environment” on page 147, z/OS
| v C/370 V1 and V2 Language Environment Run-Time
| v OS/VS COBOL Migration Guide, and:
| v VS COBOL II v z/OS C/C++ Compiler and Run-Time
| v VS FORTRAN V1 and V2 Migration Guide
| v OS PL/I V1 and V2 v COBOL for OS/390 & VM and COBOL
| for MVS & VM Compiler and Run-Time
| Not functionally equivalent, migration Migration Guide
| actions and installation (if CBPDO) are v Language Environment for MVS & VM
| both required. Fortran Run-Time Migration Guide
| Note: The listed products contain both a v PL/I for MVS & VM Compiler and
| compiler and a run-time library. The Run-Time Migration Guide
| object programs produced by the v VisualAge PL/I for OS/390 Compiler
| compilers are supported running under and Run-Time Migration Guide
| z/OS Language Environment, although
| not all of the compilers themselves are I (if CBPDO): z/OS V1R1.0 Program
| still supported. Directory.
| OS/390 R6 Language Environment—> M: “Migration Actions for Language
| z/OS V1R1 Environment” on page 147 and z/OS
| Language Environment Run-Time
| Not functionally equivalent, migration Migration Guide.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Language Environment Data OS/390 R6 Language Environment Use the Language Environment base
| Decryption Data Decryption—> z/OS V1R1 element.

| Language Environment Data Decryption

| was removed as an optional feature as of
| OS/390 R9. The function was merged
| into the Language Environment base
| element.
| LANRES OS/390 R6 LANRES—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| MICR/OCR OS/390 R6 MICR/OCR—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| msys for Setup No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required.
| Network File System OS/390 R6 Network File System—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| OCSF Security Level 3 No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.

96 z/OS V1R1.0 Planning for Installation

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| OSA/SF OS/390 R6 OSA/SF—> z/OS V1R1 M: OSA/SF User’s Guide for OSA-2 and
| S/390: OSA-Express Customer’s Guide
| Not functionally equivalent, migration and Reference.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| OSA/SF V2R1—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| RMF OS/390 R6 RMF—> z/OS V1R1 M: RMF User’s Guide.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and RMF User’s Guide.
| both required.
| SDSF OS/390 R6 SDSF—> z/OS V1R1 M: z/OS SDSF Operation and
| Customization.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required if you use JES2. Directory.
| SecureWay Security Server OS/390 R6 Security Server—> z/OS M: z/OS SecureWay Security Server
| V1R1 RACF Migration, z/OS DCE Planning,
| z/OS SecureWay Security Server LDAP
| OCEP and Network Authentication and Server Administration and Use, and z/OS
| Privacy Service components: New SecureWay Security Server Firewall
| function, installation (if CBPDO) is Technologies.
| required.
| I (if CBPDO): z/OS V1R1.0 Program
| Other components: Not functionally Directory.
| equivalent, migration actions and
| installation (if CBPDO) are both required.
| Security Server LDAP Server OS/390 R6 Security Server LDAP Use the System SSL Security Level 3
| DES Server DES—> z/OS V1R1 feature.

| Security Server LDAP Server DES was

| removed as an optional feature as of
| OS/390 R8. Instead use the System SSL
| Security Level 3 feature.
| SMP/E OS/390 R6 SMP/E—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| Softcopy Print OS/390 R6 Softcopy Print—> z/OS See Softcopy Print in Table 2 on page 20.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| SOMobjects ADE OS/390 R6 SOMobjects ADE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.

Chapter 6. Preparing for Migration 97

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| SOMobjects RTL OS/390 R6 SOMobjects RTL—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| System SSL Security Level 3 No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| Text Search OS/390 R6 NetQuestion—> z/OS V1R1 M: z/OS Text Search: Installation and
| Administration for the Text Search
| Not functionally equivalent, migration Engine.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| OS/390 R6 with Text Search I (if CBPDO): z/OS V1R1.0 Program
| downloaded from the Web—> z/OS Directory.
| V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| TIOC OS/390 R6 TIOC—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Tivoli Management Framework No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required.
| Tivoli Management Framework for I (if CBPDO): z/OS V1R1.0 Program
| OS/390 V3.6—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| TSO/E OS/390 R6 TSO/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| VisualLift ADE OS/390 R6 VisualLift ADE—> z/OS None.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| VisualLift RTE OS/390 R6 VisualLift RTE—> z/OS None.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| WebSphere Application Server OS/390 R6 Domino Go Webserver—> Use the stand-alone product WebSphere
| z/OS V1R1 Application Server for OS/390 V3
| (5655-A98).
| Removed from OS/390 as of OS/390
| R10.

98 z/OS V1R1.0 Planning for Installation

| Table 12. Migrating from OS/390 R6 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| z/OS UNIX System Services OS/390 R6 UNIX System Services—> M: z/OS UNIX System Services Planning
| z/OS V1R1 and z/OS UNIX System Services
| Connection Scaling Reference.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| 3270 PC File Transfer 3270 PC File Transfer Program—> Not applicable.
| Program z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
|
|
| Migrating from OS/390 R7 to z/OS V1R1
| Table 13 helps you migrate from the OS/390 R7 levels of elements, features, and
| products and points to books that contain appropriate migration and installation
| information.
| Table 13. Migrating from OS/390 R7 to z/OS V1R1
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| AET OS/390 R7 AET—> z/OS V1R1 Not applicable.

| Removed from OS/390 as of OS/390 R8.

| BCP OS/390 R7 BCP—> z/OS V1R1 M: z/OS MVS Migration and z/OS UNIX
| System Services Planning.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| BDT OS/390 R7 BDT—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BDT File-to-File OS/390 R7 BDT File-to-File—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BDT SNA NJE OS/390 R7 BDT SNA NJE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.

Chapter 6. Preparing for Migration 99

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| BookManager BookServer OS/390 R7 BookManager M: “Migration Actions for BookManager
| BookServer—> OS/390 R10 BookServer” on page 138.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| BookManager BookServer for World Not applicable.
| Wide Web for MVS/ESA V2.2—> z/OS
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager BUILD OS/390 R7 BookManager BUILD—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager READ OS/390 R7 BookManager READ—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| C/C++ IBM Open Class Library OS/390 R7 C/C++ IBM Open Class M: “Migration Actions for C/C++” on
| Library—> z/OS V1R1 page 142 and z/OS C/C++ Compiler and
| Run-Time Migration Guide.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| C/C++ with Debug Tool OS/390 R7 C/C++—> z/OS V1R1 M: “Migration Actions for C/C++” on
| page 142 and z/OS C/C++ Compiler and
| Except for Debug Tool: Not functionally Run-Time Migration Guide.
| equivalent, migration actions and
| installation (if CBPDO) are both required. I (if CBPDO): z/OS V1R1.0 Program
| For Debug Tool: Functionally equivalent, Directory.
| no installation (if CBPDO) is required.
| C/C++ without Debug Tool OS/390 R7 C/C++—> z/OS V1R1 M: “Migration Actions for C/C++” on
| page 142 and z/OS C/C++ Compiler and
| Not functionally equivalent, migration Run-Time Migration Guide.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Communications Server OS/390 R7 eNetwork Communications M: z/OS Communications Server: IP
| Server—> z/OS V1R1 Migration and z/OS Communications
| Server: SNA Migration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.

100 z/OS V1R1.0 Planning for Installation

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Communications Server NPF No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R7 eNetwork Communications I (if CBPDO): z/OS V1R1.0 Program
| Server NPF—> z/OS V1R1 Directory.

| Functionally equivalent but installation (if

| CBPDO) is required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 1 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R7 eNetwork Communications I (if CBPDO): z/OS V1R1.0 Program
| Server Security Level 1—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 2 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R7 eNetwork Communications I (if CBPDO): z/OS V1R1.0 Program
| Server Security Level 2—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 3 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R7 eNetwork Communications I (if CBPDO): z/OS V1R1.0 Program
| Server Security Level 3—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Cryptographic Services OS/390 R7 Cryptographic Services—> M: z/OS ICSF Administrator’s Guide and
| z/OS V1R1 z/OS ICSF System Programmer’s Guide.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DCE Application Support OS/390 R7 DCE Application Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.

Chapter 6. Preparing for Migration 101

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| DCE Base Services OS/390 R7 DCE Base Services—> I (if CBPDO): z/OS V1R1.0 Program
| z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| DCE User Data Privacy CDMF OS/390 R7 DCE User Data Privacy Use the DCE Base Services base
| CDMF—> z/OS V1R1 element.

| DCE User Data Privacy CDMF was

| removed as an optional feature as of
| OS/390 R9. The function was merged
| into the DCE Base Services base
| element.
| DCE User Data Privacy OS/390 R7 DCE User Data Privacy Use the DCE Base Services base
| DES/CDMF DES/CDMF—> z/OS V1R1 element.

| DCE User Data Privacy DES/CDMF was

| removed as an optional feature as of
| OS/390 R9. The function was merged
| into the DCE Base Services base
| element.
| DFSMSdfp OS/390 R7 DFSMSdfp—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSMSdss OS/390 R7 DFSMSdss—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSMShsm OS/390 R7 DFSMShsm—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSMSrmm OS/390 R7 DFSMSrmm—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSORT OS/390 R7 DFSORT—> z/OS V1R1 Not applicable.

| DFSORT V1R14—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Distributed File Service OS/390 R7 Distributed File Service—> M: z/OS Distributed File Service
| z/OS V1R1 Customization and z/OS Distributed File
| Service SMB Administration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.

102 z/OS V1R1.0 Planning for Installation

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Encina Toolkit Executive OS/390 R7 Encina Toolkit Not applicable.
| Executive—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| EREP OS/390 R7 EREP —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ESCON Director Support OS/390 R7 ESCON Director Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| FFST OS/390 R7 FFST —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM OS/390 R7 GDDM—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM-PGF OS/390 R7 GDDM-PGF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM-REXX OS/390 R7 GDDM-REXX—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| HCD OS/390 R7 HCD—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HCM OS/390 R7 HCM—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory and z/OS HCM User’s Guide.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HLASM OS/390 R7 HLASM—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HLASM V1R4—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.

Chapter 6. Preparing for Migration 103

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| HLASM Toolkit OS/390 R7 HLASM Toolkit—> z/OS I (if CBPDO): z/OS V1R1.0 Program
| V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| HLASM Toolkit in HLASM V1R4—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| IBM HTTP Server OS/390 R7 WebSphere Application M: z/OS HTTP Server Planning,
| Server—> z/OS V1R1 Installing, and Using.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and z/OS HTTP Server
| both required. Planning, Installing, and Using.
| IBM HTTP Server Export OS/390 R7 IBM HTTP Server Export Not applicable.
| Secure Secure—> z/OS V1R1

| Removed from OS/390 as of OS/390

| R10. It is no longer needed; the
| equivalent level of security is provided by
| base element Cryptographic Services.
| IBM HTTP Server France OS/390 R7 IBM HTTP Server France Not applicable.
| Secure Secure—> z/OS V1R1

| Removed from OS/390 as of OS/390

| R10. It is no longer needed; the
| equivalent level of security is provided by
| base element Cryptographic Services.
| IBM HTTP Server NA Secure No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory and z/OS HTTP Server
| Installation (if CBPDO) is required if the Planning, Installing, and Using.
| feature is ordered.
| OS/390 R7 IBM HTTP Server NA I (if CBPDO): z/OS V1R1.0 Program
| Secure—> z/OS V1R1 Directory and z/OS HTTP Server
| Planning, Installing, and Using.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| ICKDSF OS/390 R7 ICKDSF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ILM No prior product—> z/OS V1R1 M: “Migration Actions for ILM” on
| page 143.
| Migration actions and installation (if
| CBPDO) are both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.

104 z/OS V1R1.0 Planning for Installation

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Infoprint Server IP PrintWay feature of PSF/MVS V2R2 M: “Migration Actions for Infoprint Server”
| or PSF V3R1—> z/OS V1R1 on page 144 and z/OS Infoprint Server
| Migration.
| NetSpool feature of PSF/MVS V2R2 or
| PSF V3R1—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| OS/390 R7 Print Server—> z/OS V1R1

| Not functionally equivalent, migration

| actions and installation (if CBPDO) are
| both required.
| ISPF OS/390 R7 ISPF—> z/OS V1R1 M: For host-based services: z/OS ISPF
| Planning and Customizing. For
| Not functionally equivalent, migration client-server services: z/OS ISPF User’s
| actions and installation (if CBPDO) are Guide.
| both required.
| I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| JES2 OS/390 R7 JES2—> z/OS V1R1 M: “Migration Actions for JES2” on
| page 147 and z/OS JES2 Migration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required if you use JES2. Directory.
| JES3 OS/390 R7 JES3—> z/OS V1R1 M: z/OS JES3 Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required if you use JES3.
| LAN Server OS/390 R7 LAN Server—> z/OS V1R1 The OS/2 Front End Processor
| configurations from previous releases of
| OS/390 R9 was the last release to LAN Server are still supported on z/OS
| include both the workstation and host V1R1 for customers who want to migrate
| components. OS/390 R10 and z/OS to z/OS V1R1 prior to migrating off LAN
| V1R1 have only the host component. Server. See S/390 File and Print Serving,
| After z/OS V1R1, neither component will SG24-5330, for alternative solutions and
| be available. migration guidance.

Chapter 6. Preparing for Migration 105

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Language Environment To z/OS V1R1 from pre-Language M: “Migration Actions for Language
| Environment run-time libraries: Environment” on page 147, z/OS
| v C/370 V1 and V2 Language Environment Run-Time
| v OS/VS COBOL Migration Guide, and:
| v VS COBOL II v z/OS C/C++ Compiler and Run-Time
| v VS FORTRAN V1 and V2 Migration Guide
| v OS PL/I V1 and V2 v COBOL for OS/390 & VM and COBOL
| for MVS & VM Compiler and Run-Time
| Not functionally equivalent, migration Migration Guide
| actions and installation (if CBPDO) are v Language Environment for MVS & VM
| both required. Fortran Run-Time Migration Guide
| Note: The listed products contain both a v PL/I for MVS & VM Compiler and
| compiler and a run-time library. The Run-Time Migration Guide
| object programs produced by the v VisualAge PL/I for OS/390 Compiler
| compilers are supported running under and Run-Time Migration Guide
| z/OS Language Environment, although
| not all of the compilers themselves are I (if CBPDO): z/OS V1R1.0 Program
| still supported. Directory.
| OS/390 R7 Language Environment—> M: “Migration Actions for Language
| z/OS V1R1 Environment” on page 147 and z/OS
| Language Environment Run-Time
| Not functionally equivalent, migration Migration Guide.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Language Environment Data OS/390 R7 Language Environment Use the Language Environment base
| Decryption Data Decryption—> z/OS V1R1 element.

| Language Environment Data Decryption

| was removed as an optional feature as of
| OS/390 R9. The function was merged
| into the Language Environment base
| element.
| LANRES OS/390 R7 LANRES—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| MICR/OCR OS/390 R7 MICR/OCR—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| msys for Setup No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required.
| Network File System OS/390 R7 Network File System—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| OCSF France OS/390 R7 OCSF France—> z/OS V1R1 Use the Cryptographic Services base
| element.
| OCSF France was removed as an
| optional feature as of OS/390 R9. The
| function was merged into the
| Cryptographic Services base element.

106 z/OS V1R1.0 Planning for Installation

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| OCSF Security Level 1 OS/390 R7 OCSF Security Level 1—> Use the Cryptographic Services base
| z/OS V1R1 element.

| OCSF Security Level 1 was removed as

| an optional feature as of OS/390 R9. The
| function was merged into the
| Cryptographic Services base element.
| OCSF Security Level 2 OS/390 R7 OCSF Security Level 2—> Use the Cryptographic Services base
| z/OS V1R1 element.

| OCSF Security Level 2 was removed as

| an optional feature as of OS/390 R9. The
| function was merged into the
| Cryptographic Services base element.
| OCSF Security Level 3 No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R7 OCSF Security Level 3—> I (if CBPDO): z/OS V1R1.0 Program
| z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| OSA/SF OS/390 R7 OSA/SF—> z/OS V1R1 M: OSA/SF User’s Guide for OSA-2 and
| S/390: OSA-Express Customer’s Guide
| Not functionally equivalent, migration and Reference.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| OSA/SF V2R1—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| RMF OS/390 R7 RMF—> z/OS V1R1 M: RMF User’s Guide.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and RMF User’s Guide.
| both required.
| SDSF OS/390 R7 SDSF—> z/OS V1R1 M: z/OS SDSF Operation and
| Customization.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required if you use JES2. Directory.

Chapter 6. Preparing for Migration 107

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| SecureWay Security Server OS/390 R7 Security Server—> z/OS M: z/OS SecureWay Security Server
| V1R1 RACF Migration, z/OS SecureWay
| Security Server LDAP Server
| DCE Security Server component: Not Administration and Use, and z/OS
| functionally equivalent, no migration SecureWay Security Server Firewall
| actions, installation (if CBPDO) is Technologies.
| required.
| I (if CBPDO): z/OS V1R1.0 Program
| OCEP and Network Authentication and Directory.
| Privacy Service components: New
| function, installation (if CBPDO) is
| required.

| Other components: Not functionally

| equivalent, migration actions and
| installation (if CBPDO) are both required.
| Security Server LDAP Server OS/390 R7 Security Server LDAP Use the System SSL Security Level 3
| DES Server DES—> z/OS V1R1 feature.

| Security Server LDAP Server DES was

| removed as an optional feature as of
| OS/390 R8. Instead use the System SSL
| Security Level 3 feature.
| SMP/E OS/390 R7 SMP/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Softcopy Print OS/390 R7 Softcopy Print—> z/OS See Softcopy Print in Table 2 on page 20.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| SOMobjects ADE OS/390 R7 SOMobjects ADE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| SOMobjects RTL OS/390 R7 SOMobjects RTL—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| System SSL Crypto OS/390 R7 System SSL Crypto—>
| z/OS V1R1

| System SSL Crypto was renamed

| System SSL Security Level 3 as of
| OS/390 R8.

108 z/OS V1R1.0 Planning for Installation

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| System SSL Security Level 3 No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R7 System SSL Crypto—> I (if CBPDO): z/OS V1R1.0 Program
| z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Text Search OS/390 R7 NetQuestion—> z/OS V1R1 M: z/OS Text Search: Installation and
| Administration for the Text Search
| Not functionally equivalent, migration Engine.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| OS/390 R7 with Text Search I (if CBPDO): z/OS V1R1.0 Program
| downloaded from the Web—> z/OS Directory.
| V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| TIOC OS/390 R7 TIOC—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Tivoli Management Framework No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required.
| OS/390 R7 Tivoli Management I (if CBPDO): z/OS V1R1.0 Program
| Framework—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| TSO/E OS/390 R7 TSO/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| VisualLift ADE OS/390 R7 VisualLift ADE—> z/OS None.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| VisualLift RTE OS/390 R7 VisualLift RTE—> z/OS None.
| V1R1

| Removed from OS/390 as of OS/390

| R10.

Chapter 6. Preparing for Migration 109

| Table 13. Migrating from OS/390 R7 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| WebSphere Application Server OS/390 R7 WebSphere Application Use the stand-alone product WebSphere
| Server—> z/OS V1R1 Application Server for OS/390 V3
| (5655-A98).
| Removed from OS/390 as of OS/390
| R10.
| z/OS UNIX System Services OS/390 R7 UNIX System Services—> M: z/OS UNIX System Services
| z/OS V1R1 Planning.

| Application Services component: Not I (if CBPDO): z/OS V1R1.0 Program

| functionally equivalent, migration actions Directory.
| and installation (if CBPDO) are both
| required.

| Connection Manager and Process

| Manager components: Functionally
| equivalent, no installation (if CBPDO) is
| required.

| Integrated Call Level Interface

| component: Not functionally equivalent,
| no migration actions, installation (if
| CBPDO) is required.
| 3270 PC File Transfer 3270 PC File Transfer Program—> Not applicable.
| Program z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
|
|
| Migrating from OS/390 R8 to z/OS V1R1
| Table 14 helps you migrate from the OS/390 R8 levels of elements, features, and
| products and points to books that contain appropriate migration and installation
| information.
| Table 14. Migrating from OS/390 R8 to z/OS V1R1
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| BCP OS/390 R8 BCP—> z/OS V1R1 M: z/OS MVS Migration and z/OS UNIX
| System Services Planning.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| BDT OS/390 R8 BDT—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BDT File-to-File OS/390 R8 BDT File-to-File—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.

110 z/OS V1R1.0 Planning for Installation

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| BDT SNA NJE OS/390 R8 BDT SNA NJE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager BookServer OS/390 R8 BookManager Not applicable.
| BookServer—> z/OS V1R1

| BookManager BookServer for World

| Wide Web for MVS/ESA V2.2—> z/OS
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager BUILD OS/390 R8 BookManager BUILD—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager READ OS/390 R8 BookManager READ—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| C/C++ IBM Open Class Library OS/390 R8 C/C++ IBM Open Class M: “Migration Actions for C/C++” on
| Library—> z/OS V1R1 page 142 and z/OS C/C++ Compiler and
| Run-Time Migration Guide.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| C/C++ with Debug Tool OS/390 R8 C/C++—> z/OS V1R1 M: “Migration Actions for C/C++” on
| page 142 and z/OS C/C++ Compiler and
| Except for Debug Tool: Not functionally Run-Time Migration Guide.
| equivalent, migration actions and
| installation (if CBPDO) are both required. I (if CBPDO): z/OS V1R1.0 Program
| For Debug Tool: Functionally equivalent, Directory.
| no installation (if CBPDO) is required.
| C/C++ without Debug Tool OS/390 R8 C/C++—> z/OS V1R1 M: “Migration Actions for C/C++” on
| page 142 and z/OS C/C++ Compiler and
| Not functionally equivalent, migration Run-Time Migration Guide.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Communications Server OS/390 R8 SecureWay M: z/OS Communications Server: IP
| Communications Server—> z/OS V1R1 Migration and z/OS Communications
| Server: SNA Migration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.

Chapter 6. Preparing for Migration 111

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Communications Server NPF No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R8 SecureWay I (if CBPDO): z/OS V1R1.0 Program
| Communications Server NPF—> z/OS Directory.
| V1R1

| Functionally equivalent but installation (if

| CBPDO) is required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 1 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R8 SecureWay I (if CBPDO): z/OS V1R1.0 Program
| Communications Server Security Directory.
| Level 1—> z/OS V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 2 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R8 SecureWay I (if CBPDO): z/OS V1R1.0 Program
| Communications Server Security Directory.
| Level 2—> z/OS V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 3 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R8 SecureWay I (if CBPDO): z/OS V1R1.0 Program
| Communications Server Security Directory.
| Level 3—> z/OS V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Cryptographic Services OS/390 R8 Cryptographic Services—> M: z/OS ICSF Administrator’s Guide and
| z/OS V1R1 z/OS ICSF System Programmer’s Guide.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DCE Application Support OS/390 R8 DCE Application Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.

112 z/OS V1R1.0 Planning for Installation

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| DCE Base Services OS/390 R8 DCE Base Services—> I (if CBPDO): z/OS V1R1.0 Program
| z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| DCE User Data Privacy CDMF OS/390 R8 DCE User Data Privacy Use the DCE Base Services base
| CDMF—> z/OS V1R1 element.

| DCE User Data Privacy CDMF was

| removed as an optional feature as of
| OS/390 R9. The function was merged
| into the DCE Base Services base
| element.
| DCE User Data Privacy OS/390 R8 DCE User Data Privacy Use the DCE Base Services base
| DES/CDMF DES/CDMF—> z/OS V1R1 element.

| DCE User Data Privacy DES/CDMF was

| removed as an optional feature as of
| OS/390 R9. The function was merged
| into the DCE Base Services base
| element.
| DFSMSdfp OS/390 R8 DFSMSdfp—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSMSdss OS/390 R8 DFSMSdss—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSMShsm OS/390 R8 DFSMShsm—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSMSrmm OS/390 R8 DFSMSrmm—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSORT OS/390 R8 DFSORT—> z/OS V1R1 Not applicable.

| DFSORT V1R14—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Distributed File Service OS/390 R8 Distributed File Service—> M: z/OS Distributed File Service
| z/OS V1R1 Customization and z/OS Distributed File
| Service SMB Administration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.

Chapter 6. Preparing for Migration 113

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Encina Toolkit Executive OS/390 R8 Encina Toolkit Not applicable.
| Executive—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| EREP OS/390 R8 EREP —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ESCON Director Support OS/390 R8 ESCON Director Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| FFST OS/390 R8 FFST —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM OS/390 R8 GDDM—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM-PGF OS/390 R8 GDDM-PGF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM-REXX OS/390 R8 GDDM-REXX—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| HCD OS/390 R8 HCD—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HCM OS/390 R8 HCM—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory and z/OS HCM User’s Guide.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HLASM OS/390 R8 HLASM—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HLASM V1R4—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.

114 z/OS V1R1.0 Planning for Installation

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| HLASM Toolkit OS/390 R8 HLASM Toolkit—> z/OS I (if CBPDO): z/OS V1R1.0 Program
| V1R1 Directory.

| HLASM Toolkit in HLASM V1R3—>

| z/OS V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| HLASM Toolkit in HLASM V1R4—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| IBM HTTP Server OS/390 R8 WebSphere Application M: z/OS HTTP Server Planning,
| Server—> z/OS V1R1 Installing, and Using.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and z/OS HTTP Server
| both required. Planning, Installing, and Using.
| IBM HTTP Server Export OS/390 R8 IBM HTTP Server Export Not applicable.
| Secure Secure—> z/OS V1R1

| Removed from OS/390 as of OS/390

| R10. It is no longer needed; the
| equivalent level of security is provided by
| base element Cryptographic Services.
| IBM HTTP Server France OS/390 R8 IBM HTTP Server France Not applicable.
| Secure Secure—> z/OS V1R1

| Removed from OS/390 as of OS/390

| R10. It is no longer needed; the
| equivalent level of security is provided by
| base element Cryptographic Services.
| IBM HTTP Server NA Secure No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory and z/OS HTTP Server
| Installation (if CBPDO) is required if the Planning, Installing, and Using.
| feature is ordered.
| OS/390 R8 IBM HTTP Server NA I (if CBPDO): z/OS V1R1.0 Program
| Secure—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| ICKDSF OS/390 R8 ICKDSF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ILM No prior product—> z/OS V1R1 M: “Migration Actions for ILM” on
| page 143.
| Migration actions and installation (if
| CBPDO) are both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.

Chapter 6. Preparing for Migration 115

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Infoprint Server IP PrintWay feature of PSF/MVS V2R2 M: “Migration Actions for Infoprint Server”
| or PSF V3R1—> z/OS V1R1 on page 144 and z/OS Infoprint Server
| Migration.
| NetSpool feature of PSF/MVS V2R2 or
| PSF V3R1—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are
| both required.
| OS/390 R8 Infoprint Server—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ISPF OS/390 R8 ISPF—> z/OS V1R1 M: For host-based services: z/OS ISPF
| Planning and Customizing. For
| Not functionally equivalent, migration client-server services: z/OS ISPF User’s
| actions and installation (if CBPDO) are Guide.
| both required.
| I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| JES2 OS/390 R8 JES2—> z/OS V1R1 M: “Migration Actions for JES2” on
| page 147 and z/OS JES2 Migration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required if you use JES2. Directory.
| JES3 OS/390 R8 JES3—> z/OS V1R1 M: z/OS JES3 Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required if you use JES3.
| LAN Server OS/390 R8 LAN Server—> z/OS V1R1 The OS/2 Front End Processor
| configurations from previous releases of
| OS/390 R9 was the last release to LAN Server are still supported on z/OS
| include both the workstation and host V1R1 for customers who want to migrate
| components. OS/390 R10 and z/OS to z/OS V1R1 prior to migrating off LAN
| V1R1 have only the host component. Server. See S/390 File and Print Serving,
| After z/OS V1R1, neither component will SG24-5330, for alternative solutions and
| be available. migration guidance.

116 z/OS V1R1.0 Planning for Installation

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Language Environment To z/OS V1R1 from pre-Language M: “Migration Actions for Language
| Environment run-time libraries: Environment” on page 147, z/OS
| v C/370 V1 and V2 Language Environment Run-Time
| v OS/VS COBOL Migration Guide, and:
| v VS COBOL II v z/OS C/C++ Compiler and Run-Time
| v VS FORTRAN V1 and V2 Migration Guide
| v OS PL/I V1 and V2 v COBOL for OS/390 & VM and COBOL
| for MVS & VM Compiler and Run-Time
| Not functionally equivalent, migration Migration Guide
| actions and installation (if CBPDO) are v Language Environment for MVS & VM
| both required. Fortran Run-Time Migration Guide
| Note: The listed products contain both a v PL/I for MVS & VM Compiler and
| compiler and a run-time library. The Run-Time Migration Guide
| object programs produced by the v VisualAge PL/I for OS/390 Compiler
| compilers are supported running under and Run-Time Migration Guide
| z/OS Language Environment, although
| not all of the compilers themselves are I (if CBPDO): z/OS V1R1.0 Program
| still supported. Directory.
| OS/390 R8 Language Environment—> M: “Migration Actions for Language
| z/OS V1R1 Environment” on page 147 and z/OS
| Language Environment Run-Time
| Not functionally equivalent, migration Migration Guide.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Language Environment Data OS/390 R8 Language Environment Use the Language Environment base
| Decryption Data Decryption—> z/OS V1R1 element.

| Language Environment Data Decryption

| was removed as an optional feature as of
| OS/390 R9. The function was merged
| into the Language Environment base
| element.
| LANRES OS/390 R8 LANRES—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| MICR/OCR OS/390 R8 MICR/OCR—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| msys for Setup No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required.
| Network File System OS/390 R8 Network File System—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| OCSF France OS/390 R8 OCSF France—> z/OS V1R1 Use the Cryptographic Services base
| element.
| OCSF France was removed as an
| optional feature as of OS/390 R9. The
| function was merged into the
| Cryptographic Services base element.

Chapter 6. Preparing for Migration 117

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| OCSF Security Level 1 OCSF R8 Security Level 1—> z/OS Use the Cryptographic Services base
| V1R1 element.

| OCSF Security Level 1 was removed as

| an optional feature as of OS/390 R9. The
| function was merged into the
| Cryptographic Services base element.
| OCSF Security Level 2 OS/390 R8 OCSF Security Level 2—> Use the Cryptographic Services base
| z/OS V1R1 element.

| OCSF Security Level 2 was removed as

| an optional feature as of OS/390 R9. The
| function was merged into the
| Cryptographic Services base element.
| OCSF Security Level 3 No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R8 OCSF Security Level 3—> I (if CBPDO): z/OS V1R1.0 Program
| z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| OSA/SF OS/390 R8 OSA/SF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| RMF OS/390 R8 RMF—> z/OS V1R1 M: RMF User’s Guide.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and RMF User’s Guide.
| both required.
| SDSF OS/390 R8 SDSF—> z/OS V1R1 M: z/OS SDSF Operation and
| Customization.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required if you use JES2. Directory.

118 z/OS V1R1.0 Planning for Installation

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| SecureWay Security Server OS/390 R8 Security Server—> z/OS M: z/OS SecureWay Security Server
| V1R1 RACF Migration, z/OS SecureWay
| Security Server LDAP Server
| DCE Security Server component: Not Administration and Use, and z/OS
| functionally equivalent, no migration SecureWay Security Server Firewall
| actions, installation (if CBPDO) is Technologies.
| required.
| I (if CBPDO): z/OS V1R1.0 Program
| RACF, LDAP Server, and Firewall Directory.
| Technologies components: Not
| functionally equivalent, migration actions
| and installation (if CBPDO) are both
| required.

| OCEP component: Not functionally

| equivalent, no migration actions,
| installation (if CBPDO) is required.

| Network Authentication and Privacy

| Service component: New function,
| installation (if CBPDO) is required.
| SMP/E OS/390 R8 SMP/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Softcopy Print OS/390 R8 Softcopy Print—> z/OS See Softcopy Print in Table 2 on page 20.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| SOMobjects ADE OS/390 R8 SOMobjects ADE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| SOMobjects RTL OS/390 R8 SOMobjects RTL—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| System SSL Security Level 2 OS/390 R8 System SSL Security Level Use the Cryptographic Services base
| 2—> z/OS V1R1 element.

| System SSL Security Level 2 was

| removed as an optional feature as of
| OS/390 R10. The function was merged
| into the Cryptographic Services base
| element.

Chapter 6. Preparing for Migration 119

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| System SSL Security Level 3 No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R8 System SSL Security Level I (if CBPDO): z/OS V1R1.0 Program
| 3—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Text Search OS/390 R8 Text Search—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| TIOC OS/390 R8 TIOC—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Tivoli Management Framework OS/390 R8 Tivoli Management I (if CBPDO): z/OS V1R1.0 Program
| Framework—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| TSO/E OS/390 R8 TSO/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| VisualLift ADE OS/390 R8 VisualLift ADE—> z/OS None.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| VisualLift RTE OS/390 R8 VisualLift RTE—> z/OS None.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| WebSphere Application Server OS/390 R8 WebSphere Application Use the stand-alone product WebSphere
| Server—> z/OS V1R1 Application Server for OS/390 V3
| (5655-A98).
| Removed from OS/390 as of OS/390
| R10.

120 z/OS V1R1.0 Planning for Installation

| Table 14. Migrating from OS/390 R8 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| z/OS UNIX System Services OS/390 R8 UNIX System Services—> M: z/OS UNIX System Services
| z/OS V1R1 Planning.

| Application Services component: Not I (if CBPDO): z/OS V1R1.0 Program

| functionally equivalent, migration actions Directory.
| and installation (if CBPDO) are both
| required.

| Connection Manager and Process

| Manager components: Functionally
| equivalent, no installation (if CBPDO) is
| required.

| Integrated Call Level Interface

| component: Not functionally equivalent,
| no migration actions, installation (if
| CBPDO) is required.
| 3270 PC File Transfer 3270 PC File Transfer Program—> Not applicable.
| Program z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
|
|
| Migrating from OS/390 R9 to z/OS V1R1
| Table 15 helps you migrate from the OS/390 R9 levels of elements, features, and
| products and points to books that contain appropriate migration and installation
| information.
| Table 15. Migrating from OS/390 R9 to z/OS V1R1
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| BCP OS/390 R9 BCP—> z/OS V1R1 M: z/OS MVS Migration and z/OS UNIX
| System Services Planning.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| BDT OS/390 R9 BDT—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BDT File-to-File OS/390 R9 BDT File-to-File—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BDT SNA NJE OS/390 R9 BDT SNA NJE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.

Chapter 6. Preparing for Migration 121

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| BookManager BookServer OS/390 R9 BookManager Not applicable.
| BookServer—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager BUILD OS/390 R9 BookManager BUILD—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| BookManager READ OS/390 R9 BookManager READ—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| C/C++ IBM Open Class Library OS/390 R9 C/C++ IBM Open Class M: “Migration Actions for C/C++” on
| Library—> z/OS V1R1 page 142 and z/OS C/C++ Compiler and
| Run-Time Migration Guide.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| C/C++ with Debug Tool OS/390 R9 C/C++—> z/OS V1R1 M: “Migration Actions for C/C++” on
| page 142 and z/OS C/C++ Compiler and
| Except for Debug Tool: Not functionally Run-Time Migration Guide.
| equivalent, migration actions and
| installation (if CBPDO) are both required. I (if CBPDO): z/OS V1R1.0 Program
| For Debug Tool: Functionally equivalent, Directory.
| no installation (if CBPDO) is required.
| C/C++ without Debug Tool OS/390 R9 C/C++—> z/OS V1R1 M: “Migration Actions for C/C++” on
| page 142 and z/OS C/C++ Compiler and
| Not functionally equivalent, migration Run-Time Migration Guide.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Communications Server OS/390 R9 SecureWay M: z/OS Communications Server: IP
| Communications Server—> z/OS V1R1 Migration and z/OS Communications
| Server: SNA Migration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| Communications Server NPF No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R9 SecureWay I (if CBPDO): z/OS V1R1.0 Program
| Communications Server NPF—> z/OS Directory.
| V1R1

| Functionally equivalent but installation (if

| CBPDO) is required.

122 z/OS V1R1.0 Planning for Installation

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 1 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R9 SecureWay I (if CBPDO): z/OS V1R1.0 Program
| Communications Server Security Directory.
| Level 1—> z/OS V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 2 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R9 SecureWay I (if CBPDO): z/OS V1R1.0 Program
| Communications Server Security Directory.
| Level 2—> z/OS V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Communications Server No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Security Level 3 Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R9 SecureWay I (if CBPDO): z/OS V1R1.0 Program
| Communications Server Security Directory.
| Level 3—> z/OS V1R1

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Cryptographic Services OS/390 R9 Cryptographic Services—> M: z/OS ICSF Administrator’s Guide and
| z/OS V1R1 z/OS ICSF System Programmer’s Guide.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DCE Application Support OS/390 R9 DCE Application Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| DCE Base Services OS/390 R9 DCE Base Services—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| DFSMSdfp OS/390 R9 DFSMSdfp—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.

Chapter 6. Preparing for Migration 123

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| DFSMSdss OS/390 R9 DFSMSdss—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSMShsm OS/390 R9 DFSMShsm—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSMSrmm OS/390 R9 DFSMSrmm—> z/OS V1R1 M: z/OS DFSMS Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required.
| DFSORT OS/390 R9 DFSORT—> z/OS V1R1 Not applicable.

| DFSORT V1R14—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Distributed File Service OS/390 R9 Distributed File Service—> M: z/OS Distributed File Service
| z/OS V1R1 Customization and z/OS Distributed File
| Service SMB Administration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required. Directory.
| Encina Toolkit Executive OS/390 R9 Encina Toolkit Not applicable.
| Executive—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| EREP OS/390 R9 EREP —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ESCON Director Support OS/390 R9 ESCON Director Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| FFST OS/390 R9 FFST —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM OS/390 R9 GDDM—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| GDDM-PGF OS/390 R9 GDDM-PGF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.

124 z/OS V1R1.0 Planning for Installation

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| GDDM-REXX OS/390 R9 GDDM-REXX—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| HCD OS/390 R9 HCD—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| HCM OS/390 R9 HCM—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| HLASM OS/390 R9 HLASM—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.
| HLASM V1R4—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| HLASM Toolkit OS/390 R9 HLASM Toolkit—> z/OS I (if CBPDO): z/OS V1R1.0 Program
| V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| HLASM Toolkit in HLASM V1R4—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| IBM HTTP Server OS/390 R9 IBM HTTP Server—> z/OS M: z/OS HTTP Server Planning,
| V1R1 Installing, and Using.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and z/OS HTTP Server
| both required. Planning, Installing, and Using.
| IBM HTTP Server Export OS/390 R9 IBM HTTP Server Export Not applicable.
| Secure Secure—> z/OS V1R1

| Removed from OS/390 as of OS/390

| R10. It is no longer needed; the
| equivalent level of security is provided by
| base element Cryptographic Services.
| IBM HTTP Server France OS/390 R9 IBM HTTP Server France Not applicable.
| Secure Secure—> z/OS V1R1

| Removed from OS/390 as of OS/390

| R10. It is no longer needed; the
| equivalent level of security is provided by
| base element Cryptographic Services.

Chapter 6. Preparing for Migration 125

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| IBM HTTP Server NA Secure No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory and z/OS HTTP Server
| Installation (if CBPDO) is required if the Planning, Installing, and Using.
| feature is ordered.
| OS/390 R9 IBM HTTP Server NA I (if CBPDO): z/OS V1R1.0 Program
| Secure—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| ICKDSF OS/390 R9 ICKDSF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ILM No prior product—> z/OS V1R1 M: “Migration Actions for ILM” on
| page 143.
| Migration actions and installation (if
| CBPDO) are both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Infoprint Server IP PrintWay feature of PSF/MVS V2R2 M: “Migration Actions for Infoprint Server”
| or PSF V3R1—> z/OS V1R1 on page 144 and z/OS Infoprint Server
| Migration.
| NetSpool feature of PSF/MVS V2R2 or
| PSF V3R1—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are
| both required.
| OS/390 R9 Infoprint Server—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| ISPF OS/390 R9 ISPF—> z/OS V1R1 M: For host-based services: z/OS ISPF
| Planning and Customizing. For
| Not functionally equivalent, migration client-server services: z/OS ISPF User’s
| actions and installation (if CBPDO) are Guide.
| both required.
| I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| JES2 OS/390 R9 JES2—> z/OS V1R1 M: “Migration Actions for JES2” on
| page 147 and z/OS JES2 Migration.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required if you use JES2. Directory.
| JES3 OS/390 R9 JES3—> z/OS V1R1 M: z/OS JES3 Migration.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory.
| both required if you use JES3.

126 z/OS V1R1.0 Planning for Installation

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| LAN Server OS/390 R9 LAN Server—> z/OS V1R1 The OS/2 Front End Processor
| configurations from previous releases of
| OS/390 R9 was the last release to LAN Server are still supported on z/OS
| include both the workstation and host V1R1 for customers who want to migrate
| components. OS/390 R10 and z/OS to z/OS V1R1 prior to migrating off LAN
| V1R1 have only the host component. Server. See S/390 File and Print Serving,
| After z/OS V1R1, neither component will SG24-5330, for alternative solutions and
| be available. migration guidance.
| Language Environment To z/OS V1R1 from pre-Language M: “Migration Actions for Language
| Environment run-time libraries: Environment” on page 147, z/OS
| v C/370 V1 and V2 Language Environment Run-Time
| v OS/VS COBOL Migration Guide, and:
| v VS COBOL II v z/OS C/C++ Compiler and Run-Time
| v VS FORTRAN V1 and V2 Migration Guide
| v OS PL/I V1 and V2 v COBOL for OS/390 & VM and COBOL
| for MVS & VM Compiler and Run-Time
| Not functionally equivalent, migration Migration Guide
| actions and installation (if CBPDO) are v Language Environment for MVS & VM
| both required. Fortran Run-Time Migration Guide
| Note: The listed products contain both a v PL/I for MVS & VM Compiler and
| compiler and a run-time library. The Run-Time Migration Guide
| object programs produced by the v VisualAge PL/I for OS/390 Compiler
| compilers are supported running under and Run-Time Migration Guide
| z/OS Language Environment, although
| not all of the compilers themselves are I (if CBPDO): z/OS V1R1.0 Program
| still supported. Directory.
| OS/390 R9 Language Environment—> M: “Migration Actions for Language
| z/OS V1R1 Environment” on page 147 and z/OS
| Language Environment Run-Time
| Not functionally equivalent, migration Migration Guide.
| actions and installation (if CBPDO) are
| both required. I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| LANRES OS/390 R9 LANRES—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| MICR/OCR OS/390 R9 MICR/OCR—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| msys for Setup No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required.
| Network File System OS/390 R9 Network File System—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.

Chapter 6. Preparing for Migration 127

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| OCSF Security Level 3 No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R9 OCSF Security Level 3—> I (if CBPDO): z/OS V1R1.0 Program
| z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required if the feature is ordered.
| OSA/SF OS/390 R9 OSA/SF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| RMF OS/390 R9 RMF—> z/OS V1R1 M: RMF User’s Guide.

| Not functionally equivalent, migration I (if CBPDO): z/OS V1R1.0 Program

| actions and installation (if CBPDO) are Directory and RMF User’s Guide.
| both required.
| SDSF OS/390 R9 SDSF—> z/OS V1R1 M: z/OS SDSF Operation and
| Customization.
| Not functionally equivalent, migration
| actions and installation (if CBPDO) are I (if CBPDO): z/OS V1R1.0 Program
| both required if you use JES2. Directory.
| SecureWay Security Server OS/390 R9 Security Server—> z/OS M: z/OS SecureWay Security Server
| V1R1 RACF Migration, z/OS SecureWay
| Security Server LDAP Server
| DCE Security Server component: Administration and Use, and z/OS
| Functionally equivalent, no installation (if SecureWay Security Server Firewall
| CBPDO) is required. Technologies.
| RACF, LDAP Server, and Firewall I (if CBPDO): z/OS V1R1.0 Program
| Technologies components: Not Directory.
| functionally equivalent, migration actions
| and installation (if CBPDO) are both
| required.

| OCEP component: Not functionally

| equivalent, no migration actions,
| installation (if CBPDO) is required.

| Network Authentication and Privacy

| Service component: New function,
| installation (if CBPDO) is required.
| SMP/E OS/390 R9 SMP/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Softcopy Print OS/390 R9 Softcopy Print—> z/OS See Softcopy Print in Table 2 on page 20.
| V1R1

| Removed from OS/390 as of OS/390

| R10.

128 z/OS V1R1.0 Planning for Installation

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| SOMobjects ADE OS/390 R9 SOMobjects ADE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| SOMobjects RTL OS/390 R9 SOMobjects RTL—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| System SSL Security Level 2 OS/390 R9 System SSL Security Level Use the Cryptographic Services base
| 2—> z/OS V1R1 element.

| System SSL Security Level 2 was

| removed as an optional feature as of
| OS/390 R10. The function was merged
| into the Cryptographic Services base
| element.
| System SSL Security Level 3 No prior product—> z/OS V1R1 I (if CBPDO): z/OS V1R1.0 Program
| Directory.
| Installation (if CBPDO) is required if the
| feature is ordered.
| OS/390 R9 System SSL Security Level I (if CBPDO): z/OS V1R1.0 Program
| 3—> z/OS V1R1 Directory.

| Not functionally equivalent, no migration

| actions, installation (if CBPDO) is
| required.
| Text Search OS/390 R9 Text Search—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| TIOC OS/390 R9 TIOC—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| Tivoli Management Framework OS/390 R9 Tivoli Management Not applicable.
| Framework—> z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
| TSO/E OS/390 R9 TSO/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation (if

| CBPDO) is required.
| VisualLift ADE OS/390 R9 VisualLift ADE—> z/OS None.
| V1R1

| Removed from OS/390 as of OS/390

| R10.

Chapter 6. Preparing for Migration 129

| Table 15. Migrating from OS/390 R9 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| VisualLift RTE OS/390 R9 VisualLift RTE—> z/OS None.
| V1R1

| Removed from OS/390 as of OS/390

| R10.
| WebSphere Application Server OS/390 R9 WebSphere Application Use the stand-alone product WebSphere
| Server—> z/OS V1R1 Application Server for OS/390 V3
| (5655-A98).
| Removed from OS/390 as of OS/390
| R10.
| z/OS UNIX System Services OS/390 R9 UNIX System Services—> I (if CBPDO): z/OS V1R1.0 Program
| z/OS V1R1 Directory.

| Application Services and Integrated Call

| Level Interface components: Not
| functionally equivalent, no migration
| actions, installation (if CBPDO) is
| required.

| Connection Manager and Process

| Manager components: Functionally
| equivalent, no installation (if CBPDO) is
| required.
| 3270 PC File Transfer 3270 PC File Transfer Program—> Not applicable.
| Program z/OS V1R1

| Functionally equivalent, no installation (if

| CBPDO) is required.
|
|
| Migrating from OS/390 R10 to z/OS V1R1
| Table 16 helps you migrate from the OS/390 R10 levels of elements, features, and
| products and points to books that contain appropriate migration and installation
| information.

| If you’re migrating from OS/390 R10, the z/OS V1R1 Upgrade Package for OS/390
| V2R10 is the deliverable to order. However, if you want any optional features you
| never had before, you have to additionally order the z/OS product to get the
| features. Order z/OS using the CBPDO selective service option.
| Table 16. Migrating from OS/390 R10 to z/OS V1R1
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| BCP OS/390 R10 BCP—> z/OS V1R1 M: z/OS MVS Migration.

| Not functionally equivalent, migration I : z/OS V1R1.0 Program Directory

| actions and installation are both required. Upgrade Package.
| For installation, use the z/OS V1R1
| Upgrade Package for OS/390 V2R10.
| BDT OS/390 R10 BDT—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.

130 z/OS V1R1.0 Planning for Installation

| Table 16. Migrating from OS/390 R10 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| BDT File-to-File OS/390 R10 BDT File-to-File—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| BDT SNA NJE OS/390 R10 BDT SNA NJE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| BookManager BookServer OS/390 R10 BookManager Not applicable.
| BookServer—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| BookManager BUILD OS/390 R10 BookManager BUILD—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation is

| required.
| BookManager READ OS/390 R10 BookManager READ—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation is

| required.
| C/C++ IBM Open Class Library OS/390 R10 C/C++ IBM Open Class Not applicable.
| Library—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| C/C++ with Debug Tool OS/390 R10 C/C++—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| C/C++ without Debug Tool OS/390 R10 C/C++—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| Communications Server OS/390 R10 SecureWay Not applicable.
| Communications Server—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| Communications Server NPF No prior product—> z/OS V1R1 I: z/OS V1R1.0 Program Directory.

| Installation using CBPDO is required if

| the feature is ordered.
| OS/390 R10 IBM Communications Not applicable.
| Server NPF—> z/OS V1R1

| Functionally equivalent, no installation is

| required.

Chapter 6. Preparing for Migration 131

| Table 16. Migrating from OS/390 R10 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Communications Server No prior product—> z/OS V1R1 I: z/OS V1R1.0 Program Directory.
| Security Level 1
| Installation using CBPDO is required if
| the feature is ordered.
| OS/390 R10 IBM Communications Not applicable.
| Server Security Level 1—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| Communications Server No prior product—> z/OS V1R1 I: z/OS V1R1.0 Program Directory.
| Security Level 2
| Installation using CBPDO is required if
| the feature is ordered.
| OS/390 R10 IBM Communications Not applicable.
| Server Security Level 2—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| Communications Server No prior product—> z/OS V1R1 I: z/OS V1R1.0 Program Directory.
| Security Level 3
| Installation using CBPDO is required if
| the feature is ordered.
| OS/390 R10 IBM Communications Not applicable.
| Server Security Level 3—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| Cryptographic Services OS/390 R10 Cryptographic Not applicable.
| Services—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| DCE Application Support OS/390 R10 DCE Application Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| DCE Base Services OS/390 R10 DCE Base Services—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation is

| required.
| DFSMSdfp OS/390 R10 DFSMSdfp—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| DFSMSdss OS/390 R10 DFSMSdss—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| DFSMShsm OS/390 R10 DFSMShsm—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.

132 z/OS V1R1.0 Planning for Installation

| Table 16. Migrating from OS/390 R10 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| DFSMSrmm OS/390 R10 DFSMSrmm—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| DFSORT OS/390 R10 DFSORT—> z/OS V1R1 Not applicable.

| DFSORT V1R14—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| Distributed File Service OS/390 R10 Distributed File Service—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation is

| required.
| Encina Toolkit Executive OS/390 R10 Encina Toolkit Not applicable.
| Executive—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| EREP OS/390 R10 EREP —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| ESCON Director Support OS/390 R10 ESCON Director Not applicable.
| Support—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| FFST OS/390 R10 FFST —> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| GDDM OS/390 R10 GDDM—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| GDDM-PGF OS/390 R10 GDDM-PGF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| GDDM-REXX OS/390 R10 GDDM-REXX—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| HCD OS/390 R10 HCD—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| HCM OS/390 R10 HCM—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.

Chapter 6. Preparing for Migration 133

| Table 16. Migrating from OS/390 R10 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| HLASM OS/390 R10 HLASM—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| HLASM Toolkit OS/390 R10 HLASM Toolkit—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| IBM HTTP Server OS/390 R10 IBM HTTP Server—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| IBM HTTP Server NA Secure No prior product—> z/OS V1R1 I: z/OS V1R1.0 Program Directory and
| z/OS HTTP Server Planning, Installing,
| Installation using CBPDO is required if and Using.
| the feature is ordered.
| OS/390 R10 IBM HTTP Server NA Not applicable.
| Secure—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| ICKDSF OS/390 R10 ICKDSF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| ILM No prior product—> z/OS V1R1 M: “Migration Actions for ILM” on
| page 143.
| Migration actions are required. Also,
| installation using the z/OS V1R1 I : z/OS V1R1.0 Program Directory
| Upgrade Package for OS/390 V2R10 is Upgrade Package.
| required.
| Infoprint Server IP PrintWay feature of PSF/MVS V2R2 M: “Migration Actions for Infoprint Server”
| or PSF V3R1—> z/OS V1R1 on page 144 and z/OS Infoprint Server
| Migration.
| NetSpool feature of PSF/MVS V2R2 or
| PSF V3R1—> z/OS V1R1 I: z/OS V1R1.0 Program Directory.

| Not functionally equivalent, migration

| actions and installation using CBPDO are
| both required.
| OS/390 R10 Infoprint Server—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| ISPF OS/390 R10 ISPF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.

134 z/OS V1R1.0 Planning for Installation

| Table 16. Migrating from OS/390 R10 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| JES2 OS/390 R10 JES2—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| JES3 OS/390 R10 JES3—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| LAN Server OS/390 R10 LAN Server—> z/OS V1R1 The OS/2 Front End Processor
| configurations from previous releases of
| OS/390 R9 was the last release to LAN Server are still supported on z/OS
| include both the workstation and host V1R1 for customers who want to migrate
| components. OS/390 R10 and z/OS to z/OS V1R1 prior to migrating off LAN
| V1R1 have only the host component. Server. See S/390 File and Print Serving,
| After z/OS V1R1, neither component will SG24-5330, for alternative solutions and
| be available. migration guidance.
| Language Environment To z/OS V1R1 from pre-Language M: “Migration Actions for Language
| Environment run-time libraries: Environment” on page 147, z/OS
| v C/370 V1 and V2 Language Environment Run-Time
| v OS/VS COBOL Migration Guide, and:
| v VS COBOL II v z/OS C/C++ Compiler and Run-Time
| v VS FORTRAN V1 and V2 Migration Guide
| v OS PL/I V1 and V2 v COBOL for OS/390 & VM and COBOL
| for MVS & VM Compiler and Run-Time
| Not functionally equivalent, migration Migration Guide
| actions and installation using CBPDO are v Language Environment for MVS & VM
| both required. Fortran Run-Time Migration Guide
| Note: The listed products contain both a v PL/I for MVS & VM Compiler and
| compiler and a run-time library. The Run-Time Migration Guide
| object programs produced by the v VisualAge PL/I for OS/390 Compiler
| compilers are supported running under and Run-Time Migration Guide
| z/OS Language Environment, although
| not all of the compilers themselves are I: z/OS V1R1.0 Program Directory.
| still supported.
| OS/390 R10 Language Environment—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation is

| required.
| LANRES OS/390 R10 LANRES—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| MICR/OCR OS/390 R10 MICR/OCR—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| msys for Setup No prior product—> z/OS V1R1 I : z/OS V1R1.0 Program Directory
| Upgrade Package.
| Installation using the z/OS V1R1
| Upgrade Package for OS/390 V2R10 is
| required.

Chapter 6. Preparing for Migration 135

| Table 16. Migrating from OS/390 R10 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Network File System OS/390 R10 Network File System—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation is

| required.
| OCSF Security Level 3 No prior product—> z/OS V1R1 I: z/OS V1R1.0 Program Directory.

| Installation using CBPDO is required if

| the feature is ordered.
| OS/390 R10 OCSF Security Level 3—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation is

| required.
| OSA/SF OS/390 R10 OSA/SF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| RMF OS/390 R10 RMF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| SDSF OS/390 R10 SDSF—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| SecureWay Security Server OS/390 R10 Security Server—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| SMP/E OS/390 R10 SMP/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| SOMobjects ADE OS/390 R10 SOMobjects ADE—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| SOMobjects RTL OS/390 R10 SOMobjects RTL—> z/OS Not applicable.
| V1R1

| Functionally equivalent, no installation is

| required.
| System SSL Security Level 3 No prior product—> z/OS V1R1 I: z/OS V1R1.0 Program Directory.

| Installation using CBPDO is required if

| the feature is ordered.
| OS/390 R10 System SSL Security Not applicable.
| Level 3—> z/OS V1R1

| Functionally equivalent, no installation is

| required.

136 z/OS V1R1.0 Planning for Installation

| Table 16. Migrating from OS/390 R10 to z/OS V1R1 (continued)
| Element or feature If you are migrating through the Look for migration (M) and installation
| following paths: (I) information in the following:
| Text Search OS/390 R10 Text Search—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| TIOC OS/390 R10 TIOC—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| Tivoli Management Framework OS/390 R10 Tivoli Management Not applicable.
| Framework—> z/OS V1R1

| Functionally equivalent, no installation is

| required.
| TSO/E OS/390 R10 TSO/E—> z/OS V1R1 Not applicable.

| Functionally equivalent, no installation is

| required.
| z/OS UNIX System Services OS/390 R10 UNIX System Services—> Not applicable.
| z/OS V1R1

| Functionally equivalent, no installation is

| required.
| 3270 PC File Transfer 3270 PC File Transfer Program—> Not applicable.
| Program z/OS V1R1

| Functionally equivalent, no installation is

| required.
|
|
Identifying Migration Actions Needed for ISV Products
First, check to make sure that your level of the product supports the z/OS
environment. Ask the ISV how z/OS affects the use of the product. If the product
does not intersect with z/OS, place the products in their own sets of libraries and
SMP/E zones. This means that, unless you have to change product code, such as
applying PTFs, or obtain a new level of the product, you will not need to reinstall it
after you install a new ServerPac or SystemPac.

For those using SystemPac, if the ISV products are selectable in the SystemPac
shopping list, configure them such that they are placed on a separate volume and
in their own SMP/E zones. You can either (1) place all the selectable ISV products
in one SMP/E zone, separate from IBM products, or (2) separate ISV products even
further by placing products from different vendors in their own unique zone. Use the
Local Order Entry tool during order placement to perform the separation. For details
about the tool, refer to:
http://www.ibm.com/ca/custompac/

For the addresses of World Wide Web sites dealing with ISV products, see
“Choosing ISV Products That You Want to Run with z/OS” on page 61.

Chapter 6. Preparing for Migration 137

Miscellaneous Migration Actions
You will find some of the topics in this section discussed in other books as well.
They are repeated here because of their importance.

Migrating Files in the /etc Directory

Migration of system control files includes the migration of members of parmlib and
proclib as well as files in the /etc directory. During installation, IBM defines
directories in the /etc directory but does not install files there. Because the
configuration and customization data in your existing /etc directory might not be
correct for the new system, you might need to make changes to the files in your
new /etc directory. IBM recommends that you make these changes before the first
IPL of the new system.

For steps to make a copy of your existing /etc directory, see z/OS V1R1.0 Program
Directory. For information about changes you should make to /etc before the first
IPL, see the various element and feature migration books listed in the migration
tables in this chapter.

Migrating Your Application Development Environment

Before OS/390, you were able to migrate your application development environment
independent of your production system upgrade schedule. In addition, a common
practice was to upgrade application development systems with the newest level of
the operating system, exposing application developers to the newest level and
allowing them to be “testers” to help uncover as many problems as possible before
cutover to production. If you use these same techniques in the z/OS environment,
so that your applications are compiled and link-edited on a later level of z/OS than
the level of the production systems that run the applications, you could encounter
the “downward compatibility” problem.

The “downward compatibility” problem is really an incompatibility problem that

stems from the integration of certain application development environments into
z/OS, such as Language Environment, the C/C++ Compiler, and the C/C++ IBM
Open Class Library. It can occur if you develop applications on systems running a
later level of z/OS than the production centers running these applications. It can
occur even though the applications are not using any of the new functions provided
in the later-level application development environment.

As a general recommendation, customer-written applications that make use of

application development environments provided with z/OS should be developed
(assembled, compiled, or link-edited) using the lowest level of that application
development environment. This ensures that the applications will successfully
execute on any system at that level or later.

For information about cases where IBM has done specific things to assist you, see
“Migration Actions for C/C++” on page 142 and “Developing Applications with
Language Environment in z/OS” on page 148.

Migration Actions for BookManager BookServer

The stand-alone product BookManager BookServer V2R1 is functionally equivalent
to the BookManager BookServer base element in OS/390 R6 and R7. The
stand-alone product BookManager BookServer V2R2 runs on OS/390 R6 and R7,
and is functionally equivalent to the BookManager BookServer base element in
OS/390 R8 and later (including z/OS). If you are migrating from the V2R1 to V2R2

138 z/OS V1R1.0 Planning for Installation

 level of BookManager BookServer, whether stand-alone product or z/OS base
element, you must perform the migration actions described in this section.

The migration actions primarily involve modifying or copying, or both, your existing
(customized) configuration files, note files, and picture cache. Using your existing
files and cache, rather than creating new ones, preserves your configuration
settings, notes, and pictures, and lets you avoid having to redo administrative tasks.
Therefore, as you get ready to migrate, do not delete or alter your existing
configuration files or any files in the /notes or /pictures directories, unless you do
not intend to use them with the new level of BookManager BookServer.

The migration actions also affect BookRead, the application programming interface
(API).

| Changed Executable
| The name of the executable in the V2R1 level of BookManager BookServer, which
| is BOOKMGR.CMD, has been changed to BOOKMGR.EXE in the V2R2 level. This
| change results from the elimination of the REXX exec (BOOKMGR.CMD) in favor of
| a C program executable (BOOKMGR.EXE). In order to maintain compatibility with
| V2R1 Web addresses, including bookmarks, an exec directive (for Web server
| configuration) is provided in z/OS V1R1.0 Program Directory. This exec directive
| (exec /bookmgr-cgi/bookmgr.cmd* /usr/lpp/booksrv/cgi-bin/bookmgr.exe) will
| “translate” BookManager BookServer V2R1 Web addresses to V2R2 Web
| addresses.

Configuration Files
The configuration files in the V2R2 level of BookManager BookServer have
changed as follows:
v FOOTER has been moved from .../cgi-bin/bookmgr.conf to .../cgi-
bin/booksrv.conf.
v To support the frames-based end user interface, FRAMES has been added to
.../cgi-bin/booksrv.conf.
v FRAMESDIR has been added to .../cgi-bin/bookmgr.conf.
v LOGDIR (parameter in .../cgi-bin/bookmgr.conf) specifies the directory for some
additional files.

Modify your configuration files as follows. For simplicity, make your changes to your
existing (customized) /etc/booksrv/bookmgr.80 and /etc/booksrv/booksrv.80, or the
equivalent configuration files for your installation, rather than copying and
customizing the samples in .../cgi-bin/.
v Edit /etc/booksrv/bookmgr.80. Remove the FOOTER line and add a FRAMESDIR
line. FRAMESDIR specifies the directory to use for building and caching frames
from BookManager BOOKs. If you do not specify a value, the default is the
.../public/bookmgr/frames/ subdirectory.
When a BookServer client requests display of a page from a BOOK, the frames
HTML is placed in this directory so that the client can access it. Once displayed,
the frames are left in the directory to speed future retrieval. The specified
directory must be readable, writable, and searchable by BookServer users.
Therefore, the initial mode setting for the directory should be 777.
To specify your own directory, enter the fully-qualified path name of a directory.
The directory must already exist. Do not end the path name with a forward slash,
for example, do not specify:
.../public/bookmgr/frames/

The correct way to specify this path would be:

Chapter 6. Preparing for Migration 139

 .../public/bookmgr/frames

If you specify FRAMESDIR, you must add a pass rule statement to the
appropriate webserver configuration file. For example, if FRAMESDIR is specified
as /var/booksrv/frames, the pass rule is:
Pass /bookmgr/frames/* /var/booksrv/frames/*

This pass rule must precede the pass rule for /bookmgr/*.
v Edit /etc/booksrv/booksrv.80. Add a FOOTER line, with the value of FOOTER
equal to the same value as in file ..../bookmgr.80. Add another FRAMES line,
with the value FRAMES=0. (FOOTER and FRAMES are updated through the
Administration panel.)
v LOGDIR specifies the directory of the BOOK access log (filename bookmgr.log),
the diagnostic output log (bookmgr.dbg), the site customized Library page header
(library.htm), the site customized header (bmheader.htm), and the site
customized footer (bmfooter.htm). If used, all five files must reside in the same
directory, which you specify with the LOGDIR parameter. The default directory for
LOGDIR is /usr/lpp/booksrv/cgi-bin/. To specify your own directory, enter the
fully-qualified path name of a directory. The directory must already exist. The
initial mode setting for the directory should be 755. Do not end the path name
with a forward slash, for example, do not specify:
.../usr/lpp/booksrv/cgi-bin/

The correct way to specify this path would be:

.../usr/lpp/booksrv/cgi-bin

You can modify the site customized Library page header, the site customized
header, and the site customized footer, as follows:
– To use a customized Library page header, copy file .../cgi-bin/library.samp to
the directory specified on the LOGDIR parameter (or the default directory),
renaming library.samp to library.htm. If you do not want to use a customized
Library page header, do not place a library.htm into the LOGDIR directory.

Note: Use of a Library page header could slightly degrade performance.

– A customized header can be displayed at the top of most pages. To use a
customized header, copy file .../cgi-bin/custhead.htm to the directory specified
on the LOGDIR parameter (or the default directory), renaming custhead.htm
to bmheader.htm. Customize bmheader.htm as desired. Directions for
implementing a customized header are contained in .../cgi-bin/custhead.htm. If
you do not want to use a customized header, then do not place a
bmheader.htm into the LOGDIR directory.

Note: Use of a customized header could slightly degrade performance.

– A customized footer can be displayed on the bottom of all pages. To use a
customized footer, copy file .../cgi-bin/custfoot.htm to the directory specified on
the LOGDIR parameter (or the default directory), renaming custfoot.htm to
bmfooter.htm. Customize bmfooter.htm as desired. Directions for implementing
a customized footer are contained in .../cgi-bin/bmfooter.htm. If you do not
want to use a customized footer, then do not place a bmfooter.htm into the
LOGDIR directory.

Note: Use of a customized footer could slightly degrade performance.

140 z/OS V1R1.0 Planning for Installation

Note Files
Migrating the notes in the notes directory will make them available to the V2R2
level of BookServer. If you do not migrate them, they will not appear in the books in
which they were entered.

To migrate book notes, copy all the files from your existing notes directory to the
new one. The default directory for saving book notes is
/usr/lpp/booksrv/public/bookmgr/notes. You can override this default by specifying a
directory on the NOTEDIR parameter of the /etc/booksrv/bookmgr.80 configuration
file.

Picture Cache
Migrating the pictures in picture cache preserves the benefit of caching. If you do
not migrate the pictures, they will be re-created and cached when first requested,
which degrades performance.

To migrate picture cache, copy all the files from your existing pictures directory to
the new one. The default directory for picture cache is
/usr/lpp/booksrv/public/bookmgr/pictures. You can override this default by specifying
a directory on the PICDIR parameter of the /etc/booksrv/bookmgr.80 configuration
file.

BookRead
BookRead is an application programming interface (API) that extracts the text of a
book topic and places it in the calling program’s buffer. BookRead supports the man
command for z/OS UNIX System Services. Although provided with BookManager
BookServer, BookRead is not used by BookServer.

BookRead requires the use of the members installed in the SEPHTAB data set. If
the SEPHTAB data set is other than EPH.SEPHTAB, BookRead must be given the
appropriate high-level qualifier or fully-qualified data set name. Originally, the
EPHWP00 member of SYS1.PARMLIB was used to specify the high-level qualifier
or fully-qualified data set name. A sample of EPHWP00 is provided in SEPHSAMP.
Although EPHWP00 continues to be supported in z/OS, IBM recommends use of an
alternate method to provide BookRead with the name for the SEPHTAB data set.
You should use an HFS configuration file, bookread.conf, to specify the name of the
SEPHTAB data set. The default directory containing bookread.conf is /etc/booksrv.
To override the default directory, use the environment variable EPHBookReadConfig
to specify another directory name. The bookread.conf format is identical to
EPHWP00. See the EPHWP00 sample in SEPHSAMP. Line one of bookread.conf
or SYS1.PARMLIB(EPHWP00) must contain either the high-level qualifier for
SEPHTAB or DSN=’fully qualified data set name’. BookRead searches for the name
of the SEPHTAB data set in the following order:
1. If the environment variable EPHBookReadConfig exists, and the bookread.conf
file in the directory specified in the variable exists, the high-level qualifier or the
fully-qualified data set name is used.
2. If EPHBookReadConfig doesn’t exist or bookread.conf doesn’t exist in the
directory specified in EPHBookReadConfig, BookRead checks for file
/etc/booksrv/bookread.conf. The high-level qualifier or fully-qualified data set
name in /etc/booksrv/bookread.conf is used.
3. If bookread.conf is not found as explained above, BookRead checks for
SYS1.PARMLIB(EPHWP00). If found, the high-level qualifier or fully-qualified
data set name in EPHWP00 is used.
4. If none of the above methods provides a high-level qualifier or fully-qualified
data set name for the SEPHTAB data set, EPH.SEPHTAB is used.

Chapter 6. Preparing for Migration 141

 Note: BookRead must have access to the members of the SEPHTAB data set.

Migration Actions for C/C++

If you develop C/C++ applications on systems running a later level of z/OS than the
production centers that run these applications, you might encounter “downward
compatibility” problems even though these applications are not using new functions
of the later-level C/C++ Compiler or Class Libraries.

Migration Action for the C/C++ Compiler

The C/C++ Compiler provides an option, TARGET, that instructs the compiler to
generate object code that will run on earlier releases. The TARGET option provides
the solution for the downward compatibility problem for the compiler. For a detailed
description of the TARGET option, see z/OS C/C++ User’s Guide.

Migration Action for C++ Class Libraries

Link-editing applications on a later level of Class Libraries and then executing these
applications on an earlier level of Class Libraries might produce errors, and
therefore is not supported. In order to allow you to continue with this type of
application development environment and also to allow you to roll in new releases
of z/OS, IBM has documented a tactical solution in informational APAR II11576.

IBM’s tactical solution for this downward compatibility problem is to have customers
with this type of application development environment save the older levels of the
C/C++ Compiler (if not using the TARGET option) and Class Libraries, and to use
them for development. Specifically, you should maintain, on your application
development machine, your earliest level of the C/C++ Compiler (if not using the
TARGET option) and Class Libraries currently active in your production centers, and
point to these data sets during the compilation and link-edit phases of application
development. This method does not allow you to exploit new functions provided on
the later-level z/OS system, but it does allow you to build an application on one
level of the system and run the application on an earlier level. For a detailed
description of the APAR, see:
http://www.ibm.com/software/ad/c390/service/ii11576.html

Migration Actions for Dynamic Enablement Member IFAPRDxx

| When z/OS runs on an S/390 server (G5, G6, or Multiprise 3000), or when z/OS
| runs on a z900 server prior to production use of ILM, migration actions for dynamic
| enablement member IFAPRDxx can include the following. (Note: ILM will be initially
| delivered 30 March 2001 as part of z/OS. IBM testing of ILM is planned to be
| complete by the end of September 2001, at which time customer production use of
| ILM will be available.)
| v Add the IFAPRD00 member to one of your PARMLIB data sets to be used to IPL
| z/OS V1R1. IFAPRD00 is shipped with z/OS, unless you’re installing the z/OS
| V1R1 Upgrade Package for OS/390 V2R10, in which case you use your R10
| version of IFAPRD00 and change the ID and NAME values as specified below.
v Ensure that the IEASYSxx to be used to IPL z/OS points to the IFAPRD00
member that was shipped with z/OS (that is, IEASYSxx specifies PROD=00).
IEASYSxx can also point to additional IFAPRDxx members, if appropriate.
| v Change any existing IFAPRDxx members, which you created based on special
| needs, to reflect z/OS values:
| – Change the ID value from 5647-A01 (for OS/390 V2) to 5694-A01 (for z/OS
| V1).
| – Change the NAME value from OS/390 to 'z/OS'.

142 z/OS V1R1.0 Planning for Installation

 v Change any COMMNDxx or automated SET commands to reflect new IFAPRDxx
members.
v Remove the PSF entry from any IFAPRDxx members once they are no longer
processed by an OS/390 R6 system. PSF/MVS V2 (5695-040), which uses
dynamic enablement, is supported on OS/390 R6 but not on later systems
(OS/390 R7 and later, including z/OS). The follow-on product, PSF for OS/390
V3 (5655-B17), is supported on later systems (OS/390 R7 and later, including
z/OS) but does not use dynamic enablement.
v If you ordered z/OS V1R1 Infoprint Server, and you had OS/390 Print Server
enabled prior to R8, update your IFAPRDxx member to add an entry with
FEATURENAME('INFOPRINT SERVER') and remove entries with FEATURENAME('IP
PRINTWAY'), FEATURENAME('NETSPOOL'), and FEATURENAME('PRINT INTERFACE').

For a complete discussion of dynamic enablement, see “Using Dynamic

Enablement on an S/390 Server” on page 151.

| Migration Actions for ILM

| The base element IBM License Manager (ILM) is the tool in z/OS that enforces
| Workload License Charges on a z900 server. ILM will be initially delivered on 30
| March 2001 (as part of z/OS V1R1) for preproduction use, with Workload License
| Charges at full machine capacity. Customer production use of ILM, with Workload
| License Charges at less than full machine capacity, will be available when IBM
| completes full testing of ILM and you have applied the recommended z/OS service
| to make your system ILM production-ready. This testing by IBM is planned to be
| complete by the end of September 2001. The migration actions in this section apply
| to production use of ILM. For information about the preproduction use of ILM, see
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/.

| With OS/390, priced features are enabled or disabled via the IFAPRDxx parmlib
| member. With z/OS on an S/390 server, the method is the same. But with z/OS on
| a z900 server with production use of ILM, parmlib is no longer the vehicle for
| determining which z/OS priced features have been ordered and should run, and for
| changing this policy. Instead, you receive license certificates (in files) that indicate
| which priced features you have ordered. Using ILM, you can update the certificates
| to enable or disable features. The license change takes effect immediately on your
| system and is communicated to IBM when you send in a reconciliation message.
| This message contains records of all certificate changes and exception events
| recorded since the last reconciliation message (typically one month). This
| communication satisfies the requirement for notifying IBM when features are
| enabled that were shipped from IBM as disabled. For greater detail about how to
| enable or disable products using ILM, and how the monthly reconciliation process
| works, see z/OS IBM License Manager Administration.

| ILM components that you need to configure are:

| v License server. This is a program that controls the license management
| resources, including license certificates and license instances. It receives and
| processes requests from the application agents for license verifications and
| grants. It processes requests from the management agent to manage the
| licensing system.
| v Application agent. This is the interface for applications. It receives requests for
| licenses and works with the license server as needed.
| v Management tool. This is an interface that manages the license server’s
| resources. The tool provides you with the ability to view and administer resources
| within the license system and to update license certificates. The management

Chapter 6. Preparing for Migration 143

| tool and management agent run together, either on z/OS or on a workstation.
| When run on z/OS, the management tool has a command line interface. When
| run on a workstation, the management tool has a graphical interface, which runs
| on the management console.
| v Management agent. This is the interface used by the management tool to
| communicate with the license server.

| Things to consider as you prepare to set up ILM are:

| v You may configure only one production-level license server for a processor. The
| image that has the license server requires:
| – An application agent.
| – The management tool configured.
| – Certificate repositories.
| – The system logger to log certificate changes and licensing exceptions. The
| system logger requires a sysplex configuration (monoplex is sufficient),
| DASD-only log streams (not coupling facility), and an SMS environment to
| manage the DASD log streams.
| – An activated OCSF Base component of the Cryptographic Services base
| element.
| – z/OS UNIX System Services operating in full function mode (which implies
| that an HFS is set up).
| v Each LPAR running a z/OS image on the new hardware must have an
| application agent defined. Each application agent must have Communications
| Server IP connectivity to the license server. Conversely, the license server must
| have IP connectivity to all agents on a processor and to the management agent.
| v You must configure the management agent. FTP connectivity between the
| workstation running the management agent and the license server, which runs on
| z/OS, is recommended but not required. The reconciliation message FTP to IBM
| can occur from any computer that has access to the reconciliation message. This
| computer can be a workstation.
| v You are sent two types of certificates, which are required for full functionality of
| ILM on z/OS images running on z900 servers. The two types are a publisher
| global license certificate (PGLC) and a publisher product license certificate
| (PPLC). An IPL option allows you to run software for a limited amount of time
| while you complete the configuration of ILM and install certificates on the z/OS
| image on the z900 server. Both IBM’s PGLC and the z/OS PPLC must be
| installed and customized to enable z/OS and its features to have licenses
| granted in normal mode.

| You can set up the license server and application agents prior to IPLing z/OS, that
| is, while still using OS/390. Although you cannot exploit the services of ILM, getting
| a head start on setup will enable a more rapid deployment of the ILM license server
| once you migrate to z/OS and the z900 server, helping you more quickly take
| advantage of Workload License Charges. For information about ILM software
| requirements, see “Appendix B. Software Requirements for z/OS Elements and
| Features” on page 201. For information about ILM hardware requirements, see
| “Appendix D. Hardware Requirements for z/OS Elements and Features” on
| page 229.

Migration Actions for Infoprint Server

Prior to OS/390 R8, the IP PrintWay and NetSpool components of the OS/390 Print
Server feature were identical to the IP PrintWay and NetSpool features of the PSF
V3 for OS/390 (5655-B17) and PSF/MVS V2 (5695-040) products. You could install

144 z/OS V1R1.0 Planning for Installation

 and use either the OS/390 Print Server feature or the PSF V3 product’s features,
and obtain equivalent function. Starting with OS/390 R8 (and continuing into z/OS),
this is no longer the case. The IP PrintWay and NetSpool components of the
OS/390 R8 and later Infoprint Server feature contain new function that is not
available in the PSF V3 product’s features.

If you are migrating from OS/390 R7 or earlier, migration actions are required
before you can use Infoprint Server on z/OS V1R1, even if you do not plan to
exploit new function. A summary of the migration steps is listed in the following
sections. Refer to z/OS Infoprint Server Migration for detailed information on
migrating to Infoprint Server.

Terminology note: Some of the names used in this section are similar and could
be confused. z/OS V1R1 Infoprint Server (or just Infoprint Server) is an optional
feature of z/OS. Prior to OS/390 R8, its name was OS/390 Print Server. It contains
the following components:
v IP PrintWay. This name is also used for one of the features of PSF.
v NetSpool. This name is also used for one of the features of PSF.
v Print Interface.
v Printer Inventory Manager.
v SNMP Subagent.
v Transform Manager.
| v Infoprint Server Windows Client.

Migrating to z/OS V1R1 Infoprint Server from OS/390 Releases

Prior to R8
As of OS/390 R8, Infoprint Server has a new, consolidated Printer Inventory
Manager component that is used by the other components of Infoprint Server to
define and manage printer definitions. The IP PrintWay routing and options files and
the NetSpool print characteristics data set are no longer used. A migration program
is provided to migrate existing IP PrintWay, NetSpool, and Print Interface printer
definitions to the Printer Inventory. The migration program reads existing
configuration data, identifies relationships, and generates configuration definitions in
the format required by Infoprint Server.

The migration program accepts as input:

v IP PrintWay routing and options data sets
v NetSpool print characteristics data sets (PCDS)
v NetSpool end-of-file rules data sets
v NetSpool page format data sets
v NetSpool startup procedures that contain OUTPUT statements
v Print Interface printer definitions stored in the /var/Printsrv/printers HFS directory

The migration program runs as a two-step process:

1. Process the input using the migration program. The output from this program is
a set of printer definitions and a report.
2. Process the printer definitions that were created by the migration program to
load the Printer Inventory.

The Printer Inventory enables all of Infoprint Server’s components to store their
configuration data in the same repository. It also allows you to define one printer
definition that can be used by all of the components. Much of the processing
performed by the migration program focuses on combining NetSpool, Print

Chapter 6. Preparing for Migration 145

 Interface, and IP PrintWay definitions that refer to the same printer. The migration
program can combine definitions only if you specify all inputs that you are using,
and migrate everything at once.

Once you have run the migration program and loaded the Printer Inventory, you can
use the Infoprint Server ISPF panels to view and manipulate the printer definitions
that were created.

Migration to the Printer Inventory is required to use any of the functions of Infoprint
Server. Other migration tasks might need to be performed as well, as described in
z/OS Infoprint Server Migration. Existing NetSpool and IP PrintWay exits can be
used with Infoprint Server. You must recompile, and possibly modify, IP PrintWay
exit routines for use with Infoprint Server. You must place NetSpool exit routines in
an APF-authorized library, but recompilation is not required.

Migrating to z/OS V1R1 Infoprint Server from PSF V3 IP PrintWay

and NetSpool
If you are migrating from the stand-alone PSF product’s IP PrintWay and NetSpool
features to Infoprint Server, the same migration considerations apply as are listed in
“Migrating to z/OS V1R1 Infoprint Server from OS/390 Releases Prior to R8” on
page 145. When you run the migration program, you specify as input only the files
for the components that you are using. For example, if you are migrating from the
stand-alone PSF product’s NetSpool, you would use only the NetSpool data sets as
input to the migration program.

The IP PrintWay and NetSpool components of Infoprint Server cannot use the IP
PrintWay routing and options files and the NetSpool print characteristics data set
that were used for PSF V3 features. You must migrate your printer definitions to the
Printer Inventory. If you want to continue to use the PSF V3 IP PrintWay or
NetSpool features on z/OS V1R1, you should review the considerations listed in
“Using PSF V3 IP PrintWay and NetSpool on z/OS”.

Using PSF V3 IP PrintWay and NetSpool on z/OS

You can install the PSF V3 IP PrintWay and NetSpool features on z/OS V1R1, but
you must take steps to ensure that these features can be installed and can run with
z/OS. The installation of Infoprint Server will delete and supersede the FMIDs for
the PSF V3 IP PrintWay and NetSpool features. In order to use the PSF V3 IP
PrintWay and NetSpool features on z/OS V1R1, the following considerations apply:
v You cannot install PSF V3 IP PrintWay and NetSpool into the same SMP/E target
and distribution zone as z/OS. You must install them into a separate zone. IP
PrintWay and NetSpool can be installed together in the same zone, but the zone
must be different from the one you use to install z/OS.
v The executable code for the PSF V3 IP PrintWay and NetSpool features can run
on the same system as the executable code for Infoprint Server. PSF V3 IP
PrintWay modules will be installed into ANF.SANFLOAD and PSF V3 NetSpool
modules will be installed into API.SAPIMOD1. Infoprint Server modules will be
installed into SYS1.LINKLIB.
v If you want to run PSF V3 IP PrintWay or NetSpool on z/OS V1R1, you must use
a STEPLIB statement in the startup procedure for PSF V3 IP PrintWay and
NetSpool. You should not put ANF.SANFLOAD or API.SAPIMOD1 in the link list
because modules with the same names reside in SYS1.LINKLIB, and the
modules in ANF.SANFLOAD and API.SAPIMOD1 would not be found.
v SYS1.PROCLIB will contain startup procedures for Infoprint Server after the
installation of z/OS V1R1. These procedures have the same names as the
procedures provided with PSF V3 IP PrintWay and NetSpool. You should use

146 z/OS V1R1.0 Planning for Installation

 different names for the startup procedures for IP PrintWay and NetSpool if you
are using the PSF V3 features, rather than the default procedures ANFWPROC
and APIJPJCL.
v The JES work selection criteria you use for PSF V3 IP PrintWay must be
different from that used for Infoprint Server if you want to run both of them in
parallel. This will ensure that print jobs will be routed to the appropriate program
for processing.
v You must use separate operational data sets for IP PrintWay and NetSpool if you
want to run them in parallel with Infoprint Server. Separate data sets are required
for the PSF V3 features for the IP PrintWay transmission queue file, IP PrintWay
message log data set, and NetSpool message log data set.
v You must dynamically enable the PSF V3 IP PrintWay and NetSpool features as
described in “IP PrintWay Feature of PSF V3” on page 158 and “NetSpool
Feature of PSF V3” on page 158.
v You must use separate logon procedures to access the ISPF panels for IP
PrintWay administration. Different data sets are required for the ISPPLIB,
ISPMLIB, and SYSEXEC concatenations for the PSF V3 level of IP PrintWay
than for Infoprint Server. Also, the logon procedure for the PSF V3 IP PrintWay
requires a STEPLIB to ANF.SANFLOAD.

Migration Actions for JES2

JES2 pre-Release 4 mode (not “$ACTIVATEd”) is supported by the JES2 element
available with OS/390 R4 through R9. However, starting with OS/390 R10, JES2
does not support running in pre-Release 4 mode. To avoid a cold start, customers
wishing to migrate directly to OS/390 R10 or later JES2 must migrate to JES2
Release 4 mode (available in OS/390 R4 JES2 through OS/390 R9 JES2) prior to
installing OS/390 R10 or later JES2. For further migration information about JES2
pre-Release 4 mode, see z/OS JES2 Migration.

Migration Actions for Language Environment

This section presents several important Language Environment migration
considerations. Refer to z/OS Language Environment Run-Time Migration Guide for
more comprehensive Language Environment coverage.

Making the Language Environment Run-Time Library Available to

z/OS
Many elements and features, such as Communications Server and z/OS UNIX
System Services, require the run-time library that Language Environment provides.
This means that you must make the Language Environment data sets SCEERUN
and SCEERUN2 available as part of the libraries that are searched by z/OS. The
best way to do this is by adding these data sets to the link list. However, adding
these data sets to the link list could adversely affect other applications that have
dependencies on pre-Language Environment run-time libraries.

If you cannot add the SCEERUN and SCEERUN2 data sets to the link list, add
them (through STEPLIB) to cataloged procedures for those z/OS elements and
features that require Language Environment. Alternatively, use run-time library
services (RTLS) to access the run-time library. All of these environments are tested
and supported by IBM.

See z/OS V1R1.0 Program Directory for the list of z/OS elements and features that
require Language Environment and how they can access SCEERUN and
SCEERUN2 when they are not in the link list.

Chapter 6. Preparing for Migration 147

 All z/OS elements and features that require Language Environment must use the
current (latest) level of the Language Environment run-time libraries. Use of earlier
levels of the SCEERUN data set is not supported for these programs. Additionally,
because Language Environment is a base element of z/OS, running a later level of
Language Environment on an earlier release of z/OS is unsupported and violates
z/OS service policy.

Using Run-Time Library Services (RTLS)

A function called run-time library services (RTLS) allows you to access different
levels of the Language Environment run-time libraries, controlled by run-time
options. These run-time options allow you to control an application or your entire
application environment. See z/OS Language Environment Customization for
details.

Developing Applications with Language Environment in z/OS

OS/390 R10 and later (including z/OS) Language Environment provides downward
compatibility support. Assuming that required programming guidelines and
restrictions (documented in z/OS Language Environment Programming Guide) are
observed, this support enables programmers to develop applications on later
releases and run the applications on earlier releases. For example, a company
could use z/OS V1R1 (and Language Environment) on a development system
where applications are coded, link-edited, and tested, while using any supported
earlier release of OS/390 (and Language Environment) on their production systems
where the finished application modules are run.

Downward compatibility support is not the rollback of new function to prior releases
of OS/390. Applications that make use of the downward compatibility support must
not use Language Environment function that is unavailable on the earlier release of
OS/390 where the application will run. The downward compatibility support includes
coexistence (toleration) PTFs for earlier releases of OS/390 to assist in diagnosis of
applications that violate the programming requirements for this support. See
“Chapter 5. Ensuring Coexistence” on page 71 for PTF numbers.

The downward compatibility support provided by z/OS and by the coexistence PTFs
does not change Language Environment’s upward compatibility. That is,
applications coded and link-edited on one release of z/OS Language Environment
will continue to run on later releases of z/OS Language Environment without the
need to be recompiled and relink-edited.

Migration Actions for ServerPac and SystemPac

v ServerPac and SystemPac use the PROGxx parmlib member to specify LNKLST
concatenation. Using PROGxx allows exploitation of the z/OS dynamic link list
function. You should define the link list using either LNKLSTxx or PROGxx, but
not both. The system will ignore LNKLSTxx members of parmlib during IPL if you
specify a PROGxx that contains a LNKLST ACTIVATE statement, and will
replace the link list defined in LNKLSTxx with the one defined in PROGxx if it
processes a LNKLST ACTIVATE statement after IPL. For more information, see
z/OS MVS Initialization and Tuning Reference.
If you do not currently use PROGxx to define your LNKLST concatenation and
you intend to use your existing LNKLSTxx parmlib members with the
ServerPac-provided or SystemPac-provided parmlib, you can use the conversion
aid CSVLNKPR to migrate your existing LNKLSTxx parmlib member to a
PROGxx parmlib member. Refer to z/OS MVS Migration for details about
CSVLNKPR.

148 z/OS V1R1.0 Planning for Installation

 v Beginning with OS/390 R7, the shipped JES2/SDSF and JES3 zones are
consistently named. In some previous releases, IBM shipped the JES2/SDSF
elements in the MVST111 and MVSD111 zones, and the JES3 feature in the
MVST110 and MVSD110 zones. In OS/390 R7 and later, however, this
relationship is reversed: JES2 is shipped in the MVST110 and MVSD110 zones,
and JES3 is shipped in the MVST111 and MVSD111 zones.
If you use a zone-related naming convention for SMP/E data sets, you will need
to rename the data sets after the merge configuration to maintain this convention.
Rename the data sets in each of the four SMP/E zones. For example, in the
previous releases, if your SMPLTS data set in the MVST110 zone was
JES3.SMPLTS, merging that same data set with OS/390 R7 or later leaves the
data set name unchanged as JES3.SMPLTS. You must rename this data set to
JES2.SMPLTS to maintain your naming convention.

Virtual Storage Migration Considerations

You need to consider the impact on your virtual storage settings caused by the
release to which you’re migrating. Your virtual storage requirements will increase
when you include any of the load libraries that contain RMODE 24 LPA-eligible
modules in the LPA list. (These modules are listed in Table 31 on page 253.)

Load modules for some elements are installed in SYS1.LPALIB, while load modules
for other elements that are eligible for placement in LPA (including ELPA) are
installed in other, element-specific libraries. The amount of common area virtual
storage required to run z/OS will depend in large part on how many of the modules
in element-specific libraries you choose to place in LPA. This, in turn, will affect how
much PLPA or common page data set space will be required, and can also affect
how much private area will be available above and below 16 megabytes.

Load modules in element-specific libraries that are eligible for placement in LPA will
increase the common area storage required only if you include them in LPA. If you
place these libraries in the LPA list or in dynamic LPA, less virtual storage might be
available for the private areas above and below 16 megabytes. For this reason, you
should usually place modules from element-specific libraries in LPA only if you use
the elements.

If you later decide to enable a disabled feature, and the feature requires you to
place its modules in LPA or you decide to place them in LPA for best performance,
you can either add them to dynamic LPA and issue a SET command or add them to
the LPA list and IPL to activate them. (Similarly, you can add libraries to the link list
dynamically or with an IPL.) For more information about dynamic LPA, see the topic
about PROGxx in z/OS MVS Initialization and Tuning Reference.

The impact on virtual storage as you migrate to z/OS varies and needs to be
understood based upon what exists on the system now and what will be the net
product increase with z/OS. In addition, you must understand what new products,
elements, and features will be activated in the new z/OS system.

For more information about what you should consider when deciding how to
activate a z/OS feature (or another product), and about how those decisions affect
applications, system performance, and the use of virtual and real storage, see the
topic about placing modules in the system’s search order for programs in z/OS
MVS Initialization and Tuning Guide.

Chapter 6. Preparing for Migration 149

150 z/OS V1R1.0 Planning for Installation
 Chapter 7. Preparing for Customization and Test
You complete your installation by customizing and testing the new system. To help
you prepare, this chapter discusses some of the relevant activities: using dynamic
enablement on an S/390 server, scheduling test activities, and establishing a
fallback plan and procedures.

This chapter also discusses a post-test activity: rolling z/OS across a multisystem
configuration.

Using Dynamic Enablement on an S/390 Server

As explained in Chapter 1. Learning about z/OS, the priced features support
dynamic enablement. This means that the priced features that you order are
shipped enabled and are ready to use after you install and customize them. The
priced features that you don’t order are shipped disabled; even though you install
them, you can’t use them. Later on, if you decide to use them, you enable them
dynamically.

While priced features are the main focus of dynamic enablement, several related
items can also be dynamically enabled should you decide to use them with z/OS:
v The stand-alone product versions of z/OS nonexclusive features.
v The IP PrintWay and NetSpool features of stand-alone product PSF V3 for
OS/390 (5655-B17).
v The stand-alone product Document Composition Facility (DCF) (5748-XX9).
v The stand-alone product Infoprint Server Transforms for OS/390 (5697-F51).
v IP Services, one of the components of base element Communications Server,
which is shipped enabled when you order the standard z/OS base but disabled
when you order the alternate base configuration. Note that “TCP/IP” is the name
used for dynamic enablement of this component.

| The way in which you dynamically enable in z/OS depends on the server you’re
| using and whether you’re using ILM in production mode or preproduction mode.
| (ILM will be initially delivered on 30 March 2001 as part of z/OS V1R1 for ILM
| preproduction use. IBM testing of ILM is planned to be complete by the end of
| September 2001, at which time customer production use of ILM will be available.)
| v If you’re running z/OS on a z900 server and using ILM in ILM production mode,
| you dynamically enable by updating license certificates. The license change
| takes effect immediately on your system and is communicated to IBM on a
| monthly basis when you send in a reconciliation message. For details, do not use
| this chapter. Instead, see z/OS IBM License Manager Administration.
| v If you’re running z/OS on a z900 server, using ILM in ILM preproduction mode,
| and:
| – If ILM is active, you dynamically enable by updating license certificates and
| you notify IBM by contacting your IBM representative. For details, do not use
| this chapter. Instead, see http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
| – If ILM is not active, you dynamically enable by updating parmlib and you notify
| IBM by contacting your IBM representative. For details, continue reading this
| chapter.
| v If you’re running z/OS on an S/390 server, you dynamically enable by updating
| parmlib and you notify IBM by contacting your IBM representative. For details,
| continue reading this chapter.

© Copyright IBM Corp. 1996, 2001 151

 In brief, the steps required to dynamically enable if you’re using an S/390 server
are:
1. Notify IBM that you are starting to use the feature, stand-alone product, or
TCP/IP on a specific processor (as identified by a specific processor serial
number).
2. Update parmlib. IBM supplies a SYS1.PARMLIB member, IFAPRD00, that is
tailored to your order. IFAPRD00 contains entries that enable the priced
features, stand-alone products, or TCP/IP that you ordered for a specific
processor. To make the parmlib update, copy the contents of IFAPRD00 to an
IFAPRDxx member that will be active on the processor for which your OS/390
order was placed, and modify IFAPRDxx appropriately.
3. Establish the active parmlib member through the PROD parameter in IEASYSxx
or the SET PROD operator command.

The rest of this section helps you decide whether you need to use dynamic
enablement, describes in detail the three steps to do it, and explains how to disable
should you want to. Topics are:
v “Deciding Whether to Dynamically Enable”
v “Dynamic Enablement Step 1: Notify IBM” on page 154
v “Dynamic Enablement Step 2: Update Parmlib” on page 154
v “Dynamic Enablement Step 3: Establish the Active Parmlib Member” on page 159
v “Disabling What Was Enabled” on page 159.

A related section is “Migration Actions for Dynamic Enablement Member IFAPRDxx”

on page 142. Read it if you’re migrating from OS/390 to z/OS or from one z/OS
release to another.

Deciding Whether to Dynamically Enable

By describing the situations that require dynamic enablement, this section helps you
decide whether you need to dynamically enable.

A priced feature was not in your original order for a specific processor (as
identified by a specific processor serial number) but you now want to use it
on that processor. If this is the case, then follow the steps starting with “Dynamic
Enablement Step 1: Notify IBM” on page 154. The priced features are:
v BDT File-to-File
v BDT SNA NJE
v BookManager BUILD
v C/C++ without Debug Tool
v C/C++ with Debug Tool
v DFSMSdss
v DFSMShsm
v DFSMSrmm
v DFSORT
v GDDM-PGF
v GDDM-REXX
v HCM
v HLASM Toolkit
v Infoprint Server
v JES3
v RMF
v SDSF
v SecureWay Security Server
v SOMobjects ADE

152 z/OS V1R1.0 Planning for Installation

You are licensed for a stand-alone product that is also a nonexclusive priced
feature and the license is on a processor other than the one to which your
z/OS order applies. To allow your installation flexibility as you migrate to z/OS, you
can run the stand-alone product versions of the z/OS nonexclusive priced features
(or, in one case, a component of a nonexclusive priced feature). Running the
stand-alone product version of such an z/OS feature means you do not have to
order and install the z/OS feature. The stand-alone products that are also z/OS
nonexclusive priced features are:
v BookManager BUILD/MVS. The corresponding z/OS feature is BookManager
BUILD.
v Debug Tool component of several language products. In z/OS, the Debug Tool is
a component of the C/C++ with Debug Tool feature.
v DFSORT. The corresponding z/OS feature is DFSORT.
v GDDM-PGF. The corresponding z/OS feature is GDDM-PGF.
v HLASM Toolkit feature of HLASM. The corresponding z/OS feature is HLASM
Toolkit.

If your order included stand-alone product versions of these features, the

stand-alone versions are enabled in the IBM-supplied IFAPRD00 member. If you
are licensed for such stand-alone products on a processor other than the one to
which your z/OS order applies, you must specifically enable them because the
IBM-supplied IFAPRD00 does not. Follow the steps starting with “Dynamic
Enablement Step 1: Notify IBM” on page 154.

You are licensed for PSF V3 on a processor other than the one to which your
z/OS order applies and you want to use the PSF V3 IP PrintWay and NetSpool
features with z/OS. The stand-alone product PSF V3 for OS/390 (5655-B17)
contains the IP PrintWay and NetSpool features. The z/OS Infoprint Server feature
contains the IP PrintWay and NetSpool components. Although IP PrintWay and
NetSpool in z/OS are functionally superior to IP PrintWay and NetSpool in PSF V3,
you could use PSF V3’s IP PrintWay and NetSpool instead of z/OS Infoprint
Server’s IP PrintWay and NetSpool.

If your order included the PSF V3 features IP PrintWay and NetSpool, these
features are enabled in the IBM-supplied IFAPRD00 member. If you are licensed for
PSF V3 on a processor other than the one to which your z/OS order applies, you
must specifically enable the PSF V3 IP PrintWay and NetSpool features because
the IBM-suppled IFAPRD00 does not. Follow the steps starting with “Dynamic
Enablement Step 1: Notify IBM” on page 154. In either case, also refer to “Using
PSF V3 IP PrintWay and NetSpool on z/OS” on page 146.

You are licensed for DCF on a processor other than the one to which your
z/OS order applies, or not licensed at all. The stand-alone product DCF
(5748-XX9) can be dynamically enabled. To use DCF, you must do one of the
following:
v If you are already licensed for DCF on a specific processor, you must explicitly
enable it in the IFAPRDxx member that is active on that processor in order to
continue to use it with z/OS. Follow the steps starting with “Dynamic Enablement
Step 1: Notify IBM” on page 154.
v If you are not licensed for DCF on a specific processor and would like to use it,
you must purchase a license for that processor, receive and install DCF, and then
follow the steps starting with “Dynamic Enablement Step 1: Notify IBM” on
page 154 to enable it in the IFAPRDxx member that is active on that processor.

Chapter 7. Preparing for Customization and Test 153

 (It is a violation of your license agreement with IBM to enable DCF on a
processor if you are not licensed for it on that processor.)

You are licensed for Infoprint Server Transforms on a processor other than
the one to which your z/OS order applies, or not licensed at all. The
stand-alone product Infoprint Server Transforms for OS/390 (5697-F51) is closely
related to z/OS; it enhances the function available in the Infoprint Server feature of
z/OS. Infoprint Server Transforms can be dynamically enabled. To use Infoprint
Server Transforms, you must do one of the following:
v If you are already licensed for Infoprint Server Transforms on a specific
processor, you must explicitly enable it in the IFAPRDxx member that is active on
that processor in order to continue to use it with z/OS. Follow the steps starting
with “Dynamic Enablement Step 1: Notify IBM”.
v If you are not licensed for Infoprint Server Transforms on a specific processor
and would like to use it, you must obtain a license for that processor, receive and
install Infoprint Server Transforms, and then follow the steps starting with
“Dynamic Enablement Step 1: Notify IBM” to enable it in the IFAPRDxx member
that is active on that processor. (It is a violation of your license agreement with
IBM to enable Infoprint Server Transforms on a processor if you are not licensed
for it on that processor.)

You are licensed for the alternate base but now want to use the standard
base. IP Services, the component of element Communications Server that supports
TCP/IP networking, supports dynamic enablement because of the z/OS alternate
base configuration. (Refer to “z/OS Alternate Base” on page 60.) IP Services is
shipped enabled if you order the standard z/OS base but disabled if you order the
alternate base. Thus, if you’re licensed for the alternate base but now want to be
licensed to use the standard base, you must enable IP Services (using the name
TCP/IP). Follow the steps starting with “Dynamic Enablement Step 1: Notify IBM”.

Dynamic Enablement Step 1: Notify IBM

Ask your asset manager to contact your IBM representative to alert IBM that you
are starting to use the feature or stand-alone product or TCP/IP on a specific
processor (as identified by a specific processor serial number). Because the z/OS
license is processor-based, you need to contact IBM only once when multiple z/OS
systems execute in LPAR mode on that processor.

Use of (and enablement of) the feature, stand-alone product, or TCP/IP is subject to
the z/OS license terms and conditions and must be done with the knowledge of
your asset manager according to the terms and conditions for z/OS. See the Usage
Restriction section of z/OS Licensed Program Specifications for additional license
terms and conditions.

Dynamic Enablement Step 2: Update Parmlib

The IBM-supplied SYS1.PARMLIB member that defines the product enablement
policy for a system is IFAPRD00. IFAPRD00 contains a PRODUCT statement for
each item (feature, stand-alone product, or TCP/IP) that can be dynamically
enabled, set to an enablement state determined by your order. Copy IFAPRD00 to
an IFAPRDxx of your choosing and edit IFAPRDxx, if necessary, so that it contains
the correct form of PRODUCT statements to enable each feature, product, or
TCP/IP that should be enabled, as described in the sections starting with “z/OS
Priced Features and TCP/IP” on page 155.

154 z/OS V1R1.0 Planning for Installation

 If you use the order that IBM ships to you to clone systems for use on other
processors, you must ensure that the IFAPRDxx member used on each processor
enables only the z/OS priced features and stand-alone products that are licensed to
that processor. A single shared copy of IFAPRDxx might or might not be suitable for
use by all of them. Note that appropriate use of IFAPRDxx WHEN statements can
allow a single shared IFAPRDxx member to be used by several processors, all of
which have different combinations of priced features and stand-alone products
licensed to them. See z/OS MVS Initialization and Tuning Reference for further
details.

Note the following:

v DFSMSdss, DFSMSrmm, and DFSMShsm do not use the IGDDFPKG parmlib
member for enablement.
v GDDM-REXX does not use the ERXTENAB JCL member of the GDDM
SADMSAM data set.

z/OS Priced Features and TCP/IP

For each priced feature that you want to enable, or to enable TCP/IP, ensure that
there is a PRODUCT statement (or, for TCP/IP, multiple PRODUCT statements)
having the following form:
| PRODUCT OWNER('IBM CORP')
| NAME('z/OS')
| FEATURENAME(name)
| ID(5694-A01)
| STATE(ENABLED)

| NAME specifies the operating system. Note that this value has changed to z/OS; it
| was OS/390.

The variable name on the FEATURENAME parameter identifies the feature, or

TCP/IP, that you want to enable. Refer to Table 17 for possible values.

| ID specifies the program number for z/OS. Note that this value has changed to
| 5694-A01; it was 5647-A01 in OS/390 V2.

The VERSION RELEASE MOD parameter should be omitted or specified with

asterisks, as follows:
VERSION(*) RELEASE(*) MOD(*)

Table 17. FEATURENAME values for z/OS priced features and TCP/IP
Name FEATURENAME value
BDT File-to-File BDTFTF
BDT SNA-NJE BDTNJE
BookManager BUILD BOOKMGR BUILD
(See Note 1.)
C/C++ without Debug Tool C/C++
(See Note 2.)
C/C++ with Debug Tool C/C++/DEBUG
(See Note 2.)
DFSMSdss DFSMSDSS
DFSMShsm DFSMSHSM
DFSMSrmm DFSMSRMM
DFSORT DFSORT

Chapter 7. Preparing for Customization and Test 155

 Table 17. FEATURENAME values for z/OS priced features and TCP/IP (continued)
Name FEATURENAME value
GDDM-PGF GDDM-PGF
GDDM-REXX GDDM-REXX
HCM HCM
HLASM Toolkit TOOLKIT DEBUGGER
(See Note 1.)
Infoprint Server INFOPRINT SERVER
(See Note 1.)
JES3 JES3
RMF RMF
SDSF SDSF
SecureWay Security Server SECURITY SERVER
(See Note 1.)
SOMobjects ADE SOM/MVS ADE
(See Note 1.)
TCP/IP (includes the components TCP/IP Base, TCP/IP TCP/IP BASE
CICS, and TCP/IP IMS) TCP/IP CICS
TCP/IP IMS
(See Notes 1, 3, and 4.)
Notes:
1. To specify a FEATURENAME value that contains a blank, either replace the blank with
an underscore (as in SOM/MVS_ADE) or enclose the name in single quotation marks
(as in ‘SOM/MVS ADE’).
2. To specify a FEATURENAME value that contains a +, enclose the name in single
quotation marks (as in ‘C/C++’).
3. You must specify multiple PRODUCT statements.
4. If your installation ordered the standard z/OS base, TCP/IP is shipped enabled.
Otherwise, it is shipped disabled.

Stand-Alone Product BookManager BUILD/MVS

To enable the BookManager BUILD/MVS stand-alone product to run with z/OS, the
following entry must be in the IFAPRDxx parmlib member:
PRODUCT OWNER ('IBM CORP')
NAME('BOOKMGR BUILD')
ID(5695-045)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME('BOOKMGR BUILD')
STATE(ENABLED)

A sample BookManager BUILD/MVS entry appears in the EOYIFAPR member of

the SEOYSAMP library.

Debug Tool Component of Several Stand-Alone Products

The Debug Tool is available as a component of the z/OS C/C++ with Debug Tool
feature and as a component of several stand-alone language products.

If you order the z/OS C/C++ with Debug Tool feature, there is no need to also order
the C/C++ without Debug Tool feature. The IBM-supplied IFAPRD00 member
enables the use of C/C++ and the Debug Tool.

156 z/OS V1R1.0 Planning for Installation

 If you order C/C++ with Debug Tool and then later decide to order C/C++ without
Debug Tool, explicitly enable the C/C++ feature name as follows (and disable the
C/C++/DEBUG feature name):
| PRODUCT OWNER ('IBM CORP')
| NAME('z/OS')
| ID(5694-A01)
| VERSION(*) RELEASE(*) MOD(*)
| FEATURENAME('C/C++')
| STATE(ENABLED)

If you order C/C++ without Debug Tool and then later decide to order C/C++ with
Debug Tool, explicitly enable the C/C++/DEBUG feature name as follows. (This
statement allows use of both C/C++ and the Debug Tool; you can then disable the
C/C++ without Debug Tool feature.)
| PRODUCT OWNER ('IBM CORP')
| NAME('z/OS')
| ID(5694-A01)
| VERSION(*) RELEASE(*) MOD(*)
| FEATURENAME('C/C++/DEBUG')
| STATE(ENABLED)

The stand-alone products that use the Debug Tool are:

v IBM COBOL for OS/390 & VM
v IBM COBOL for MVS & VM
v IBM CODE/370
v IBM VisualAge PL/I for OS/390 Version 2
v IBM PL/I
v IBM VisualAge for Java, Enterprise Edition for OS/390 Version 2
If you order any of these products with z/OS, the IBM-supplied IFAPRD00 member
that IBM ships with your order contains the required PRODUCT statements.
Otherwise, you must explicitly enable the product when you run it with z/OS. The
following list identifies the entry you are required to include in the IFAPRDxx parmlib
member.

Stand-alone product IFAPRDxx entry

IBM COBOL for OS/390 & VM (5648-A25) PRODUCT OWNER('IBM CORP')
NAME('IBM COBOL OS/390')
ID(5648-A25)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(COBOL-DEBUG)
STATE(ENABLED)
IBM COBOL for MVS & VM (5688-197) PRODUCT OWNER('IBM CORP')
NAME('IBM COBOL MVS/VM')
ID(5688-197)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(COBOL-DEBUG)
STATE(ENABLED)
IBM CODE/370 (5688-194) PRODUCT OWNER('IBM CORP')
NAME('IBM CODE/370')
ID(5688-194)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(CODE/370-DEBUG)
STATE(ENABLED)
IBM VisualAge PL/I for OS/390 V2 PRODUCT OWNER('IBM CORP')
(5655-B22) NAME('IBM VAPLI/390')
ID(5655-B22)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(VAPL/I-DEBUG)
STATE(ENABLED)

Chapter 7. Preparing for Customization and Test 157

 Stand-alone product IFAPRDxx entry
IBM PL/I (5688-235) PRODUCT OWNER('IBM CORP')
NAME('IBM PL/I MVS/VM')
ID(5688-235)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(PL/I-DEBUG)
STATE(ENABLED)
IBM VisualAge for Java, Enterprise Edition for PRODUCT OWNER('IBM CORP')
OS/390 V2 (5655-JAV) NAME('IBM VA JAVA/390')
ID(5655-JAV)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(VAJAVA/390-DEBUG)
STATE(ENABLED)

Stand-Alone Product DFSORT

To enable the DFSORT stand-alone product to run with z/OS, the following entry
must be in the IFAPRDxx parmlib member:
PRODUCT OWNER ('IBM CORP')
NAME(DFSORT)
ID(5740-SM1)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(DFSORT)
STATE(ENABLED)

Stand-Alone Product GDDM-PGF

To enable the GDDM-PGF stand-alone product to run with z/OS, the following entry
must be in the IFAPRDxx parmlib member:
PRODUCT OWNER('IBM CORP')
NAME(GDDM-PGF)
ID(5668-812)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(GDDM-PGF)
STATE(ENABLED)

Stand-Alone Product HLASM Toolkit

To enable the High Level Assembler (HLASM) Toolkit feature of the HLASM
stand-alone product to run with z/OS, the following entry must be in the IFAPRDxx
parmlib member:
PRODUCT OWNER ('IBM CORP')
NAME('HI LVL ASSEMBLER')
ID(5696-234)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME('TOOLKIT DEBUGGER')
STATE(ENABLED)

IP PrintWay Feature of PSF V3

To enable the IP PrintWay feature of stand-alone product PSF V3 to run with z/OS,
the following entry must be in the IFAPRDxx parmlib member:
PRODUCT OWNER('IBM CORP')
NAME('PSF FOR OS/390')
ID(5655-B17)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME('IP PRINTWAY')
STATE(ENABLED)

NetSpool Feature of PSF V3

To enable the NetSpool feature of stand-alone product PSF V3 to run with z/OS,
the following entry must be in the IFAPRDxx parmlib member:

158 z/OS V1R1.0 Planning for Installation

 PRODUCT OWNER('IBM CORP')
NAME('PSF FOR OS/390')
ID(5655-B17)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME('NETSPOOL')
STATE(ENABLED)

Stand-Alone Product DCF

To enable the Document Composition Facility (DCF) stand-alone product to run with
z/OS, the following entry must be in the IFAPRDxx parmlib member:
PRODUCT OWNER('IBM CORP')
NAME(DCF)
ID(5748-XX9)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME(DCF)
STATE(ENABLED)

Stand-Alone Product Infoprint Server Transforms

To enable the Infoprint Server Transforms stand-alone product to run with z/OS, the
following entry must be in the IFAPRDxx parmlib member:
PRODUCT OWNER('IBM CORP')
NAME('INFOPRINT XFORMS')
ID(5697-F51)
VERSION(*) RELEASE(*) MOD(*)
FEATURENAME('TRANSFORM TO AFP')
STATE(ENABLED)

Dynamic Enablement Step 3: Establish the Active Parmlib Member

To dynamically activate the updated enablement policy without an IPL, place the
updated PRODUCT statements in the appropriate IFAPRDxx member of the active
SYS1.PARMLIB data set. You can then issue the SET PROD operator command to
specify the IFAPRDxx member that defines the enablement policy. See z/OS MVS
System Commands for more information.

The enablement policy change takes place immediately but does not affect any
instances of features, stand-alone products, or TCP/IP that are already executing.
Also, activating a new enablement policy does not start any of the enabled features,
stand-alone products, or TCP/IP. They will only run when explicitly started by some
other action, such as a START command.

Be sure to change the PROD system parameter in IEASYSxx to point to the

appropriate IFAPRDxx member; no IFAPRDxx member is activated by default. This
change ensures that the next IPL activates the correct policy. For more information
about using IFAPRDxx, see z/OS MVS Initialization and Tuning Reference.

Disabling What Was Enabled

If, after you use an enabled feature, stand-alone product, or TCP/IP, you want to
discontinue its use, you must disable it — again using the IFAPRDxx member to
define the policy change and the SET PROD command to activate the changed
policy.

Because disabling the feature, stand-alone product, or TCP/IP in the enablement

policy does not stop it from running, you might have to explicitly stop it. For
example, you might have to:
v Issue a command provided by the feature, stand-alone product, or TCP/IP.
v Issue the MVS MODIFY or MVS STOP command, as appropriate.

Chapter 7. Preparing for Customization and Test 159

 Or, you might decide that the least disruptive way to stop a long-running feature,
stand-alone product, or TCP/IP is to IPL the system without it.

After you disable a feature, stand-alone product, or TCP/IP, ask your asset manager
to contact your IBM representative to alert IBM that you are discontinuing its use on
a specific processor. See the Usage Restriction section of z/OS Licensed Program
Specifications for additional license terms and conditions.

Scheduling Test Activities

IPL the new release in a production environment after you have tested the new
release with a simulated production workload that includes all applications and all
non-IBM products, and that ensures that service level agreements can be met.

IPL in a shared resource environment after you have installed any coexistence
PTFs.

| If you’re using a z900 server and your production workload will require greater than
| 2 GB of central storage, be sure to use greater than 2 GB on your test image. In
| fact, the more storage you use above the 2 GB line on your test image, the greater
| the chance that pages will be backed up there, and the greater the odds of
| exposing problems during test rather than during production.

Perform function and stress test. IBM’s testing does not replace the need for this
testing in your own environment. Testing might include:
v Initializing the system
v Initializing JES2 or JES3
v Logging on to TSO/E
v Running the IVPs
v Submitting a job
v Checking the job’s output
v Starting customization of z/OS
v If CICS or IMS is installed, initializing a region and signing on to a terminal
v Bringing your ISV products into the test environment
v Running critical production jobs
v Supporting a representative interactive workload
v Communicating with all networks
v Testing critical functions in applications
v Checking some of the paths not often taken
v Checking for completeness of accounting records
v Testing all non-IBM product functions
v Bringing your applications into the test environment
v Ensuring that performance goals stated in service level agreements can be met.

Don’t complicate your testing by exploiting the new function that z/OS provides.
Save that task until after you are successfully running in production.

Establishing a Fallback Plan and Procedures

You should have a fallback (backout) plan in case problems occur during testing
and you have to fall back to your previous level.

Fallback for z/OS is at a system level, rather than an element or feature level,
except for JES2 and JES3. That is, except for JES2 and JES3, you can’t back out
an element or feature; you can only back out the entire z/OS product. JES2 and

160 z/OS V1R1.0 Planning for Installation

 JES3 fallback can be done separately as long as the level of JES is supported with
the release of z/OS and any necessary coexistence service is installed.

Fallback will usually require you to install service on the system to which you’re
falling back so that it tolerates changes that were made by the later-level system.
Refer to “Chapter 5. Ensuring Coexistence” on page 71.

If your fallback plans include making a clone, refer to “Appendix F. Making a Copy
of Your System Software (Cloning)” on page 275.

Rolling z/OS across a Multisystem Configuration

A rolling IPL is the IPL of one system at a time in a multisystem configuration. You
might stage the IPLs over a few hours or a few weeks. The use of rolling IPLs
allows you to migrate each z/OS system to a later z/OS release, one at a time,
while allowing for continuous application availability. Data sharing applications, for
example, offer continuous availability in a Parallel Sysplex configuration by treating
each z/OS system as a resource for processing the workload. This allows z/OS
systems running these applications to be IPLed one at a time, to migrate to a new
release of z/OS, while the applications continue to be processed by the other z/OS
systems that support the workload. By using LPAR technology, you can use this
technique to upgrade your systems without losing either availability or capacity.

You can use rolling IPLs when both of the following are true:
| v The release to which you’re migrating falls within four consecutive releases of the
| releases running on the other systems (or within the range of releases supported
| by special provisions, where available). See “Coexistence Policy” on page 72 for
| the releases that are supported by the coexistence policy.
v The appropriate coexistence maintenance has been installed on the other
systems in the multisystem configuration.

Even when you’re using applications that do not support data sharing, rolling IPLs
often make it easier to schedule z/OS software upgrades. It can be very difficult to
schedule a time when all applications running on all the systems in a multisystem
configuration can be taken down to allow for a complex-wide or Parallel
Sysplex-wide IPL.

The use of rolling IPLs not only enables continuous availability from an end-user
application point of view, but it also eliminates the work associated with migrating all
z/OS systems in a multisystem configuration at the same time.

Chapter 7. Preparing for Customization and Test 161

162 z/OS V1R1.0 Planning for Installation
Chapter 8. Preparing for Future Installations
When you build a z/OS system, you must balance the needs of your installation to
build a system that meets its needs well. While this will sometimes mean
compromise, it more often means finding ways to build a flexible system that is
easy to install, easy to migrate, easy to extend, and easy to change. z/OS provides
tremendous flexibility in installation and customization. When applied using a
well-planned structure, this flexibility can minimize the time it takes to install and
migrate new systems or new software levels throughout an installation.

Adopting a well-planned structure for your installation provides the foundation for
controlling workload during future installations and migrations. Depending on how
your system is structured today, doing this can be very easy, requiring little
investment, or quite difficult, requiring many system programming hours. However,
the long-term benefits of a well-planned structure are quite clear.

This chapter helps you prepare for future installations. Many of the techniques
discussed in this chapter, if you are not using them today, could take considerable
time to implement. It can be difficult or even impossible to attempt to do all these
things during a single build and migration cycle, for any number of reasons.

A phased approach will often prove most feasible and can begin to control the
installation and migration workload in the least time. This provides you benefits,
starting with the next installation and migration cycle, while controlling the work
involved in implementation. As you implement each technique, more time to
implement the remainder should be available during future system builds and
migrations.

Note: Some of the SystemPac-related techniques discussed in this chapter are

applicable only to SystemPac dump-by-data-set format. SystemPac full
volume dump format employs a very different philosophy, requiring far fewer
actions on your part.

System and Installation Requirements

Creating an installation plan helps you make sure the software you install is able to
meet your installation’s requirements for software function. However, software
function alone will not meet all the needs of your business, and there are other
things you should consider when planning to build a system, such as:
v Achieving efficient virtual storage mapping
v Achieving best application performance
v Building a minimum number of system software configurations
v Reducing installation and migration time
v Reducing the opportunities for error during migration
v Making it easy to manage the system after it is in production
v Minimizing migration actions for the people who use the system.

How you choose to meet all of these requirements can have a significant effect on
how much work is required to perform the tasks associated with each stage. Keep
these requirements in mind while reading this chapter.

© Copyright IBM Corp. 1996, 2001 163

Separating Data from Software
When you separate your data from your system software, you eliminate many tasks
that would otherwise need to be performed each time you upgrade or replace your
system software. An effective way to separate data from software is to use different
DASD volumes for each.

You will minimize your installation and migration workload if you try to satisfy these
objectives:
v All system software volumes for the same product set at the same product and
service levels should be identical.
v All differentiation between systems should happen during or after IPL.
v Only system software (and SMP/E data pertaining to it) should reside on system
software volumes.

If you have not previously used a system replacement method to install software,
you will find that it makes the installation considerably easier. Most of the work
involves separating the following kinds of data from z/OS software:
v Customization data, including most system control files
v Non-IBM software
v IBM products that run on z/OS
v User exits
v User data.

Your goal is to make it easier to replace the volumes that contain z/OS software,
which are supplied by ServerPac or SystemPac (dump-by-data-set format). This
allows you to more easily keep the other software and data you will need to use
with z/OS across migrations.

What to do with the non-ServerPac or non-SystemPac code

1. Ask if the code is still required. If not, don’t carry it forward; if so, go to the
next step.
2. Determine the usefulness and effectiveness of this code:
v Does it need to be updated for the new function in z/OS? If it does, you
might need to upgrade a product or change the code.
3. If this code can be separated from the code delivered with ServerPac or
SystemPac, place it in another product set. The product set should be
placed on another volume so that future ServerPac or SystemPac
installations will not overlay it. This requires moving it into separate
libraries and SMP/E zones.
4. If the code cannot be separated from the code delivered with ServerPac or
SystemPac, then it must be reinstalled in the same zones and libraries
delivered with ServerPac or SystemPac. One way to do this is with the
SMP/E BUILDMCS command.
5. Enable the useful and effective code to work with z/OS. This might mean
using concatenation, reinstalling the code, or possibly reassembling it.

As you face the task of where to place the various types of code in your installation
and enabling the code to work with z/OS, keep in mind the following advice:
v Use SMP/E to install all modules you use with the operating system; place
comments in each module that identify its function.

164 z/OS V1R1.0 Planning for Installation

v Where possible, use IBM-supplied exit points to control the system rather than
changing the source or object code.
v Where possible, use the dynamic exits service. This service allows you to refresh
exits without losing availability. For information about the dynamic exits service,
see z/OS MVS Installation Exits.
v Where possible, place your exit code in libraries placed on different volumes from
IBM code. This allows compatible exits to stay in place when you start to use a
new level of the operating system, and reduces migration time.

The following list includes the different kinds of code found in an installation, and
describes actions that ensure that the code you want to use with z/OS survives the
installation process and is enabled to run with z/OS. The list includes the ways you
insert customer-written code into an operating system environment or change the
operating system code:
v IBM products that run on z/OS: This category includes the following:
– Products that are no longer marketed. Such products are not available
through ServerPac. To avoid having to reinstall these products every time you
reinstall a z/OS ServerPac order, place these products, if possible, in separate
product sets with separate libraries or SMP/E zones. Also, to make sure that
these products still run on z/OS, be sure to check “Appendix C. Minimum
Levels of IBM Software Products That Run with z/OS” on page 217.
Note: SMP/E V1R8.1 provides the BUILDMCS command to copy a product
from one zone to another. For example, if you have an existing image of a
vendor product in your current MVS zone, and it does not need to be installed
in that zone, you can use BUILDMCS to move it to another zone before you
install z/OS. In that way you avoid having the ServerPac overlay the vendor
product. For the information you need to use the BUILDMCS command and
restrictions on its use, see z/OS SMP/E Commands.
Products that are no longer marketed but are still service supported are
available for selection in the SystemPac shopping list. Where appropriate,
when you order a SystemPac, have these products separated into their own
SMP/E zone or volume via the Local Order Entry tool.
– Available MVS SREL products, such as PSF or NetView. You can order these
products in the same ServerPac or SystemPac as z/OS.
– Non-MVS SREL products, such as the subsystems (DB2, CICS, IMS, and
NCP). Check to make sure that these products do not need to be upgraded to
run with z/OS. If you need to upgrade a non-MVS SREL product, order it in a
separate ServerPac or use SystemPac. SystemPac provides the option of
integrated subsystems. The package you order can include z/OS and no more
than one of the subsystems (DB2, CICS, IMS, or NCP). The deliverable is
shipped to you integrated and requires just one installation, via either the
CustomPac Installation Dialog or a full volume restore.
Should you choose to order subsystems with z/OS in one single SystemPac
order, separate your subsystems from the z/OS SREL products to gain
maximum flexibility in the future. The Local Order Entry tool enables you to do
so. For a description of the Local Order Entry tool, refer to:
http://www.ibm.com/ca/custompac/
v User modifications: This category includes:
– User exits
– Updates to source code
– Zaps
– Changes to ISPF elements, such as panels, CLISTs, and EXECs.

Chapter 8. Preparing for Future Installations 165

 Isolate this code from the IBM code when possible by:
– Placing it in a separate library that can be concatenated ahead of the IBM
libraries
– Using the dynamic exits service and placing the code in separate libraries.

One simple way to tell whether user modifications must be reworked for the new
level of software is to try to reapply them and see how many of them SMP/E will
install. Those that SMP/E will not install will need to be changed for the new level
of software. This method works if you have followed IBM’s advice about using
SMP/E to install the code.

If your user modifications have been installed using SMP/E, you can get the list
of user modifications you now have installed by running a LIST SYSMODS
USERMODS command against each of your existing target zones. You will need
to evaluate each user modification to determine whether it is still needed and
whether it needs to be reworked to be reinstalled.

To save time, you can run SMP/E REPORT SYSMODS commands, specifying
each existing target zone on the INZONE keyword and each corresponding new
target zone on the COMPAREDTO keyword. SMP/E will create SYSMODS
Comparison Reports that identify user modifications that are installed in the old
zones and are applicable to FMIDs in the new zone. It will also create a job in
the SMPPUNCH data set to reinstall them (and any applicable PTF and APAR
SYSMODs) in the new ServerPac or SystemPac system’s target zone.

Some of your user modifications might be listed by the LIST commands but not
included in the SYSMODS Comparison Reports. These user modifications apply
to FMIDs that are not installed on your new system. Some FMIDs might have
been replaced by others, in which case you will have to rework applicable user
modifications before reinstalling them. The others might have no replacements
and their user modifications are almost certainly no longer needed.

For FMIDs that have changed, evaluate the usermods and rework them, if
necessary.

Keep the source for all user modifications in a single data set, and document
each modification. Such documentation often includes:
– The name of the part (for example the module) affected by the usermod
– The business justification for the usermod
– When the usermod can be eliminated
– The purpose of the usermod
– Instructions for reworking or reinstalling the usermod
– The product and current FMID to which the usermod is applied.

You might need to rework and reinstall source updates and zaps.

Some actions not only make a ServerPac or SystemPac (dump-by-data-set format)

installation easier, but can also organize code and data so that other tasks are
easier. Here are some recommended actions:
v SYSRES: Some SYSRES volumes are not large enough to hold all the z/OS
target libraries. If you have such a volume you can move some of the data sets
off SYSRES. For help in determining which ones to move, see “Recommended
Data Set Placement” on page 170.
v Parmlib and proclib:

166 z/OS V1R1.0 Planning for Installation

 – Don’t make changes to the parmlib and proclib data sets that you use for
production until you have seen what IBM sends in the copies that IBM ships
with z/OS. Compare the IBM copy to your production copy or use the IBM
library in your production concatenation and decide which of IBM’s parmlib
and proclib specifications apply to your environment and manually make the
changes. Copy any new parmlib and proclib members into your production
copy. Then, tailor your production copy, as needs require.
– In a multisystem environment, try to have SYSRES, master catalog, and
system-type libraries (such as IODF, SYS1.DAE, and RACF data) common to
as many systems as is practical. Use symbolic substitution to reduce the
number of parmlib and proclib members that are unique to specific systems.
Using symbols in parmlib members makes it easier to share a parmlib
member across multiple systems. z/OS provides a tool that helps you to verify
that your system symbolics work successfully in your own configuration before
you put the parmlib member into production. This tool, called the parmlib
symbolic preprocessor, runs as an ISPF dialog to interactively display the
results of symbol substitution before you IPL the system and use the symbols.
You can find the tool in members SPPINST and SPPPACK in
SYS1.SAMPLIB. Information about setting up and using the tool appears in
the prolog of the SPPINST member.

Use parmlib concatenation to separate your tailored parmlib members from the
IBM-supplied parmlib members. See information about parmlib concatenation in the
description of the LOADxx parmlib member in z/OS MVS Initialization and Tuning
Reference.

Placing Data Sets on Specific Volumes

Some SYSRES volume types, such as the 3390-3, are not big enough to hold all
the target libraries for a z/OS system. Therefore, you have to move some data sets
to SYSRES logical extension volumes (overflow volumes). This section describes
considerations for placing data sets on specific volumes. These considerations try
to minimize your migration actions, taking into account:
v Your ability to use a system (or subsystem) replacement
v Data set and system availability
v System performance
v System cloning and servicing techniques
v Sysplex/multisystem operations
v Your ability to exploit new technologies
v Sharing of data sets
v Backup and recovery
v Disaster recovery.

Using the guidelines in this section, you will have to determine which data set
placements work best in your environment, probably making trade-offs in order to
achieve your business goals.

Product Sets
Introducing Product Sets
A product set is a set of products that you should install, maintain, and migrate as a
group. Everyone has at least one product set that includes z/OS. The judicious
grouping of your other system software products into product sets can help you
avoid reinstalling software you have already installed, give you greater flexibility

Chapter 8. Preparing for Future Installations 167

 during migrations, control the amount of DASD used for system software, and make
it easier to have different groups maintain different sets of products.

Well-chosen product sets let you treat most system software in a logical, modular
way. When different images have different sets of requirements, you can use
product sets as modular building blocks to make the entire needed set of software
available on each image. Specific recommendations for placement of each product
set’s data sets are discussed in “Recommended Data Set Placement” on page 170.

Characteristics of a Product Set

A product set is a group of products that is logically separate from any other group
of products. Each product set is an entity that can be installed, maintained, and
migrated by itself. Each product set has its own data sets, typically on separate
DASD volumes, and its own SMP/E target and DLIB zones. Which products you
should place in each product set depends on how you plan to install, maintain, and
use software from different vendors.

When planning the number and content of product sets to be used in your
installation, consider:
v Software installation requirements.
Some products must be installed in data sets and SMP/E zones shared with
other products in order to work. Such products cannot be considered as
candidates for placement in different product sets. However, the remaining
products are potential candidates.
v Migration cycles.
Do you install and migrate all your software products at the same time (for
example, once a year)? Or do you install and migrate groups of products
separately? Software often installed or migrated separately includes subsystems,
software from vendors, and application software.
Any software installed or migrated on a cycle different from other software is
itself a candidate product set.
v Organizational requirements.
Does a single person or group of people do all software installations and
migrations? Or do different people maintain different products? Note that some
installations that once had separate organizations install and maintain different
product sets now have one group install all of them and others make the
software operational (including customization). This lets them include more
products in each product set and reduce the number of product sets.
Examples of software often maintained by different groups include application
development software (such as compilers and debuggers), database products
(such as IMS Database Manager and DB2), transaction processing products
(such as CICS and IMS Transaction Manager), and networking products (such as
ACF/NCP and NCP/SSP).
Software products maintained by different groups are sometimes candidates for
inclusion in separate product sets.
v Sharing boundaries.
Software can often be shared among multiple system images. There are many
considerations for sharing system software, and more information about this can
be found in OS/390 Software Management Cookbook , SG24-4775. The
boundaries on which you choose to share different products can vary, depending
on which products are being used.

168 z/OS V1R1.0 Planning for Installation

 When some products are shared among some sets of images and other products
are shared among different sets of images, they are candidates for inclusion in
different product sets.

Note: You should generally not separate products to control access to them on
different images for licensing reasons, unless the terms and conditions of
your licensing agreements require you to do so. Most often, access to
particular programs is better controlled using your security product.
v Product availability.
Some of the products you use might no longer be available from a particular
software vendor. They might originally have been placed in product sets with
other products. Depending on how the product is installed, it might become a
candidate for inclusion in a product set separate from the vendor’s other
products. Moving these products to separate product sets can sometimes let you
avoid reinstalling them each time you rebuild the product sets in which they were
originally placed.

Which Product Sets Are Appropriate?

One or more product sets, as described below, will be appropriate for your
installation. Any of these product sets can be merged with any other, as required by
your business needs. (The result of merging two product sets is considered to be a
single product set.) Any product set described below can also be split into two or
more product sets, if this is what’s needed to meet your installation’s requirements.
Product sets can be built at the same time or different times, and migrated together
or separately to different images as your business requires.

Each installation’s requirements usually lead to a unique number of product sets

and to unique content in each set. Remember that your objective in choosing the
number and composition of product sets is to control workload while providing the
amount of flexibility you need to manage your software easily. If you have either too
many or too few product sets, you will do more work during some phase of
installation or migration, and your system software will be harder to manage.

z/OS and Closely-Related Products Product Set: The z/OS product set consists
of all z/OS elements and features and other products that either must be installed
with z/OS or that you choose to install with z/OS. Some products must be installed
with z/OS because they share load modules with z/OS load modules. Others can
be installed separately but are difficult to maintain separately, because of frequent
service dependencies or local installation policies. Products in these two categories
should always be part of the z/OS product set.

Other products within the MVS SREL need not be installed with z/OS and are not
difficult to maintain separately. However, unless your installation has a reason to
place them in a separate product set, you should consider including them in the
z/OS product set.

Subsystem Product Sets: Subsystem software includes database software,

transaction processing software, and some network software. This software is often
installed using different installation methods, is usually migrated on different cycles,
is usually shared on different boundaries, and is often maintained by different
groups. These products are usually good candidates for different product sets.

Licensed Product Sets: If your migration cycles, organizational requirements, and

sharing of boundaries make it appropriate, you should consider creating a separate
product set for some products. Generally, such products should be reasonably

Chapter 8. Preparing for Future Installations 169

 stable and easy to install, maintain, and migrate separately. Examples of such
products include compilers, automation products, and products that can no longer
be ordered.

Vendor Product Sets: You should consider creating one or more product sets for
each vendor’s products.

Recommended Data Set Placement

Data set placement recommendations are not mandatory. The use of any or all of
this layout is strictly optional. The recommended layout provides a good foundation
for many recent functional and system management enhancements (such as
sharing a master catalog, indirect volume serial support, z/OS UNIX System
Services, and Parallel Sysplex). It can be used to suggest how you might place
data sets or as a set of objectives to which you can evolve.

To help you decide whether to follow the recommendations, ask yourself the
following questions. Positive answers indicate that at least some of the
recommended actions would be beneficial to you.
v Will you require additional SYSRES logical extension volumes? Some SYSRES
volume types, such as the 3390-3, are not big enough to hold all the z/OS target
libraries. Therefore, you might have to move some data sets to SYSRES logical
extension volumes.
v Do you plan to use indirect volume serial support? If so, the recommended layout
fits nicely with this support. See “Using Indirect Catalog Entries” on page 184 for
more information.
v Do you plan to use ServerPac or SystemPac (dump-by-data-set format) for future
installations? ServerPac replaces at least your target and distribution libraries, so
using the layout recommended in this section makes it easier to lay down the
ServerPac or SystemPac (dump-by-data-set format) libraries.
v Do you plan to share master catalogs? The recommended layout provides a
good foundation if you do.
v Do you plan to move your volumes across systems? If so, the recommended
placement of user catalogs creates more-portable volumes and reduces
migration workload. Also, the master catalog alias resolution support in
DFSMSdfp allows system symbols to be used for the user catalog name. See
z/OS DFSMS: Managing Catalogs for details.

Based on these factors, you should determine which data sets to place on each
volume based on data set type, not based on element, feature, or product. There
are five types of data sets in the recommended data set layout. Each type is placed
on a separate (logical) volume. The types of data sets and their volumes are:
v SMP/E global-shared data sets, on a volume shared by all systems in the
complex that need access to SMP/E global information. See “SMP/E Global Data
Sets” on page 171 for details.
v Target libraries (TLIBs) for product sets, on the following volumes:
– TLIB volume 1 (TVOL1)
– TLIB volume 2 (TVOL2) through TLIB volume n (TVOLn)
– HFS target volume
– Licensed product set volume (for those licensed programs not installed with
the z/OS product set)
– Vendor product set target volume
– Subsystem product set target volume

See “Target Libraries (TLIBs)” on page 172 for details.

170 z/OS V1R1.0 Planning for Installation

v Distribution libraries (DLIBs) for product sets, on the following volumes:
– DLIB volume for TVOL1
– DLIB volumes for TVOL2 through TVOLn
– DLIB volume for HFS target libraries
– DLIB volume for the licensed product sets
– DLIB volume for the vendor product sets
– DLIB volumes for the subsystem product sets

See “Distribution Libraries (DLIBs)” on page 176 for details.

v Image-related data sets, on the following volumes:
– Page data sets volume 1
– Page data sets volume 2 through n
– HFS customization volume

See “Image-Related Data Sets” on page 177 for details.

v Cluster-related data sets, on the following volumes:
– Master catalog volume (you can also choose to make this an image-related
volume)
– JES checkpoint volume
– JES spool volume
– Sysplex volume 1
– Sysplex volume 2
– Softcopy volumes

See “Cluster-Related Data Sets” on page 179 for details.

Many volumes on your system will contain data sets that are not supplied by
ServerPac or SystemPac (dump-by-data-set format). Keeping such volumes
separate from those that ServerPac or SystemPac (dump-by-data-set format) will
replace, or that you will replace when migrating the new system to other system
images, makes it easier to prevent overlaying data sets that you want to keep.
Volumes that contain non-ServerPac or non-SystemPac data sets might include, but
are not limited to, the volumes identified below in the data set descriptions, as well
as volumes for assorted data sets (dumps that were dynamically taken, logger
logstreams, and so forth). Note that you can install your ServerPac or SystemPac
(dump-by-data-set) order on volumes with existing data sets. See “Preparing for
Installation” on page 51 for the steps to follow when your target volumes contain
data that you want to preserve.

The rest of this section contains details about the five types of data sets and
volumes outlined above. As you’re reading, keep the following in mind:
v Volumes can be combined in order to conserve DASD. Combine volumes based
on like characteristics. For example, consolidating two SMS-managed volumes
with the same SMS constructs (Storage Class, Management Class and in the
same Storage Group) is more appropriate than consolidating a
non-SMS-managed volume and an SMS-managed volume.
v Although ServerPac and SystemPac (dump-by-data-set format) considerations
are mentioned specifically, this recommended system layout is equally applicable
to CBPDO users and will save time when the new system is migrated to other
images.

SMP/E Global Data Sets

These data sets contain SMP/E global system information. For the sake of
organization, and ease of backup and recovery, it’s a good idea to keep them
together on a volume shared by all systems that use SMP/E in your complex. If you

Chapter 8. Preparing for Future Installations 171

 maintain multiple global zones for subsystems or vendors, the global zone
described here should contain ZONEINDEX references to all other zones. This will
assist you in cross-zone conditional requisite checking without requiring any
changes to your installation’s maintenance procedures.

The recommended types of data sets for this volume are:

v SMP/E global CSI
v SMPPTS (this data set alone might fill a volume)
v SMP/E global logs (SMPLOG/A)

Target Libraries (TLIBs)

These data sets are SMP/E target libraries for products sets mentioned in “Which
Product Sets Are Appropriate?” on page 169.

If you want to take advantage of indirect volume serial support, do not

SMS-manage the target data sets that reside on volumes TVOL1 through TVOLn.

TVOL1 through TVOLn may be shared with other systems (for IPCS, WLM, or HCD
migrations, for example). If TVOL1 does not contain enough space to hold all the
data sets listed for your system, then the criterion for a split (between TVOL1A and
TVOL1B, for instance) would be that the IPCS and change migration libraries
should be kept together on the first volume (TVOL1A). (These libraries are listed in
“Load Module Libraries” on page 252.)

If you support more than one language and are short of space on TVOL1, you
might choose to put your primary language on TVOL1A and your secondary
languages on TVOL1B.

TVOL1 and TVOL2 contain the z/OS product set target libraries, except for HFS
files.

TLIB Volume 1 (TVOL1): TVOL1 is the first target library volume and the system
residence (IPL) volume. It contains many of the z/OS target libraries. Be sure to
leave enough free space to allow for future growth. TVOL1 allows you to IPL if one
or more TVOL2 through TVOLn volumes are temporarily not available.

TVOL1 contains some or all of the non-HFS target libraries for the z/OS product
set. (See “z/OS and Closely-Related Products Product Set” on page 169 for more
information on the z/OS product set.) This does not include the licensed product
set, which you install separate from z/OS (on licensed program volumes), or the
subsystem product set (on the subsystem target volumes).

The recommended types of TVOL1 data sets are given below. For each type you
are referred to one or more tables where detailed recommendations by DDDEF
name are listed. For other products in your z/OS product set that are not listed in
“Appendix E. Data Set Placement Recommendations for Target Volumes” on
page 243, you should determine which type of data sets they contain and on which
volumes to place them.
v Load libraries. See “Load Module Libraries” on page 252.
v Change migration libraries. These libraries are used, or might be used, during
migration from one level of software to another. These libraries are identified in
the tables as “Change Migration”. They include HCD, IPCS, SMP/E, and WLM
functions, which cover the data set types of CLISTs, messages, panels,
skeletons, tables, and the change migration library MIGLIB.
v Help libraries. See “Help Libraries” on page 251.

172 z/OS V1R1.0 Planning for Installation

v Panel libraries. See “Panel Libraries” on page 262.
v Message libraries. See “Message Libraries” on page 259.
v Skeleton libraries. See “Skeleton Libraries” on page 267.
v Table libraries. See “Table Libraries” on page 271.
v Fixed-block CLIST and EXEC libraries (if possible). See “CLIST Libraries” on
page 243 and “EXEC Libraries” on page 250. If you don’t use fixed-block CLIST
and EXEC data sets, then TVOL1 should contain your variable-block CLISTs and
EXECs and TVOL2 would contain your fixed-block CLISTs and EXECs. (In other
words, put the kind of CLISTs and EXECs you use on TVOL1.)
v Data libraries. Some data libraries should go on TVOL2. See “Data Libraries” on
page 244.
v SMP/E managed PARMLIB. This data set is the one pointed to by the PARMLIB
DDDEF, which will be used to store parmlib members supplied by products you
install. If you copy the SMP/E-managed PARMLIB data set into your own system
control data set, then the SMP/E-managed parmlib should be placed on
TVOL2-n. The placement of this PARMLIB data set makes it easier to use
concatenated PARMLIB support to reduce migration workload. See “Parameter
Libraries (Parmlibs)” on page 262.
v SMP/E managed PROCLIB. This data set is the one pointed to by the PROCLIB
DDDEF, which will be used to store JCL procedures supplied by products you
install. If you copy the SMP/E-managed PROCLIB data set into your own
procedure library, then the SMP/E-managed PROCLIB data set should be placed
on TVOL2-n. The placement of this PROCLIB data set makes it easier to use
concatenated PROCLIB support to reduce migration workload. See “Panel
Libraries” on page 262.

Reasons to put these data sets on TVOL1 are:

v These data sets are critical to basic system function and are required for
recovery. Should some TVOLn volumes be lost or become inaccessible, the
system is less likely to fail if the most critical data sets are all on a single volume.
Also, in the event that all TVOLn volumes are lost or become inaccessible, the
ability to IPL, log on, and use basic system functions after recovering TVOL1 can
speed the recovery of other volumes and greatly simplify the process of restoring
full function. (For example, restoring additional volumes from backup tapes can
be done in parallel, using cataloged tape data set names.)
v These data sets will be overlaid by a system replacement. By keeping them
together, you can more easily separate what will and will not be overlaid.
v The SMP/E DDDEFed PARMLIB and PROCLIB are on TVOL1 so that TVOL1
can be IPLed in a minimum setup (without TVOL2 through TVOLn) and still have
the SMP/E-installed defaults available. The members stored by SMP/E in the
PARMLIB pointed to by the PARMLIB DDDEF, and those stored in the PROCLIB
pointed to by the PROCLIB DDDEF, are not sufficient to IPL by themselves; a
minimum set of system control parameters and JCL procedures are required to
IPL and use the system. You can either concatenate your own PARMLIB and
PROCLIB data sets to these data sets (which IBM recommends) or add your
own members to these data sets.

TLIB Volume 2 (TVOL2) through TLIB Volume n (TVOLn): TVOL2 through

TVOLn are volumes used for data sets that do not fit on TVOL1. They are for the
z/OS product set; see “z/OS and Closely-Related Products Product Set” on
page 169 for more information about the z/OS product set. Products you want to
install separately should be placed instead on licensed program volumes or
subsystem volumes.

Chapter 8. Preparing for Future Installations 173

 The recommended types of TVOL2 through TVOLn data sets are given below. For
each type you are referred to one or more tables where detailed recommendations
by DDDEF name are listed. Again, for other products that you have ordered with
z/OS whose data sets are not listed in the tables, you should determine which type
of data sets they contain and on which volumes to place them.
v Fixed-block CLIST and EXEC libraries (only if variable-block CLIST and EXEC
libraries were used on TVOL1). See “CLIST Libraries” on page 243 and “EXEC
Libraries” on page 250.
v Sample and JCL libraries. See “Sample Libraries” on page 265.
v Source libraries. See “Source Libraries” on page 270.
v Macro libraries. See “Macro Libraries” on page 257.
v Workstation libraries (which are combined in the data libraries). See “Data
Libraries” on page 244.
v Softcopy libraries into which SMP/E installs. See “Softcopy Libraries” on
page 268.
v Font and printing libraries. See “Font Libraries” on page 250.
v Text libraries. See “Text Libraries” on page 272.
v Flat files that SMP/E cannot manage (interface repositories and so forth,
excluding books).
v MMS-compiled and MMS-source data sets. MMS-source data sets are those
data sets that are used as input into the MMS compiler.
v SMP/E target CSI.
v SMP/E target data sets: SMPLTS, SMPMTS, SMPSTS, SMPSCDS.
v User catalog for the SMP/E target CSI and MMS-compiled data sets.

If you find that just one volume (TVOL2) is not enough, and you require other
volumes (TVOL3 for instance), you could place groups of data sets (rather than
individual data sets) on one volume or the other. Some examples of groupings are:
v Operational data sets, such as flat files, font and printing libraries, MMS-compiled
libraries, and user catalogs.
v VSAM data sets, such as the target CSI, MMS-compiled clusters, and user
catalog.
v SMP/E work data sets, such as SMPLTS, SMPSCDS, SMPMTS, and SMPSTS.

Remember that these data sets are overlaid by a subsequent ServerPac or

SystemPac (dump-by-data-set format) installation and associated customization.

HFS Target Volume: This is a user-maintained volume and may be

SMS-managed. This volume is not overlaid when unloading the ServerPac or
SystemPac (dump-by-data-set format) HFS data sets. However, the data in the HFS
will be overwritten by the installation of service or the installation of z/OS with
CBPDO. Therefore, you must ensure that you have a copy of your HFS filesystem
before you install into it. See z/OS UNIX System Services Planning for more
information about installing service into the HFS.

The recommended types of data sets (filesystems) for the HFS target volume are:
v HFS data sets for z/OS elements or features that install into an HFS
v HFS data sets for products that run on z/OS, except data sets containing
customization data (which would be on the HFS customization volume)
v User catalog for HFS data sets on this volume

174 z/OS V1R1.0 Planning for Installation

 With the non-SMS HFS support available in the fourth quarter of 1999, you can
combine the HFS target volume and your TVOL2-n volumes if you wish. You might
want to combine them if the products they share are migrated on the same
boundary and there is enough space on the TVOL2-n volumes for the HFS data
sets.

Licensed Product Target Volume: The libraries on this volume consist of the
licensed product set that you might not have in a system-replacement order and
you want to keep separate. The data sets on this volume are not overlaid by a
system replacement and the content is decided on by the user. There can be any
number of this type of volume on a system.

The recommended types of data sets for this volume are:

v Licensed program target libraries
v SMP/E target CSI
v SMP/E target data sets: SMPLTS, SMPMTS, SMPSTS, SMPSCDS
v User catalog. The SMP/E target CSI should be defined using this catalog. Except
for any data sets you choose to catalog in the master catalog, all the licensed
program target libraries should also be cataloged in this user catalog, and ALIAS
entries should be defined in the master catalog to relate their high-level qualifiers
to this user catalog.

Reasons to put these data sets on this volume are:

v To keep data sets that cannot be system-replaced (no longer marketed by IBM,
older product levels, and so forth) on volumes other than TVOL1-TVOLn, so they
are not overlaid by a system replacement.
v To keep together licensed programs that have dependencies on each other.
v To facilitate data set sharing between systems and maintain data sets in one
place.

Vendor Product Target Volume: The libraries on this volume consist of the
vendor product set that you might not have in a system-replacement order and you
want to keep separate. There can be any number of this type of volume on a
system.

The recommended types of data sets for this volume are:

v Vendor target libraries (that can be separated)
v SMP/E target CSI
v SMP/E target data sets: SMPLTS, SMPMTS, SMPSTS, SMPSCDS
v User catalog for the SMP/E target CSI. Unless a data set must be in the master
catalog, all the vendor product target libraries should be cataloged in the user
catalog.

The reason to put these data sets on this volume is to keep the data sets off
volumes that are overlaid by a system replacement.

You will need to contact your vendors to determine whether their products need to
be updated for each z/OS release and whether the updates can be made ahead of
time. To access the vendor’s information through the World Wide Web, see:
| http://www.ibm.com/eserver/zseries/solutions/s390da/osnp.html

Subsystem Target Volume: The libraries on this volume consist of the subsystem
product sets (CICS, DB2, IMS, or NCP). There can be any number of this type of
volume on a system.

Chapter 8. Preparing for Future Installations 175

 The recommended types of data sets for this volume are:
v Subsystem target libraries.
v Alternate subsystem SMP/E global CSI, if applicable.
v SMP/E target CSI
v SMP/E target data sets: SMPLTS, SMPMTS, SMPSTS, SMPSCDS
v User catalog for the SMP/E global and target CSIs. Unless a data set must be in
the master catalog, all the subsystem target libraries should be cataloged in the
user catalog.

Reasons to put these data sets on this volume are:

v To keep these data sets off volumes that are overlaid by a system replacement.
v To keep the subsystem together on the same volume.
v To facilitate data set sharing between systems and maintain data sets in one
place.

A subsystem product set might need to be serviced before it can be used with a
new z/OS system. However, service updates usually can be made prior to the z/OS
migration.

Distribution Libraries (DLIBs)

You should place data sets on the DLIB volumes wherever they fit. There need not
be a correlation between TVOL1 and the DLIB volume for TVOL1, or between
TVOL2 and the DLIB volume for TVOL2, and so forth. It is possible, but not
necessary, to SMS-manage the data sets.

Keep in mind how other systems will use the distribution libraries when you are
deciding where to place them. There might be cases where you don’t want or need
a set of distribution libraries available on certain packs. These cases include:
v Distributing software to sites that don’t use SMP/E or need the distribution
libraries
v Having multiple target zones connected to a DLIB zone.

When allocating the distribution libraries you might have to use more than one DLIB
volume. See Table 5 on page 63 for an estimate of how much space the distribution
libraries in z/OS will use.

If space allows, any of the following DLIB volumes can be combined with their
corresponding target volumes: DLIB volume for licensed products, DLIB volume for
vendor products, and DLIB volume for subsystems.

If you choose to catalog your distribution library data sets, IBM recommends that
you catalog them in the user catalog used for the DLIB zone CSI. This makes it
easier to move the DLIB volumes into other environments, to switch between
different levels of DLIB volumes, and to have more than one level available at a
time. It also reduces the amount of update activity required for the master catalog.

DLIB Volumes for TVOL1, TVOL2 through TVOLn, and HFS: These distribution
libraries are the ones that are replaced by ServerPac or SystemPac
(dump-by-data-set format) for your z/OS product set. By keeping the distribution
libraries on the same volumes it will be easier to avoid overlaying data sets.
v DLIBs for TVOL1, TVOL2 through TVOLn, and TVOLH

The DLIB CSI should be placed on one of the DLIB volumes, along with a user
catalog for the DLIB CSI.

176 z/OS V1R1.0 Planning for Installation

DLIB Volume for Licensed Products: These are the distribution libraries that
correspond to the target libraries for TVOLP (the licensed product set). These are
data sets that would not be overlaid in a system replacement.
v DLIBs for TVOLP
v SMP/E DLIB CSI
v User catalog for the SMP/E DLIB CSI

DLIB Volume for Vendor Products: These are the distribution libraries that
correspond to the target libraries for TVOLV (the vendor product set). These are
data sets that would not be overlaid in a system replacement.
v DLIBs for TVOLV
v SMP/E DLIB CSI
v User catalog for the SMP/E DLIB CSI

DLIB Volumes for Subsystems: These distribution libraries are the ones that will
be replaced by ServerPac or SystemPac (dump-by-data-set format) for a subsystem
product set. By keeping the distribution libraries on the same volumes it will be
easier to avoid overlaying data sets.
v DLIBs for TVOLS
v SMP/E DLIB CSI
v User catalog for the SMP/E DLIB CSI

Image-Related Data Sets

These data sets contain nonshareable system image information. Although the
recommendation is that they be put on separate volumes, as described below, if
DASD is scarce you can combine them at the expense of performance or
availability, or both.

Image-related data sets should use system symbolics in their names for easier
maintainability. For more information on system symbolics, see z/OS MVS
Initialization and Tuning Reference.

Page Data Set Volume 1: The recommended types of data sets for this volume
are:
v PLPA (1-cylinder allocation)
v Common

Unless your system is central-storage constrained, and has significant PLPA paging
activity, there is little or no performance impact to combining the PLPA and
COMMON page data sets. The PLPA data set should be allocated first, as a
1-cylinder data set. The COMMON data set should be allocated second,
immediately following the PLPA data set on the volume. The COMMON data set’s
size should be large to contain both PLPA and COMMON pages.

This causes the vast majority of PLPA pages to be written to the COMMON page
data set during IPL. This allows the operating system to use chained CCWs within
a single data set and improves performance when both data sets are on the same
volume.

Note: A warning message (ILR005E) is issued during IPL when PLPA pages
overflow into the COMMON page data set during CLPA processing. This
message is intended to alert you to the possibility that PLPA pages might
have to be retrieved from data sets on different volumes (which would
negatively affect performance if there was significant PLPA paging). When
PLPA and COMMON page data sets are on the same volume, this message
can be ignored.

Chapter 8. Preparing for Future Installations 177

 Page Data Set Volumes 2-n: The recommended types of data sets for these
volumes are:
v Local
v SMF
v RMF reporting
v STGINDEX data sets (if used)
v Image-related LOGREC data set (if used)

Considerations when setting up a page data set volume are:

v Where possible, each local page data set should be placed on a dedicated
volume connected to a control unit that is not used for other paging volumes, and
on channel paths that are not used for other paging volumes. Although paging
rates to DASD might be low, given sufficient central and expanded storage,
increasing workloads might eventually cause significant paging. If this happens,
locating local page data sets as suggested provides the best performance.
Additionally, a large number of page data sets yields better performance than a
small number if there is significant paging to DASD.
IBM does not recommend placing other data sets on the volumes used for page
data sets. However, if you must place other data on local page data set volumes,
choose data with the lowest frequency of reference possible to minimize
contention with paging.
v As one might expect, the I/O activity to SMF data sets is proportional to the
amount of SMF data you record from your specified SMF parmlib member.
v I/O to STGINDEX data sets is only done when a job stream does batch
checkpoints to save status (to allow the job stream to be restarted) or obtains
restart status; therefore, this data set has relatively low I/O. If your installation
always IPLs using CVIO or CLPA (which implies CVIO), there is no reason to
have a STGINDEX data set. In this case, specify VIODSN=IGNORE in
IEASYSxx. For more information, see z/OS MVS Initialization and Tuning
Reference.
v For information on choosing the LOGREC recording medium, see “Recording
Logrec Error Records” in z/OS MVS Diagnosis: Tools and Service Aids. I/O
activity is typically low for the image-related LOGREC data set.
v Dynamic dumps are recommended, so SVC dump data sets are not listed above.

HFS Customization Volume: This is an installation-maintained volume. The data

sets on this volume will not be overlaid by system replacement. This volume is
separate from the HFS target volume because it may contain unshareable HFS files
that will generally need to be mounted MODE(RDWR).

The recommended types of data sets for this volume are:

v HFS data sets that must be in write mode (for instance, /etc, /u, /var) and contain
customized information.
v A user catalog to own the HFS data sets (optional). This makes the volume
portable using dump and restore, catalog services (IMPORT CONNECT), and
SMS definition changes.

Reasons to put these data sets on this volume are:

v To keep customer HFS customization filesystems separate so that they can be
mounted under the file system provided in a system replace.
v To improve system performance. The number of HFS data sets that must be in
write mode should be minimized to just what is required.

178 z/OS V1R1.0 Planning for Installation

v To keep installation-maintained HFS data sets (which may be SMS-managed)
together on the same volume for easier management.

Cluster-Related Data Sets

These are shareable data sets used in a multisystem environment. Cluster-related
data sets should use system symbolics in their names for easier maintainability. For
more information on system symbolics, see z/OS MVS Initialization and Tuning
Reference.

While all cluster-related data sets can be combined on the same volume, it is
usually preferable to separate certain data sets from others for performance or
availability reasons. For example, the following data sets should usually not be
placed on the same volume:
v Primary and secondary RACF databases
v JES spool and checkpoint data sets
v Primary and backup SMS data sets
v Primary and secondary couple data sets

Note: You should also consider placing the primary RACF database in the coupling
facility.

Master Catalog Volume: The recommended types of data sets for this
cluster-related volume are:
v Master catalog
v BRODCAST
v Customer parmlib concatenation (not the SMP/E DDDEFed PARMLIB)
v Customer proclib concatenation (not the SMP/E DDDEFed PROCLIB)
v UADS (if used)
v VTAMLST
v SMS ACDS, CDS, model DSCB, HSM, RMM, and so forth
v APPC VSAM data sets (side information, TP profile)
v System control files (TCP/IP configurations and so forth)
v Primary RACF database
v IODF
v SYS0.IPLPARM
v UCATs
v SYS1.DDIR sysplex dump directory data set
v DAE data set

Considerations when setting up the master catalog volume are:

v BRODCAST (when individual user BRODCAST data sets are in use), LOGREC,
parmlib, proclib, UADS, IODF, and DAE are low-activity data sets.
v Customer parmlib and customer proclib should be concatenated with other
parmlibs and proclibs. For information on using system symbolics in
concatenated parmlibs, see z/OS MVS Initialization and Tuning Reference.

JES2 Checkpoint Volume: For maximum performance and reduced contention,

place the primary JES2 checkpoint data set on its own dedicated volume. The JES2
checkpoint primary data set may be on a coupling facility.

JES2 Spool Volume: Except in the case of a single-system MAS complex, you
should dedicate JES2 spool volumes to spool data sets, with no other data sets on
the volumes. A system can have many spool volumes.

The JES2 checkpoint duplex data set may be on a coupling facility.

Chapter 8. Preparing for Future Installations 179

 Sysplex-Related Volume 1: This is a user-maintained volume and does not
contain data sets overlaid by a system replacement.

The recommended types of data sets for this volume are:

v SYSPLEX primary
v CFRM alternate
v ARM primary
v WLM primary
v LOGR primary

Considerations when setting up sysplex-related volume 1 are:

v Couple data sets should not be placed on volumes that have high I/O activity, are
subject to RESERVEs, have page data sets, contain SYS1.DUMPnn data sets,
or are eligible for allocation of data sets dynamically allocated for SVC dumps.
v The CFRM primary and SYSPLEX primary should be on different volumes
attached to different control units. All other primary couple data sets can reside
on the same volume, and all other alternate couple data sets can reside on a
different volume.

You can find more guidelines for placement of couple data sets in z/OS MVS
Setting Up a Sysplex.

Sysplex-Related Volume 2: This is a user-maintained volume and does not

contain data sets overlaid by a system replacement.

The recommended types of data sets for this volume are:

v SYSPLEX alternate
v CFRM primary
v ARM alternate
v WLM alternate
v LOGR alternate
v Secondary RACF database

Couple data sets should not be placed on volumes that have high I/O activity, are
subject to RESERVEs, have page data sets, contain SYS1.DUMPnn data sets, or
are eligible for allocation of data sets dynamically allocated for SVC dumps.

You can find more guidelines for placement of couple data sets in z/OS MVS
Setting Up a Sysplex.

Softcopy Volume: This volume holds softcopy books and related data sets.

There can be any number of this type of volume on a system. This is a

user-maintained volume and does not contain data sets overlaid by a system
replacement.

The recommended types of data sets for this volume are:

v Books
v Bookshelves
v Bookindexes

The data sets on the softcopy volume are recommended to be SMS-managed. This
allows the hierarchical storage manager (HSM) to migrate any unused or
infrequently-used data sets or books.

180 z/OS V1R1.0 Planning for Installation

Implementing the Recommended Data Set Placements
As you plan how you will implement the recommended data set placements, be
sure to include the following activities:
v Decide whether to merge data sets.
v Determine which data sets to move and where to move them.
v Choose a volume serial naming convention if you plan to use indirect volume
serial support.
v Decide whether to use your existing master catalog.
v Move data sets to appropriate volumes.
v Update SMP/E DDDEFs.
v Update catalog entries to point to appropriate volumes.
v Update IEASYMxx in your parmlib, using volume naming conventions.
v If using ServerPac or SystemPac (dump-by-data-set format), save your
configuration for the next release.
v Update any environmentals that are applicable.

Decide Whether to Merge Data Sets

During a ServerPac or SystemPac (dump-by-data-set format) installation you can
merge data sets while you modify the shipped order’s configuration. This makes it
possible to consolidate data sets that are used in the same ways. For example, you
might merge ISPF panel libraries to create a smaller number of panel libraries. The
merged data set configuration remains available for your use during subsequent
installations.

The CustomPac Installation Dialog shows the data sets that are eligible for merging
with a data set that you select. Not all data sets can be merged, however. The
Dialog allows you to merge data sets only when they share all of the following
attributes with the target data set:
v Same record format (RECFM)
v Same logical record size (LRECL)
v Same data set type (DLIB or target library)
v A data set organization of PO (DSORG=PO).

The candidate list is merely a reflection of the merge rules; you should not simply
merge all eligible data sets. Instead, base your merge decisions on logical
groupings and similarity of content (for example, all panel libraries). Further, take
extra care if you choose to merge system-critical data sets, such as those listed in
the LNKLST, LPALST, and APFLST parmlib members; merging such data sets could
prevent the system from IPLing properly.

Determine Which Data Sets to Move and Where to Move Them

Review “Appendix E. Data Set Placement Recommendations for Target Volumes”
on page 243 to determine which of your data sets you will need to move.

Understand the effects of this move on your environment. Do you have any
applications that refer to the data sets specifying a UNIT and VOLUME? If
references to the moved data sets use the catalog, and the catalog has been
updated, then moving the data sets should have minimal impact. However, if the
catalog is shared with other systems, then the impact would be greater.

You should also review your backup and recovery procedures for the data sets you
plan to move.

Chapter 8. Preparing for Future Installations 181

 Choose a Volume Serial Naming Convention If You Plan to Use
Indirect Volume Serial Support
If you follow a naming convention for your SYSRES logical extension volumes, you
can use a single SYMDEF statement in your IEASYMxx parmlib member. For more
information about indirect cataloging, see “Using Indirect Catalog Entries” on
page 184.

Decide Whether to Use Your Existing Master Catalog

Is your current master catalog shared between several images? If so, will all images
in your system use the same layout?

IBM recommends that all images use the same layout in order to share the master
catalog. If all systems will not use the same layout, then IBM recommends that the
master catalog not be shared. In this situation, a separate master catalog for the
system that has been converted to the layout must be used because the same data
set cannot be cataloged on two different volumes.

Keep in mind that a catalog that contains extended indirect catalog entries cannot
be used by a system where the support is not available. If you plan on sharing your
master catalog with a down-level system that does not provide this function, you
must decide if you will:
v Upgrade the down-level system to the minimum required for extended indirect
cataloging
v Not use extended indirect cataloging until each image has the minimum required
v Use a separate master catalog on the later system, and discontinue sharing
master catalogs.

Move Data Sets to Appropriate Volumes

If you are implementing the recommended data set placements during your
ServerPac or SystemPac (dump-by-data-set format) installation, once you have
configured your system data sets you do not have to move any data sets on the
global, target, distribution, image, and some cluster volumes. The data sets will
already be restored from the ServerPac or SystemPac (dump-by-data-set format) in
the configuration you have chosen.

Remember that dump directory, SMS, sysplex, and system logger data sets are not
provided in ServerPac or SystemPac (dump-by-data-set format). These data sets
will still need to be moved to the appropriate volumes.

If you are implementing the recommended data set placements outside of a

ServerPac or SystemPac (dump-by-data-set format) installation, move the data sets
you researched onto the appropriate volumes. You might need some spare DASD
space into order to move the data sets to a temporary location in order to do a
swap. How much space you’ll need will depend on how many data sets you’re
moving.

Update SMP/E DDDEFs

If you are implementing the recommended data set placements during your
ServerPac or SystemPac (dump-by-data-set format) installation, once you have
configured your system data sets you do not update your SMP/E DDDEFs to reflect
the configuration. The DDDEFs will correctly identify the data sets for the
configuration you have chosen.

If you are implementing the recommended data set placements outside of a

ServerPac or SystemPac (dump-by-data-set format) installation, update your
DDDEFs to identify the appropriate volumes. You can use the SMP/E ZONEEDIT

182 z/OS V1R1.0 Planning for Installation

 command. If your data sets are cataloged, you won’t have to update the UNIT and
VOLUME. You should verify that the data sets you moved are correct in their
DDDEFs.

Update Catalog Entries to Point to Appropriate Volumes

If you are implementing the recommended data set placements during your
ServerPac or SystemPac (dump-by-data-set format) installation, once you have
configured your system data sets, the catalog your ServerPac or SystemPac
provides will correctly reflect your configuration.

If you are implementing the recommended data set placements outside of a

ServerPac or SystemPac (dump-by-data-set format) installation, update your
catalog to identify the appropriate volumes.

Import the user catalogs created to manage the HFS and VSAM (including CSI)
data sets, and define the necessary aliases.

If you are using extended indirect cataloging, your catalog should reflect the
SYSRES logical extension volumes by using your system symbols. It is
recommended that &SYSR2 be used as the first SYSRES logical extension symbol
when using extended indirect cataloging.

Update IEASYMxx in Your Parmlib

Update your parmlib member to reflect the system symbols that you used in your
catalog for extended indirect cataloging. Your IEASYMxx member must match your
catalog entries in order for your data sets to be found.

If Using ServerPac or SystemPac (Dump-by-Data-Set Format),

Save Your Configuration for the Next Release
Because ServerPac or SystemPac (dump-by-data-set format) can save your
configuration and reuse it for your next ServerPac or SystemPac, it is
recommended that you use this function. Once your configuration is defined, you
will not have to reconfigure the same data sets again.

Update Any Environmentals That Are Applicable

If you have any customization, applications, or parameters in your environment that
have to be updated to reflect your new layout, these need to be updated.

Choosing a Naming Convention for Data Sets

Choosing the right naming conventions for system software data sets can save you
considerable time during installation and migration.

Some data sets are associated with only one system in a multisystem environment.
Choose names for these data sets that reflect the name of the specific system.
Names of system operational data sets, such as page and swap data sets, should
include the system name. You can accomplish this using the IBM-supplied system
symbol &SYSNAME.

Remember that once you go into production with a set of naming conventions, you
cannot easily change them.

Using Symbolic Substitution

Using symbolic substitution involves carefully establishing naming conventions for
such things as:
v Parmlib and proclib members

Chapter 8. Preparing for Future Installations 183

 v Data sets
v System images
v HCD definitions
v Network definitions
v Subsystems.

Data Set Names Restructured

IBM has removed the level-dependent qualifiers (such as V1R1M0) from default
data set names for elements and features in order to ease your migration to a new
release. This preserves much of your existing JCL, system procedures, parmlib and
other system control file contents, and security system definitions across upgrades,
saving you time and reducing the opportunity for error because updates will be
limited to just the data sets in which the low-level qualifiers were changed. IBM
recommends that you use the new names. For a list of the old and new names,
refer to z/OS V1R1.0 Program Directory.

If you are installing z/OS using ServerPac or SystemPac (dump-by-data-set format),

you can remove additional level-dependent qualifiers and your changes will be
remembered (after you save your configuration and then merge) for future
ServerPac or SystemPac installations. If you do rename additional data sets, you
must also update operational procedures to reflect the new names.

Recognizing that you might delay your migration to the current JES level shipped
with z/OS, IBM has added a level-dependent qualifier to JES2 and JES3. This will
allow you to more easily separate your existing JES from your new JES.

If you plan to use only the level of JES2 or JES3 provided with z/OS V1R1 (not a
previous JES2 or JES3 release), and you are migrating to z/OS V1R1 JES2 or
JES3 at the same time as the other elements and features in z/OS V1R1, you
might decide to use static names for the z/OS V1R1 JES2 or JES3 libraries,
omitting the level-dependent (VnRnMn) qualifier. This minimizes changes you must
make from release to release.

Using Indirect Catalog Entries

Indirect cataloging, also known as indirect volume serial support, allows the system
to dynamically resolve volume and device type information for non-VSAM,
non-SMS-managed data sets that reside on the system residence (IPL) volume
when accessed through the catalog. This allows you to change the volume serial
number or device type of the system residence volume without also having to
recatalog the non-VSAM data sets on that volume.

Extended indirect volume serial support allows catalog entries to be resolved using
system symbols defined in an IEASYMxx member of parmlib, so that indirect
references can be made to one or more logical extensions to the system residence
volume. Like indirect catalog support, this support lets you change the volume serial
numbers or device types of system software target volumes without having to
recatalog their non-VSAM data sets. Therefore, you can have multiple levels of
z/OS data sets residing on multiple sets of volumes with different names and device
types, and use them with the same master catalog.

Furthermore, extended indirect volume serial support includes a system-defined

static symbol, &SYSR1. The value of &SYSR1 is automatically set to the volume
serial of the IPL volume. If you name your system residence volumes and their

184 z/OS V1R1.0 Planning for Installation

 extensions according to a pattern, you can use substrings of the &SYSR1 symbol to
assign substitution text to symbols for the other volumes.

Using indirect catalog entries, together with the extended support, allows you to
share master catalogs among multiple images that use different volumes with
different names for the system residence volumes and their extensions. You can
also do this using a single SYMDEF for all images in a shared parmlib data set.
Thus, once set up, no future updates should be needed to continue using this
support.

For details about how to use indirect volume serial support, see z/OS MVS
Initialization and Tuning Reference.

Using Parmlib Concatenation (Logical Parmlib)

You can concatenate up to 10 data sets to SYS1.PARMLIB, in effect creating a
“logical parmlib”. You define the concatenation in the LOADxx member of
SYS1.PARMLIB or SYSn.IPLPARM. Programs can use the IEFPRMLB macro to
obtain the parmlib concatenation data set list, allocate and open the parmlib data
sets, read a specified parmlib member, and close and unallocate the parmlib data
sets. In addition, the operator, if desired, can use a SETLOAD command to switch
from one logical parmlib to another without an IPL.

The overriding benefit of using parmlib concatenation is that it gives you greater
flexibility in managing parmlib. Specifically, it lets you:
v Separate IBM-supplied members from locally-customized ones
v Separate members based on job responsibility and security requirements
v Separate members for change-management purposes.

If you install using ServerPac or SystemPac, the IBM-supplied defaults cause the
following concatenated parmlib data sets to be searched in the order shown when
you IPL the target system:
1. SYS1.PARMLIB (either the SYS1.PARMLIB supplied by IBM and edited by you
or your original SYS1.PARMLIB updated appropriately)
2. CPAC.PARMLIB (supplied by IBM and customized for your ServerPac or
SystemPac order)
3. SYS1.IBM.PARMLIB (supplied by IBM).

For further information about specifying parmlib concatenation, see z/OS MVS
Initialization and Tuning Reference.

DASD Space Utilization and Performance

The space required by system software data sets, except for PDSE data sets, is
affected by the block sizes you choose for those data sets. Generally, data sets with
larger block sizes use less space to store the same data than those with smaller
block sizes. Data sets that store more data in less space usually offer better DASD
performance than those that use more space to store the same data.

There are some exceptions to the general rule that larger block sizes result in better
space utilization. For example, fixed block (FB) record format data sets should not
be allocated with block sizes larger than half the track length of the DASD they are
allocated on. Doing so will cause considerable DASD space to be wasted, because
current DASD track lengths are less than twice the maximum block size of 32,760

Chapter 8. Preparing for Future Installations 185

 bytes. However, some data sets are best allocated using specific block sizes. When
this is true of system software data sets, IBM recommends specific block sizes for
them.

Note: Block sizes listed in the data set space tables in program directories are not
generally recommended unless they are explicitly identified as
recommended. You should treat the recommendations in this chapter as
though they apply to all the system software data sets you allocate unless
the product specifically says to do otherwise.

Generally, system-determined block sizes (SDB) makes the best choice for block
size for fixed block (FB), variable blocked (VB), and variable-block spanned (VBS)
record format data sets. You should use SDB for all system software data sets with
these record formats except those for which IBM specifically recommends other
block sizes. One way to do this is specifying BLKSIZE=0 in the DCB parameter of a
DD statement when allocating new data sets using JCL. For details about how to
specify system-determined block sizes, see z/OS MVS JCL Reference.

Note that system determination of block sizes affects the block size and number of
blocks used. It does not affect the amount of space allocated in a data set. The
amount of space is defined by IBM (in sample jobs and program directories).

Undefined Record Format Data Sets

Data sets with undefined (U) record formats do not follow the same rules as those
with other record formats. In particular, most load libraries in partitioned data sets
(not PDSEs) will require less space (often as much as 20% less) and offer better
performance at increasing block sizes right up to the block size limit of 32,760
bytes. This is because the program management binder, linkage editor, and
IEBCOPY’s COPYMOD command use the data set block size only to set the
maximum block length they will use. They will write a block whenever the space
available on a track is greater than the minimum block size (over which you have
no control) and less than or equal to the maximum block size.

Allocate all load libraries using a block size of 32,760 bytes unless you plan to
move your system software data sets from the device types on which they were
originally allocated to device types with shorter track lengths, or plan to move them
between device types having different track lengths without using IEBCOPY
COPYMOD. A block size of 32,760 bytes will optimize space utilization and
performance for all system software load libraries.

Using Recommended Block Sizes for z/OS Data Sets

For most efficient use of DASD, IBM recommends that you allocate z/OS data sets
using the following block sizes:
v Use the system-determined block size for most non-RECFM U data sets (for
example, code BLKSIZE=0 in JCL).
v For RECFM U data sets, use BLKSIZE=32760. (Note that 32760 is optimum
because all supported DASD types have track lengths greater than 32,760
bytes.)
v If you use a UADS data set for TSO/E, you should generally use the same block
size you currently use to allocate a new one. Do not allocate the UADS data set
with a system-determined block size. This will result in very poor DASD space
utilization. Instead, model your new UADS from your existing UADS or start with
a small block size and increase the block size if a significant number of user ID

186 z/OS V1R1.0 Planning for Installation

 entries are split into multiple members. For details about allocating a UADS data
set and optimizing its block size, see z/OS TSO/E Customization.
v The AFP font libraries should not be allocated with system-determined block
sizes. The correct block size for the font libraries is 12288. The font data sets will
take up more space if system-determined block sizes are used and will result in
very poor DASD space utilization.

For details about the conditions under which the system can determine the optimum
block size for a data set, look for information about system-determined block sizes
in z/OS DFSMS: Using Data Sets.

Chapter 8. Preparing for Future Installations 187

188 z/OS V1R1.0 Planning for Installation
 Appendix A. Installation Plan Skeleton
An installation plan is a record of the actions you need to take to install z/OS. This
appendix contains a skeleton of a sample installation plan to help you get started
creating your own installation plan.

Installing: _______________ (Product version and release)

Migrating from: _______________ (Product version and release)
Installation method:

____ ServerPac
____ CBPDO
____ SystemPac (full volume dump format)
____ SystemPac (dump-by-data-set format)
Project manager: ____________________________

Project objectives:

Examples: target completion date and resource assumptions

Learn about z/OS

Action Start End Who does Information source
Learn about the new z/OS Planning for Installation (“Chapter 1.
product release. Learning about z/OS” on page 1), z/OS
Introduction and Release Guide
| Become familiar with z/OS Information Roadmap, z/OS publications
| product documentation. on the World Wide Web at
| http://www.ibm.com/servers/eserver/
| zseries/zos/bkserv/
Schedule education. For IBM courses, call 1-800-IBM-TEACH or
visit http://www.training.ibm.com/.

In the following table, list the formal and informal educational classes that will
prepare I/S staff, application programmers, and end users for the new system.

Course name Course ID Vendor Dates Staff to enroll

© Copyright IBM Corp. 1996, 2001 189

Prepare the Driving System
Note: Skip this section if you’re doing a full volume dump SystemPac installation.
Such an installation does not require a driving system. Installation is done by
using ICKDSF to do the initialization, and Innovation FDR or DFDSS to
perform the pack restore. These programs can exist on your driving system
or, if you do not have a driving system, you can restore them from the
stand-alone tape that came with your SystemPac order. Refer to the
SystemPac Installation Guide for details regarding the installation.

Action Start End Who does Information source

Review software and hardware PSP IBMLink
buckets for changes to planning
information.
Identify driving system software z/OS Planning for Installation
requirements. (“Identifying Driving System
Software Requirements for
ServerPac and Dump-by-Data-Set
SystemPac Orders” on page 48 or
“Identifying Driving System
Software Requirements for CBPDO
Orders” on page 54)
Identify driving system hardware z/OS Planning for Installation
requirements. (“Identifying Driving System
Hardware Requirements” on
page 57)
Complete the “Driving System
Components” sections below.
Order driving system hardware. Completed “Driving System
Components: Hardware” section
Order driving system software Completed “Driving System
Components: Software” section
Install or update driving system Related product documentation
hardware.
Install or update driving system Related product documentation
software.

Driving System Components: Software

Check one:

___ All requirements are satisfied by currently installed software

___ Order the Customized Offerings Driver (IBM Product 5665-343)
___ Order the following additional software:

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

190 z/OS V1R1.0 Planning for Installation

Driving System Components: Hardware
Check one:

___ All requirements are satisfied by currently installed hardware

___ Order the following additional hardware:

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

__________________________________________________________________

Prepare Target System Hardware and Software

Action Start End Who does Information source
Choose software to install on the z/OS Planning for Installation
target system: (“Choosing Software Products to
v z/OS optional features Install and Identifying Requisites” on
v Products required by z/OS page 59)
v Additional IBM products
v ISV products
Choose the JES level that you want z/OS Planning for Installation
to run. (“Using Your Existing JES2 or JES3
with z/OS V1R1” on page 65)
Choose target system hardware to z/OS Planning for Installation
install or upgrade. (“Identifying Hardware
Requirements for the Target
System” on page 62)
Complete the “Target System
Components” section below.
Order new target system software. Completed “Target System
Components” section
Order new target system hardware. Completed “Target System
Components” section
Install or upgrade target system Related product documentation
hardware.
Receive software shipment and Packing lists in shipment
verify contents.

Target System Components: Software

Check when complete:

___ ServerPac, CBPDO, or SystemPac product order checklist attached

___ List of additional IBM software products attached
___ List of ISV products attached

Appendix A. Installation Plan Skeleton 191

Target System Components: Hardware
Check one:

___ All requirements are satisfied by currently installed hardware

___ Order additional hardware (Attach order form; consider
processor, DASD, tape, networking, and printer requirements)

Ensure Coexistence
Identify the service you must apply to ensure that other systems or older levels of
software will continue to run correctly with the new level of software.

Action Start End Who does Information source

Identify coexistence service z/OS Planning for Installation
needed. (“Chapter 5. Ensuring Coexistence”
on page 71) and other sources
such as PSP buckets and z/OS
Parallel Sysplex Test Report
Identify additional coexistence Sources such as PSP buckets and
actions needed. z/OS Parallel Sysplex Test Report
Install coexistence maintenance on “Coexistence” section of this plan
existing system software.

Coexistence Service Required

APAR/PTF number Receiving system name Comments

Additional Coexistence Actions Required

Action Receiving system name For instructions, refer to...

192 z/OS V1R1.0 Planning for Installation

 Prepare for Migration
Identify the actions you must take to migrate existing system software to the new
software level. You should consider not only z/OS elements and features such as
the BCP and JES, but other IBM products such as subsystems and ISV products as
well.

Action Start End Who does Information source

Identify migration actions for z/OS z/OS Planning for Installation
elements and features. (“Chapter 6. Preparing for
Migration” on page 83) and
element-specific migration guides
Identify migration actions for other Product-specific migration guides
IBM and ISV products.
Complete the “Migration Actions”
section of this plan.

Pre-IPL Migration Actions

List the migration actions to perform prior to IPLing the target system for the first
time. (SystemPac actions are applicable to dump-by-data-set SystemPac orders
only. For full volume dump SystemPac orders, most of the activities below are done
for you during the production of your system based on specifications you provide
during local order entry.)

Action For instructions, refer to...

Create IPL text. If ServerPac: ServerPac: Installing Your Order

If CBPDO: z/OS V1R1.0 Program Directory

If SystemPac: SystemPac Installation Guide

Build stand-alone dump text. If ServerPac: ServerPac: Installing Your Order

If CBPDO: z/OS V1R1.0 Program Directory

If SystemPac: SystemPac Installation Guide

Format any new DASD data sets to be z/OS MVS Diagnosis: Tools and Service Aids
used for stand-alone dump.
Create or update an IODF. If ServerPac: ServerPac: Installing Your Order

If CBPDO: z/OS V1R1.0 Program Directory

If SystemPac: SystemPac Installation Guide

Set up a new IPCS environment. z/OS MVS IPCS Customization
Update the TSO logon procedure. If CBPDO: z/OS V1R1.0 Program Directory
Update system control files (for z/OS MVS Migration and other product publications
example, parmlib, proclib, and /etc files).
| Prepare for use of ILM (for example, set z/OS IBM License Manager Planning and Customization
| up a license server certificate repository,
| set up a DASD-only log stream)
| Prepare for use of msys for Setup (for z/OS Managed System Infrastructure for Setup User’s Guide
| example, verify the JAVA level, set up
| sharing of security databases, enable
| the job submission interface of FTPD)

Appendix A. Installation Plan Skeleton 193

 Action For instructions, refer to...

Post-IPL Migration Actions

List the migration actions to perform after the target system has been IPLed and
verified.

Action For instructions, refer to...

Rework and install user modifications Product publications
and SVCs needed to IPL.
Reconnect subsystems (DB2, CICS, Product publications
IMS, NCP).
Update operational procedures, Product message and command manuals
including automation.
Update administrative procedures. Product publications
Update security procedures. Security product publications
Update backup and recovery Product publications
procedures.
| For ILM: load certificates, set up z/OS IBM License Manager Planning and Customization
| security definitions and configuration
| files for the license server and agent,
| and update IEASYSxx (ILMLIB= and
| ILMMODE=)
| For msys for Setup: set up the LDAP z/OS Managed System Infrastructure for Setup User’s Guide
| Server

Build and Verify the Target System

The actions you take for this task depend on the installation method you use.
Samples are provided for the following installation methods:
v ServerPac or dump-by-data-set SystemPac
v CBPDO
v SystemPac full volume dump

194 z/OS V1R1.0 Planning for Installation

Build and Verify the Target System (ServerPac or Dump-by-Data-Set
SystemPac Installation)
Action Start End Who does Information source
Prepare target system volumes for z/OS Planning for Installation
ServerPac or SystemPac (“Preparing for Installation” on
(dump-by-data-set format) page 51)
installation.
Review PSP buckets for latest IBMLink
installation information.
Receive the ServerPac or If ServerPac: ServerPac: Using the
SystemPac (dump-by-data-set) Installation Dialog
order.
If SystemPac: SystemPac:
CustomPac Dialog Reference
Tailor the work configuration. If ServerPac: ServerPac: Using the
Installation Dialog

If SystemPac: SystemPac:
CustomPac Dialog Reference
Run installation jobs. If ServerPac: ServerPac: Installing
Your Order

If SystemPac: SystemPac
Installation Guide
(dump-by-data-set format)
Review system HOLDs.
Run element-specific If ServerPac: ServerPac: Installing
post-installation jobs on the driving Your Order
system.
If SystemPac: SystemPac
Installation Guide
(dump-by-data-set format)
Preform pre-IPL migration and “Pre-IPL Migration Actions” section
customization tasks. of this plan
IPL the target system and log on. If ServerPac: ServerPac: Installing
Your Order

If SystemPac: SystemPac
Installation Guide
(dump-by-data-set format)
Run element-specific If ServerPac: ServerPac: Installing
post-installation jobs on the target Your Order
system.
If SystemPac: SystemPac
Installation Guide
(dump-by-data-set format)
With ServerPac, set up z/OS UNIX. If ServerPac: ServerPac: Installing
With SystemPac, this is done for Your Order
you. Refer to the installation guide
to find out what work is performed. If SystemPac: SystemPac
Installation Guide

Appendix A. Installation Plan Skeleton 195

Action Start End Who does Information source
Run installation verification If ServerPac: ServerPac: Installing
programs (IVPs). Your Order

If SystemPac: SystemPac
Installation Guide
Download client code to Element-specific documentation
workstations if applicable.
Apply maintenance to target system z/OS Planning for Installation
software if necessary. (“Identifying Service Needed for the
Target System” on page 64)
Complete migration activities. “Post-IPL Migration Actions” section
of this plan
Save the customized configuration. If ServerPac: ServerPac: Using the
Installation Dialog

If SystemPac: SystemPac:
CustomPac Dialog Reference
Update the ServerPac order If ServerPac: ServerPac: Using the
inventory. Installation Dialog

If SystemPac: SystemPac:
CustomPac Dialog Reference
Back up the system. z/OS Planning for Installation
(“Appendix F. Making a Copy of
Your System Software (Cloning)” on
page 275) and local procedures.

Build and Verify the Target System (CBPDO Installation)

Action Start End Who does Information source
Review PSP buckets. IBMLink
Clone the system. z/OS Planning for Installation
(“Appendix F. Making a Copy of
Your System Software (Cloning)” on
page 275)
Update SMP/E zone entries. z/OS V1R1.0 Program Directory
Create FMIDSETs for each wave. z/OS V1R1.0 Program Directory
Install wave 0: z/OS V1R1.0 Program Directory
v Receive wave 0 elements and
service.
v Prepare to install wave 0.
v APPLY wave 0.
v Receive the rest of the CBPDO.
Install wave 1: z/OS V1R1.0 Program Directory
v Prepare to install wave 1.
v APPLY wave 1.
v Do post-APPLY work.
v Migrate and customize wave 1
elements.
v IPL and verify wave 1.
v Accept waves 0 and 1.
v Run cleanup jobs.

196 z/OS V1R1.0 Planning for Installation

Action Start End Who does Information source
Install wave 2: z/OS V1R1.0 Program Directory
v Prepare to install the wave.
v APPLY wave 2.
v Do post-APPLY work.
v Migrate and customize wave 2
elements.
v IPL and verify wave 2.
v Accept wave 2.
v Run cleanup jobs.
Install wave 3: z/OS V1R1.0 Program Directory
v Prepare to install the wave.
v APPLY wave 3.
v Do post-APPLY work.
v Migrate and customize wave 3
elements.
v Verify wave 3.
v Accept wave 3.
v Run cleanup jobs.
Download client code to Element-specific documentation
workstations if applicable.
Apply maintenance to target system z/OS Planning for Installation
software if necessary. (“Identifying Service Needed for the
Target System” on page 64)
Complete the migration. “Migration Actions” section of this
plan
Back up the system. z/OS Planning for Installation
(“Appendix F. Making a Copy of
Your System Software (Cloning)” on
page 275) and local procedures.

Build and Verify the Target System (SystemPac Full Volume Dump
Installation)
Action Start End Who does Information source
Prepare target system volumes for z/OS Planning for Installation
restore.
Review PSP buckets for latest IBMLink
installation information.
Initialize volumes. SystemPac Installation Guide
Unload the tapes to the initialized SystemPac Installation Guide
volumes.
IPL the system and log on. SystemPac Installation Guide
Run post-installation jobs after IPL. SystemPac Installation Guide
Verify installation. SystemPac Installation Guide

Appendix A. Installation Plan Skeleton 197

Customize and Test the System
Action Start End Who does Information source
Identify customization needed on z/OS Planning for Installation
the new system. (“Chapter 7. Preparing for
Customization and Test” on
page 151) and product-specific
customization guides
Complete the “Customization
Actions” section below.
Identify test activities. z/OS Planning for Installation
(“Scheduling Test Activities” on
page 160) and local test policies
and procedures
Complete the “Test Activities”
section below.
Establish a fallback strategy.
Perform customization tasks. “Customization Actions” section of
this plan
Apply remaining coexistence “Coexistence” section of this plan
service if necessary.
IPL the customized system. Local procedures
Test the customized system. “Test Activities” section of this plan
Put the system into production.

Customization Actions
Identify the software customization actions that you’ll need to perform after installing
the new software. Examples include:
v Installing additional products
v Exploiting new software features and functions
v Enabling or disabling z/OS optional features

Action For instructions, refer to...

198 z/OS V1R1.0 Planning for Installation

Action For instructions, refer to...

Test Activities
At this time, also decide how you will test the customized system and define a
fallback strategy should problems occur during testing. Examples of test activities
include:
v Starting all subsystems
v Testing operational procedures
v Testing network communication
v Testing critical applications
v Performing function and stress tests
v Running performance tests
v Checking storage usage

Test Activity Comments

Plan for Future Installations

Action Start End Who does Information source
Separate data from software. z/OS Planning for Installation
(“Separating Data from Software”
on page 164)
Place data sets on specific z/OS Planning for Installation
volumes. (“Placing Data Sets on Specific
Volumes” on page 167)

Appendix A. Installation Plan Skeleton 199

Action Start End Who does Information source
Choose a naming convention for z/OS Planning for Installation
data sets. (“Choosing a Naming Convention
for Data Sets” on page 183)
Use indirect catalog entries. z/OS Planning for Installation
(“Using Indirect Catalog Entries” on
page 184)
Use parmlib concatenation. z/OS Planning for Installation
(“Using Parmlib Concatenation
(Logical Parmlib)” on page 185)
Make optimum use of DASD space. z/OS Planning for Installation
(“DASD Space Utilization and
Performance” on page 185)

200 z/OS V1R1.0 Planning for Installation

 Appendix B. Software Requirements for z/OS Elements and
Features
The z/OS base elements represent an IPLable target system and satisfy most of
the dependencies of the z/OS elements and features. But some elements and
features require other features or IBM products that are not part of the z/OS base.
Moreover, some elements and features have optional dependencies on other
features or on IBM products that help you take full advantage of z/OS capabilities.
This appendix lists the required and the optional dependencies.

| z/OS can run as a VM guest. Requirements are:

| v z900 server: For z/OS to run as a guest of z/VM on a z900 server, z/OS and
| z/VM must operate in 64-bit mode. z/OS is not supported as a guest of VM/ESA
| when VM/ESA runs on a z900 server.
| v G5, G6, or Multiprise 3000: z/OS is supported in 31-bit mode on these servers.
| To run z/OS as a VM guest on these servers, z/VM (with z/VM operating in 31-bit
| mode) or VM/ESA V2R4 or later is required.
Notes:
1. This book does not describe program requirements related to systems in a
sysplex using the coupling facility. For that information, see the zSeries Parallel
Sysplex Customization Wizard at
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/wizards.html.
2. Requirements listed in this appendix reflect the minimum levels.
3. Some IBM products, z/OS elements, and z/OS features have comparable
non-IBM equivalents. This appendix reflects only IBM software.
Table 18. Software requirements for z/OS elements and features
Element or feature Required z/OS optional features or stand-alone products
| BCP For the latest information and service related to 64-bit real storage support, see the
| z900 PSP bucket. The PSP upgrade identifier is 2064DEVICE.

Above-16-megabyte UCB definition requirements:

v ACF/TCAM V2R4 (5735-RC3) with PTF UW16886, or ACF/TCAM V3R1 (5665-314)
with PTF UW40636, is required if you use TCAM but want to prevent TCAM’s use of
DASD devices that are defined with above-the-line UCBs.

Automatic restart manager requirements:

v System Automation for OS/390 (5645-005) is required if you want to further automate
automatic restart manager enabled programs.

Dynamic APF requirements:

v The z/OS V1R1 SecureWay Security Server feature is required if you want to use the
RACF data security monitor program (DSMON) to produce reports for APF-authorized
programs.

Job support for started tasks requirements:

v The z/OS V1R1 SecureWay Security Server feature is required if you plan to use
dynamic security control for started tasks.

| Intelligent Resource Director (IRD):

| v WLM in goal mode is required to use the IRD.

© Copyright IBM Corp. 1996, 2001 201

Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
BCP (continued) Messages displayed in non-English languages:
v The z/OS V1R1 SecureWay Security Server feature is required if you use this
function because RACF is used to obtain language information for users.

Operations log (OPERLOG) requirements:

v The z/OS V1R1 SecureWay Security Server feature is required if you want to protect
the operlog log stream.
v The z/OS V1R1 SDSF feature is required if you want to use the log browser facility
for the operlog log stream.

Parmlib concatenation requirements:

v PTF UW62475 on ACF/TCAM V2R4 (5735-RC3) is required if you use ACF/TCAM
V2R4 and want it to take advantage of the concatenated parmlib in z/OS.

Run-time library services (RTLS) requirements:

v The z/OS V1R1 SecureWay Security Server feature is required if you want to check a
user’s access to libraries that are defined to RTLS and protected by security profiles.

S/390 Fiber Channel (FICON) requirements:

v To simplify configuration definition tasks when migrating to FICON, use the z/OS
V1R1 HCM feature.
v To report on the measurement data generated for FICON CHPIDs, use the z/OS
V1R1 RMF feature.
v To exploit the architecture enhancements, use the following:
– OS/390 R6/R7 or R8 JES3 feature with the PTF to APAR OW41500; or OS/390
R9 or later JES3 feature
– IMS/ESA V6 (5655-158)
– PSF V3 for OS/390 (5655-B17)
– System Automation for OS/390 (5645-005)

TSO consoles used as extended MCS consoles:

v The z/OS V1R1 SecureWay Security Server feature is required if you want to use this
function because RACF is used to obtain console security attributes.

Workload manager (WLM) requirements:

v The z/OS V1R1 SecureWay Security Server feature is required if you want to use
DSOM support.
v CICS/ESA V4 (5685-018) is required if you want to manage CICS transactions using
response time goals or obtain detailed response time breakdowns in the RMF
Workload Activity report.
v CICSPlex System Manager (SM) V1R3 (5695-081) is required if you are using
average response time goals for CICS transactions and want CICSPlex SM to
distribute transactions to AORs based on the goals of the work.
v DB2 for MVS/ESA V4 (5695-DB2) or DB2 Server for OS/390 V5 (5655-DB2) is
required if you want to use WLM to manage parallelized DB2 queries (V4) or use
WLM to automatically start and stop server address spaces for DB2 stored
procedures (V5).
v IMS/ESA V5 (5695-176) or IMS/ESA V6 (5655-158) is required if you want to manage
IMS transactions with response time goals or want detailed response time
breakdowns in the RMF Workload Activity report.

z/OS UNIX System Services kernel requirements:

v The z/OS V1R1 SecureWay Security Server feature is required if any address space
wants to make a call to a z/OS UNIX System Services kernel service.
BDT One or both of the BDT features (BDT File-to-File or BDT SNA NJE).
BDT File-to-File None
BDT SNA NJE Any supported JES3 level.

202 z/OS V1R1.0 Planning for Installation

Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
BookManager BookServer None
BookManager BUILD Required: Document Composition Facility (DCF) R4.

Optional: To build documents using source files marked up with BookMaster tags, you
need IBM Publishing Systems BookMaster (5688-015) R4 with PTFs UQ03271 and
UQ04721.
BookManager READ The Softcopy Print element was available in OS/390 R4 through R9. To continue to use
the Softcopy Print function to print BookManager books on AFP printers, you need to
have the following products installed.

For single-byte character set printing (this includes English):

v AFP Font Collection V2R1 (5648-B33)
v BookMaster V1R4 (5688-015)
v DCF V1R4 (5748-XX9)
v PSF V3R1 for OS/390 (5655-B17) or later

For double-byte character set (DBCS) printing:

v All of the requirements for single-byte printing
v The AFP DBCS fonts for your language
v The DBCS Print Utility, formerly part of Softcopy Print but now part of BookManager
READ via the PTF for APAR PQ37518.
v BookMaster PTF UQ04721 for the DBCS profiles
C/C++ IBM Open Class None
Library
C/C++ with Debug Tool None
C/C++ without Debug Tool None

Appendix B. Software Requirements for z/OS Elements and Features 203

 Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
Communications Server IP Services has the following software requirements:
v For SNAlink LU0 support or SNAlink LU 6.2 support: ACF/NCP V6 (5688-231)
(Ethernet only) or ACF/NCP V7(5648-063) (Ethernet or Token Ring, or both)
v For NCPROUTE server: SNALINK LU0 and ACF/NCP V7R1 (5648-063) or later
v For X.25 interface support: X.25 NPSI V3R4 (5688-035) or later for 3745 or 3720, or
X.25 NPSI V2R1 (5668-719) for 3725, and the corresponding level of NCP that
supports NPSI
| v For SNMP NetView client support: NetView for MVS/ESA V3R1 (5655-007) or later,
| or Tivoli NetView for OS/390 (5697-B82)
v For file access protection for FTP: z/OS V1R1 SecureWay Security Server feature
v For FTP DB2 query: DB2 V4R1 (5695-DB2) or later
v For user-written programs in Pascal that interface to a TCP, UDP, or IP boundary:
IBM VS Pascal Compiler and Library (5668-767)
v For CICS sockets: CICS/ESA V4 (5655-018) or later
v For IMS sockets: IMS/ESA V5R1 (5695-176) or later
v For Network Print Facility support: ACF/NCP V7R1 (5648-063) or later
v For user-written programs in C that interface to an X Window System client, Remote
Procedure Call, TCP or UDP protocol boundary, DPI, IP, or z/OS UNIX feature
(Rcommands, RPC, or X Window System): z/OS V1R1 C/C++ with Debug Tool
feature or z/OS V1R1 C/C++ without Debug Tool feature
v For TCP/IP functions written in C (C sample programs, Network Database System
client and server, Network Computing System, Remote Procedure Call, non-z/OS
UNIX X Window System) or z/OS UNIX features (ONC/RPC, X Window System):
z/OS V1R1 C/C++ with Debug Tool feature or z/OS V1R1 C/C++ without Debug Tool
feature
v For SNMP OSA-Express adapter management support, OSA/SF PTF UW70624 is
required.
v If you want to use the new FTP JES support (specifying JESINTERFACELEVEL 2) in
OS/390 R10 and you are running JES2, the following PTFs are required: UW65416
on OS/390 R5-R6 JES2, UW65417 on OS/390 R7 JES2, or UW65418 on OS/390
R8-R9 JES2. If you are running JES3, the PTFs to APARs OW36022, OW34753, and
OW35435 are required.

SNA Services has the following software requirements:

v To use NetView Performance Monitor V2 (5655-043) R2, R3, or R4: the PTF for
APAR OW37396.
v To use APPC/MVS: the PTF for APAR OW30425.
v For HPR Border Node and HPR network management: Tivoli NetView for OS390
(5697-B82)
v For High Performance Routing (HPR), automatic network routing in composite
network node: NCP V7R3 (5648-063)
v To use the Performance Monitor Interface: NetView Performance Monitor V2R2
(5655-043) with PTF UW19341
v To exploit VTAM topology agent and CMIP services: NetView V3 (5655-007)
v To use Spare SDLC lines:
– NCP V7R2 (5648-063)
– NTuneMON V1R2 (5648-077) and NTuneNCP V1 (5648-089) or NTuneMON V2
(5648-141)
Communications Server One of the following:
NPF v Any supported JES2 level
v Any supported JES3 level
v NCP V7 (5648-063)
Communications Server For configuration of Communications Server Security Level 1, the z/OS V1R1
Security Level 1 SecureWay Security Server feature must be installed but does not have to be enabled.
Communications Server For configuration of Communications Server Security Level 2, the z/OS V1R1
Security Level 2 SecureWay Security Server feature must be installed but does not have to be enabled.

204 z/OS V1R1.0 Planning for Installation

Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
Communications Server To create certificates with public/private keys larger than 512 bits, the z/OS V1R1
Security Level 3 optional feature System SSL Security Level 3 must be available.
Cryptographic Services To write application programs using the DCE programming interface, you need the z/OS
V1R1 C/C++ feature.
DCE Application Support The z/OS V1R1 C/C++ feature is optional.

For Transactional RPC (TRPC), IMS/ESA V6R1 is required.

For transaction processing (without Transactional RPC), CICS/ESA or IMS/ESA is

required.
DCE Base Services To use the Global Directory Agent (GDA) portion of DCE Base Services, you need the
z/OS V1R1 SecureWay Security Server feature in order to have access to the LDAP
client function in its LDAP Server component.

To write application programs using the DCE programming interface, you need the z/OS
V1R1 C/C++ feature.
DFSMSdfp
DD limit: The IMS level required to expand the DD limit to 10 KB is IMS/ESA V6
(5655-158) or later.

Distributed FileManager (DFM/MVS) DataAgent and the DFM target server: To check
the authorization of remote systems to connect to z/OS and to access specific data
sets, the z/OS V1R1 SecureWay Security Server feature (RACF component) is required.
DFSMSdss can be used as the datamover to move data sets associated with this
function.

Object access method (OAM) Parallel Sysplex support: To use this function, DB2 for
MVS/ESA V4 (5695-DB2) or later is required.

Object access method (OAM) resource measurement facility (RMF) transaction

recording: To use this function, the z/OS V1R1 RMF feature is required.

VSAM record level sharing (RLS): To use this function, you need the z/OS V1R1
SecureWay Security Server feature (RACF component); global resource serialization
(GRS) or an equivalent function for multisystem serialization; and appropriate levels of
COBOL, PL/I, FORTRAN, and Language Environment run-time libraries for batch
applications that will use VSAM RLS data access.
DFSMSdss IMS backup-while-open support: To use this function, the Database Manager feature of
IMS/ESA V6 (5655–158) or later is required.

Snapshot and virtual concurrent copy support: To use this function, IBM Extended
Facilities Product (IXFP) V2 (5648-A17) with a minimum PTF level of L170019 is
required.

VSAM record level sharing (RLS): To use this function, you need the z/OS V1R1
SecureWay Security Server feature (RACF component); global resource serialization
(GRS) or an equivalent function for multisystem serialization; and appropriate levels of
COBOL, PL/I, FORTRAN, and Language Environment run-time libraries for batch
applications that will use VSAM RLS data access.

Appendix B. Software Requirements for z/OS Elements and Features 205

 Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
DFSMShsm Control data set (CDS) record level sharing (RLS) serialization: To use this function,
global resource serialization (GRS) or an equivalent function is required.

DFSMShsm secondary host promotion: To use this function, a cross-system coupling

facility (XCF) must be configured and running in multisystem mode.

VSAM record level sharing (RLS): To use this function, you need the z/OS V1R1
SecureWay Security Server feature (RACF component); global resource serialization
(GRS) or an equivalent function for multisystem serialization; and appropriate levels of
COBOL, PL/I, FORTRAN, and Language Environment run-time libraries for batch
applications that will use VSAM RLS data access.
DFSMSrmm None
DFSORT DFSORT’s Performance Booster for The SAS System requires enabling support from
SAS Institute Inc.

If you specify COBEXIT=COB2 on the installation macro or if you use DFSORT

LOCALE support, the Language Environment run-time library must be accessible at
execution time.
| Distributed File Service The z/OS V1R1 SecureWay Security Server feature must be operational.

| The IP Services component of the z/OS V1R1 Communications Server base element
| must be operational.

| DFS client and server support requires the z/OS V1R1 DCE Base Services base
| element to be operational.

| SMB file/print serving support requires the z/OS V1R1 DCE Base Services base
| element to be installed (but it does not have to be operational).

| SMB print serving support requires the z/OS V1R1 Infoprint Server feature to be
| operational.

| SMB password encryption requires the OCSF Base component of the z/OS V1R1
| Cryptograhic Services base element to be operational to use hardware encryption
| capabilities.

| Supported SMB clients include Windows 2000 Professional, Windows 95, Windows 98,
| Windows NT 4.0 Workstation, Windows 3.11 (Windows for Workgroups), and OS/2
| Version 4 (for file access only).
Encina Toolkit Executive None
EREP None
ESCON Director Support None
FFST None
GDDM None
GDDM-PGF None
GDDM-REXX None
HCD To migrate from a saved ESCON Manager file or from the active switch configuration or
to activate a switch configuration, ESCON Manager V1R2 with UN90108 or System
Automation for OS/390 is required.

To perform the verification/priming function of the active I/O configuration, ESCON

Manager V1R3 with PTFs UN94223 and UN94761 or System Automation for OS/390 is
required.

206 z/OS V1R1.0 Planning for Installation

Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
HCM Operating system (PWS):
v Windows 95 or later, or
v Windows NT Version 4.0 or later
Note: As of OS/390 R7, OS/2, WIN-OS/2, and Windows 3.x are no longer supported.

Host communication:
v APPC communication: PCOMM for Windows NT and Windows 95 (Version 4.11 or
later).
v TCP/IP: TCP/IP networking protocol must be installed (delivered with Windows 95
and Windows NT).
v HCM installation: A method to download the code from the host to the PWS is
required (for example, FTP or PCOMM).

If you want to use the support for Tivoli Inventory (5697-INV), you need the following:
v The HCM workstation must be made a PC Managed Node of a Tivoli Management
Region (TMR). The appropriate PC agent and the Tivoli Inventory PC Scanning
Program must be installed to make the HCM workstation a PC Managed Node.
v You need Tivoli Framework and Tivoli Inventory Version 3.2. The following patches
must be installed: 3.2-TMP-0023 and 3.2-INV-0001.
HLASM None
HLASM Toolkit None
IBM HTTP Server A Web browser must be installed on a networked workstation.

Communications Server IP connectivity must be established.

IBM HTTP Server NA None
Secure
ICKDSF None

Appendix B. Software Requirements for z/OS Elements and Features 207

 Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
| ILM ILM will be initially delivered on 30 March 2001 (as part of z/OS V1R1) for
| preproduction use, with Workload License Charges at full machine capacity. Customer
| production use of ILM, with Workload License Charges at less than full machine
| capacity, will be available when IBM completes full testing of ILM and you have applied
| the recommended z/OS service to make your system ILM production-ready. This testing
| by IBM is planned to be complete by the end of September 2001. The software
| requirements in this table apply to both the preproduction and production use of ILM.
| Information about the service required to make ILM production-ready can be found at
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/.

| Both the z/OS image running the license server and all z/OS images running the
| application agent have the following requirements:
| v To enable Workload License Charges, z/OS must run in 64-bit (z/Architecture) mode.
| v z/OS UNIX kernel services must operate in full function mode.
| v The Communications Server base element must be configured for the ILM application
| agent, ILM license server, and ILM management tool. An IP connection is required
| between the license server and application agents. An FTP connection is required
| between the management tool and IBM.
| v The OCSF Base component of the z/OS V1R1 Cryptographic Services base element
| must be configured.
| v The z/OS V1R1 SecureWay Security Server feature is required so that RACF can
| protect resources and grant access to them.

| In addition, the z/OS image running the license server must be at least a base sysplex
| configuration with DASD-only log streams configured. An SMS environment for the log
| streams is highly recommended.

| The management tool on the workstation requires Windows NT or Windows 2000. Also,
| FTP connectivity between the workstation and the license server, which runs on z/OS, is
| recommended but not required. The reconciliation message FTP to IBM can occur from
| any computer that has access to the reconciliation message prepared by the
| management tool on the workstation or on the host.

208 z/OS V1R1.0 Planning for Installation

 Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
Infoprint Server The z/OS V1R1 SecureWay Security Server feature is required.

To print output from Infoprint Server using AFP printers, PSF V3 for OS/390 (5655-B17)
is required. If you want PSF to exploit the Printer Inventory Manager and SNMP
Subagent components of Infoprint Server, and you’re using R1 of PSF V3, PTF
UW64475 is required.

If you want to use the IPP server function of Infoprint Server, Java for OS/390
(5655-A46) at JDK level 1.1.8 or later is required.

Infoprint Server Transforms for OS/390 (5697-F51) can be used with the Transform
Manager component of Infoprint Server to perform data stream conversion:
v They can convert PCL, PostScript, PDF, or SAP print data to AFP format for printing
by PSF V3 for OS/390 (5655-B17).
v They can convert AFP data streams to PCL, PostScript, or PDF print data.

| To print on printers controlled by z/OS V1R1 Communications Server SNA Services, the
| Coax Printer Support feature of the Infoprint Server Transforms product (5697-F51) is
| required.

The Infoprint Server SNMP Subagent requires IBM Network Printer Manager for the
Web. You can download Network Printer Manager for the Web from the IBM Printing
Systems home page:
http://www.ibm.com/printers

The Network Printer Manager for the Web server requires the following software on a
Windows NT workstation or server:
v Windows NT Version 3.51 or Version 4.0, with TCP/IP protocol network software
installed
v A Web server running under Windows NT
v Java Virtual Machine software Version 1.1

The administrator GUI provided by Network Printer Manager for the Web can run on the
same or different system as the Network Printer Manager for the Web server and
requires a Java 1.1 enabled Web browser. The browser can be either Netscape
Communicator 4.04 (or later) or Microsoft Internet Explorer 4.0 (or later).

Appendix B. Software Requirements for z/OS Elements and Features 209

 Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
ISPF To use ISPF’s Software Configuration and Library Manager (SCLM), the z/OS V1R1
SecureWay Security Server feature is recommended, but not required, to ensure data
integrity.

To use ISPF’s Library Management Facility (LMF):

v The z/OS V1R1 DFSORT feature is required.
v The z/OS V1R1 SecureWay Security Server feature is recommended for maintaining
LMF data integrity

ISPF Client/Server runs on a variety of workstation environments and connects with a

variety of TCP/IP and APPC communication products:
v For APPC environments, ISPF Client/Server runs on IBM OS/2 Warp 3.0 or later (or
OS/2 Warp V4 J or later for DBCS support) with IBM Communications Manager/2
V1.11 or Communications Server OS/2 Access Feature V4.1.
v For TCP/IP communication, ISPF Client/Server requires the IP Services component
of Communications Server on the host and one of the following operating systems on
the workstation, using the TCP/IP included in the workstation operating system:
– IBM OS/2 Warp Connect V3 or OS/2 Warp V4 J or later for DBCS support
– Windows NT 4.0
– Windows 95
– Windows 98
– Windows 2000
– IBM AIX V4.1.5 with X11R5 Motif V1.2
– HP/UX V9.03 or later with X11R5 Motif V1.2
– Solaris V 2.5.1 with X11R5 Motif V1.2
JES2 To monitor and control jobs, output, devices, and system resources from TSO/E, you
need the z/OS V1R1 SDSF feature.

To use Advanced Function Presentation, you need PSF V3 for OS/390 (5655-B17).
JES3 To report correct JMF data for devices that have 4-digit device numbers, SLR V3R3.1
(5665-397) with PTF UN68145 is required.

To monitor JES3 activity, z/OS V1R1 RMF is required.

To report correct JMF data, the following are required:

v SLR V3R3.1 (5665-397)
v EPDM/MVS V1R2 (5695-101)

To use Advanced Function Presentation, you need PSF V3 for OS/390 (5655-B17).
| LAN Server LAN Server is being removed from z/OS because the prerequisite OS/2 software is no
| longer available. OS/390 R9 was the last release to include both the workstation (on
| diskettes) and host components. OS/390 R10 and z/OS V1R1 have only the host
| component. After z/OS V1R1, neither component will be available. For customers who
| want to migrate to z/OS V1R1 prior to migrating off LAN Server, the OS/2 Front End
| Processor configurations from previous releases of LAN Server are still supported on
| z/OS V1R1. See S/390 File and Print Serving, SG24-5330, for alternative solutions and
| migration guidance.

210 z/OS V1R1.0 Planning for Installation

 Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
| Language Environment If you plan to use CICS/ESA V4 (5655-018) or CICS Transaction Server (TS) for
| OS/390 V1 (5655-147), install the following PTFs or else Language Environment will fail
| to initialize:
| v On CICS/ESA V4R1, install PTFs:
| – UQ43781 (Language Environment initialization)
| – UQ51747 (transaction dump processing)
| v On CICS TS V1R2, install PTFs:
| – UQ43784 (Language Environment initialization)
| – UQ51836 (transaction dump processing)
| v On CICS TS V1R3, install PTFs:
| – UQ43786 (Language Environment initialization)
| – UQ51840 (transaction dump processing)
| – UQ47893 and UQ51885 (AUTODST parameter)
LANRES LANRES requires one of the following on the NetWare server:
v NetWare V3.12J from IBM
v NetWare V4.1J from IBM
| v Novell NetWare V3.2
| v Novell NetWare V4.11/V4.2
| v Novell NetWare V5.x

To use NetWare Network File System client support, you need one of the following on
the server:
v When using NetWare V3.12: NetWare Network File System V1.1 or later
v When using NetWare 3.12J: NetWare Network File System v1.2J from IBM (Version
1.2C)
Note: Versions prior to V1.2C are not supported. If you have a version prior to
V1.2C, contact IBM Japan for an update kit.
v When using NetWare V4.x: NetWare Network File System V1.2B, with patch
NFS153.EXE

To use NetWare for SAA Channel Driver Connection and SNA LU 6.2 Connection, you
need one of the following on the NetWare server:
v NetWare V3.2 or NetWare V4.x with Novell NetWare for SAA V2.0 or V2.2.
v NetWare 3.12J with NetWare for SAA V2.0 from IBM (Japanese Version).
Notes:
1. If you are using NetWare for SAA V2.0, you will need fixes SAA016.EXE and
SAA017.EXE.
2. Product numbers vary based on the number of sessions installed on the NetWare
server. For more information, see the Novell NetWare product documentation.
| 3. There is limited support for NetWare for SAA V3.0. There is no planned support for
| NetWare for SAA V4.0 and V5.0.

MICR/OCR None

Appendix B. Software Requirements for z/OS Elements and Features 211

 Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
| msys for Setup The msys for Setup environment contains the following parts:
| v A workstation for the msys workplace running Windows NT 4.0 with fixpack 4 or later.
| TCP/IP must be configured and active.
| v An OS/390 or z/OS LDAP server. The LDAP server can be on a separate OS/390 or
| z/OS image or on the msys driving or target system. The msys workplace and the
| msys driving system need to have a TCP/IP connection to the LDAP server. If you
| have a DB2 system, you may want to consider running the LDAP server on that
| system. The LDAP server requires:
| – OS/390 R8 or later, or z/OS. Note that the LDAP Server component in OS/390
| and z/OS is packaged as part of the SecureWay Security Server optional feature
| but is licensed with the base operating system and can be used without enabling
| the SecureWay Security Server feature.
| – DB2 Server for OS/390 V5 (5655-DB2) with PTF UQ16836, or DB2 Universal
| Database Server for OS/390 V6 (5645-DB2) with PTF UW41616.
| – Approximately 300 MB of DB2 backend storage for the management directory on
| the LDAP system.
| – The use of the TDBM backend of LDAP, as provided in OS/390 R10 or z/OS
| V1R1. The LDAP server provides (via PTF) automated setup scripts for the TDBM
| backend that greatly facilitate the setup of the z/OS management directory as
| needed by msys. If the LDAP server is used exclusively for the z/OS management
| directory, the TDBM backend can also be used on an OS/390 R8 or R9 system, if
| this system can access the OS/390 R10 LDAP server code libraries. If you intend
| to add non-msys directory data to the LDAP server, you must run the LDAP server
| with TDBM on an OS/390 R10 or later system. If TDBM is used with an OS/390
| R8 or R9 system, the following LDAP server functions are not available: SSL
| communications and password encryption support.
| v An msys driving system (the system on which msys runs), which requires:
| – OS/390 R8 or later, or z/OS
| – Java for OS/390 (5655-A46) at JDK level 1.1.8 with PTF UW72477, or Developer
| Kit for OS/390, Java 2 Technology Edition (5655-D35) at JDK level 1.3.0

| If the msys driving system is not a z/OS system, at least one of the msys target
| systems that are to be included in a Parallel Sysplex configuration must be running
| z/OS, the HFS containing the msys code on the msys target system must be
| mountable from the msys driving system, and the z/OS target libraries must be
| accessible from the msys driving system.
| v An msys target system (the system that is configured using msys). For a Parallel
| Sysplex configuration, it requires OS/390 R8 with PTF UW63195 or later, or z/OS.

| The msys driving system and the msys target system can be the same OS/390 or z/OS
| image, or two separate images. If they are two separate images, they must share DASD
| for parmlib and couple data set creation. If RACF is used as security manager, they
| must have a shared RACF security database.

| The environment described above requires at least one z/OS system as msys driving
| system, msys target system, or both. If the z/OS system was not installed using
| ServerPac or SystemPac, it must have been upgraded from one of the following:
| v An OS/390 R10 system that was installed using ServerPac or SystemPac and then
| upgraded to z/OS using the z/OS V1R1 Upgrade Package for OS/390 V2R10
| v An OS/390 R9 system that was installed using ServerPac or SystemPac, then
| upgraded to OS/390 R10 via CBPDO, and then upgraded to z/OS using the z/OS
| V1R1 Upgrade Package for OS/390 V2R10
| The ServerPac or SystemPac driving system (not to be confused with the msys driving
| system) must have DFSORT or an equivalent sort program installed.

212 z/OS V1R1.0 Planning for Installation

Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
Network File System Network File System Client and Network File System Server both require:
v z/OS V1R1 Communications Server - IP Services
v z/OS V1R1 SecureWay Security Server feature
OCSF Security Level 3 To write application programs using the DCE programming interface, you need the z/OS
V1R1 C/C++ feature.
OSA/SF To meet the SAF of the host operating system on which OSA/SF is running, the z/OS
V1R1 SecureWay Security Server feature is required.

To handle alerts that OSA reports when the SNA mode is active on an OSA and issue
OSA/SF for MVS commands from NetView, NetView for MVS/ESA 1.3 (5685-152) is
required.

ESCON Manager 1.3 (5688-008) Workstation feature with PTF UN75973 is required to
view OSA channel and device status. ESCON Manager commands can reconfigure an
OSA channel path and vary an OSA device

The z/OS V1R1 RMF feature is required to obtain resource utilization data about OSA
channels.

To access OSA/SF at a workstation, use:

v Microsoft Windows 95 4.00.950B (OSR2) or later, or Microsoft Windows NT 4.0 with
Service Pack 3 or later, or
v OS/2 Warp Version 4.0 with fixpack 6 or later

The OSA/SF GUI for Windows is shipped in a self-extracting file. The OSA/SF GUI for
OS/2 comes in a standard OS/2 installation package.

To establish GUI-to-server communication, one of the following is required:

v For TCP/IP workstation-to-server communication: IP Services component of z/OS
V1R1 Communications Server
v For APPC workstation-to-server communication: Personal Communications/3270
Version 4 Release 2 (with the PTF for APAR IC22680) or later, and SNA Services
component of z/OS V1R1 Communications Server
v For SNA workstation-to-server communication: Personal Communications/3270
Version 4 Release 2 (with the PTF for APAR IC22680) or later, and EHLLAPI (3270)
— SNA Services component of z/OS V1R1 Communications Server

Appendix B. Software Requirements for z/OS Elements and Features 213

 Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
RMF For Monitor II local session, BTAM/SP (5665-279) is required.

The RMF Spreadsheet Reporter requires the following software:

v Operating System
– Windows 95
– Windows NT Version 4
v Spreadsheet Program
You can use any spreadsheet program that can read Lotus files with an extension of
WK1. However, in order to be able to run the supported examples without any
difficulties, one of the following products can be used:
– Lotus 1-2-3 Version 5 (International English Version)
– Microsoft Excel Version 5 or later

Using Performance Monitoring of OS/390 requires:

v Windows or OS/2. If Windows, Windows 95, Windows 98, or Windows NT with
Service Pack 3. If OS/2, OS/2 V4 with Java at JDK level 1.1.8 or later.
v If Windows, Direct Draw 5.0 or later.
v Netscape Navigator 4.6 or later, or Microsoft Internet Explorer 5.0 or later.

| The RMF Client/Server requires the following software:

| v Host software: a z/OS V1R1 Communications Server network connection from the
| workstation to the host. If APPC is used, the connection must be capable of
| supporting parallel LU 6.2 sessions.
| v Workstation software: any operating system that supports the z/OS V1R1 ISPF
| Client/Server.
SDSF To use the SAF security feature of SDSF, the z/OS V1R1 SecureWay Security feature is
required.

The z/OS V1R1 RMF feature is required to:

v Use the RMF support provided by the DA display
v View sysplex wide data on the DA display
v View both the MVS and LPAR view of CPU use on the DA display

To display printer intervention conditions, PSF V3R1 for OS/390 (5655-B17) is required.

For sysplex-wide data on the PR and INIT displays, and for sysplex support in browse,
MQSeries for OS/390 V2 (5655-A95) is required.
SecureWay Security Server If the LDAP Server component will be used as a general LDAP directory server, DB2 is
required; use DB2 V5 with PTF UQ16836 or DB2 V6 with PTF UW41616. If the LDAP
Server component will be used only to provide LDAP access to USER and GROUP
profiles stored in RACF, or only to provide LDAP access to configuration data stored in
an IODF via HCD, DB2 is not required.

To run the RACF remove ID utility (IRRRID00) or the RACF report writer, the z/OS
DFSORT feature is required.

For enhanced IP security (packet filtering, tunnels, and NAT), the Firewall Technologies
component requires the z/OS V1R1 Communications Server Security Level 3 feature.

To write application programs using the Kerberos or GSS-API programming interface,

you need the z/OS V1R1 C/C++ with Debug Tool or z/OS V1R1 C/C++ without Debug
Tool feature.
SMP/E None

214 z/OS V1R1.0 Planning for Installation

Table 18. Software requirements for z/OS elements and features (continued)
Element or feature Required z/OS optional features or stand-alone products
SOMobjects ADE For an application that is written in C/MVS or C++/MVS, the z/OS V1R1 C++ feature is
required.

For an application that is written in object-oriented COBOL:

v IBM COBOL for OS/390 & VM V2 (5648-A25)

For an application running in the IMS environment:

v IMS/ESA V5 (5695-176)

For an application running in the CICS environment:

v CICS/ESA V4 (5655-018)

To run the installation verification programs GOS1IVP and GOS1IVPP, you must have
z/OS V1R1 C/C++ installed and enabled.
SOMobjects RTL Optional:
v z/OS V1R1 SOMobjects ADE feature
v z/OS V1R1 SecureWay Security Server feature
v DB2 V4R1 (5695-DB2) or later
v Query Management Facility V3R1.1 (5706-254) or later

To run the installation verification programs GOS0IVP and GOTIVPJ, you must have
z/OS V1R1 C/C++ installed and enabled.
System SSL Security Level To write application programs using the DCE programming interface, you need the z/OS
3 V1R1 C/C++ feature.
Text Search None
TIOC None
Tivoli Management None
Framework
TSO/E To access terminals using TCAM, ACF/TCAM V2R4 (5735-RC3) is required.

For language support service or for TSO/E to save the user’s console command profile,
the z/OS V1R1 SecureWay Security Server feature is required.

To use security labels in TSO/E, the following are required:

v z/OS V1R1 SecureWay Security Server feature
v PSF V3 for OS/390 (5655-B17).
z/OS UNIX System To write application programs using the C or C++ language application programming
Services interface, you need the z/OS V1R1 C/C++ feature.

To run reports to audit z/OS UNIX System Services, you need SLR V3R3 (5665-397)
with PTF UN25722.
3270 PC File Transfer Compatible 3270 terminal emulation software, such as IBM Personal
Program Communications/3270 and IBM Communications Manager/2, is required.

Any supported ACF/TCAM is optional.

Appendix B. Software Requirements for z/OS Elements and Features 215

216 z/OS V1R1.0 Planning for Installation
 Appendix C. Minimum Levels of IBM Software Products That
Run with z/OS
This appendix lists the minimum (earliest) levels of IBM stand-alone software
products (licensed programs) that run with z/OS. Check the list for products
installed on your target system. For these products, you must migrate to at least the
levels shown so that they can run on z/OS V1R1. Note that, although some of the
products or levels are no longer marketed, all are still being serviced.

For further reference:

v To find out the levels of products that you currently have on your system, use the
SMP/E Planning and Migration Assistant.
v To find the current versions and releases of products, check the Preventive
Service Planning (PSP) facility of the IBM Customer Support Center.
v Products that are no longer marketed are not available through ServerPac. If you
have any of these products, see “Separating Data from Software” on page 164
for information about ways to avoid having to reinstall them after installation of a
ServerPac order.
Table 19. Minimum levels of products that run with z/OS V1R1
Product (and product number) Minimum release
4700 FCS Controller Resource Manager V2 (5668-753) R4.5
4700 Host Support Program V1 (5668-989) R9.6
ACF/NCP V4 (5668-854) R3.1
ACF/NCP V5 (5668-738) R4
ACF/NCP V6 (5688-231) R3
ACF/NCP V7 (5648-063) R3
ACF/SSP V3 (5665-338) R9
ACF/SSP V4 (5655-041) R2
ACF/TCAM V2 (5735-RC3) R4
ACF/TCAM V3 (5665-314) R1
AD/Cycle C/370 V1 (5688-216) R2
Note: To find out if your C programs need to be re-link edited with
Language Environment, see z/OS Language Environment
Run-Time Migration Guide and z/OS C/C++ Compiler and
Run-Time Migration Guide.
AD/Cycle Dictionary Services/MVS V1 (5695-056) R2
AFP Century Schoolbook Font V1 (5771-ADJ) R1
AFP Font Collection V1 (5648-113) R1
AFP Font Collection V2 (5648-B33) R1
AFP Math and Science Font V1 (5771-ADT) R1
| AFP Toolbox for MVS V1 (5655-A25) R1 with PTF UQ11500
APL2 Fonts V1 (5771-ADB) R1.2
APL2 V2 (5688-228) R2 with PTFs
UN80106, UN96394,
UQ05988, UQ32641,
UQ38044, UQ40048,
and UQ40996

© Copyright IBM Corp. 1996, 2001 217

 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
APL2 Application Environment V2 (5688-229) R2 with PTFs
UN80106, UN96394,
UQ32641, UQ38044,
UQ40048 and
UQ40996
Application Map Generator for 4700 Finance Communication R3.1
System V1 (5668-934)
Application Support Facility V3 (5655-002) R2
Application Test Collection V2 (5655-B97) R1
Batchpipes for OS/390 V2 (5655-D45) R1
BookManager BookServer for World Wide Web for MVS/ESA V2R2 z/OS V1R1
(5655-A20) BookManager
Note: 5655-A20 is the stand-alone product. In z/OS, use the base BookServer element
element BookManager BookServer.
BookManager BUILD/MVS V1 (5695-045) z/OS V1R1
Note: 5695-045 is the stand-alone product. In z/OS, use the BookManager BUILD
optional feature BookManager BUILD. feature
BookManager READ/MVS V1 (5695-046) z/OS V1R1
Note: 5695-046 is the stand-alone product. In z/OS, use the base BookManager READ
element BookManager READ. element
| Breeze for Software Configuration and Library Manager (SCLM) for R1
| OS/390 V1 (5697-G58)
BTAM/SP (Basic Telecommunication Access Method/SP) V1 R1
(5665-279)
BTLS (Basic Tape Library Support) V1 (5655-056) R6
C/370 Compiler V2 (5688-187) R1
Note: To find out if your C programs need to be re-link edited with
Language Environment, see z/OS Language Environment
Run-Time Migration Guide and z/OS C/C++ Compiler and
Run-Time Migration Guide.
C/370 Library V2 (5688-188) R2
Note: To find out if your C programs need to be re-link edited with
Language Environment, see z/OS Language Environment
Run-Time Migration Guide and z/OS C/C++ Compiler and
Run-Time Migration Guide.
C/C++ Productivity Tools V1 (5655-B85) R1
| CallPath/CICS for OS/390 V2 (5655-B34) R1
| Note: This product was formerly named Corepoint Telephony for
| OS/390.
CCCA (COBOL and CICS Command Level Conversion Aid) for R1
OS/390 & MVS & VM V2 (5648-B05)
CICS Application Migration Aid V1 (5695-061) R1
CICS Transaction Affinities Utility MVS/ESA V1 (5696-582) R1
| CICS TS (Transaction Server) for OS/390 V1 (5655-147) R1 with PTF
| Note: The ILM enablement PTF enables variable Workload UQ19747 and an ILM
| License Charges and can be found at enablement PTF
http://www.ibm.com/servers/eserver/zseries/zos/ilm/. The other PTF
is necessary for the successful operation of the CICS Web Interface
(CWI).

218 z/OS V1R1.0 Planning for Installation

 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
CICS VSAM Recovery MVS/ESA V2 (5695-010) R3
| CICS/ESA V4 (5655-018) R1 with PTFs
| Note: The ILM enablement PTF enables variable Workload UQ23910, UQ28415,
| License Charges and can be found at UW43781, and an ILM
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/. enablement PTF
CICSPlex SM (System Manager) V1 (5695-081) R2
| Cloud 9 for Software Configuration and Library Manager (SCLM) for R1
| OS/390 V1 (5697-G57)
COBOL for MVS & VM V1 (5688-197) R2
Note: To find out if your OS/VS COBOL or VS COBOL II compiled
and link-edited programs need to be recompiled with this compiler
or re-link edited with Language Environment, see COBOL for
OS/390 & VM and COBOL for MVS & VM Compiler and Run-Time
Migration Guide.
| COBOL for OS/390 & VM V2 (5648-A25) R1 with an ILM
| Note: To find out if your OS/VS COBOL or VS COBOL II compiled enablement PTF
and link-edited programs need to be recompiled with this compiler
or re-link edited with Language Environment, see COBOL for
OS/390 & VM and COBOL for MVS & VM Compiler and Run-Time
Migration Guide. The ILM enablement PTF enables variable
Workload License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
COBOL Report Writer Library V1 (5798-DZX), COBOL Report R4
Writer Precompiler and Libraries V1 (5798-DYR)
COBOL Structuring Facility V3 (5696-737) R1
CODE/370 (CoOperative Development Environment/370) V1 R2
(5688-194)
Content Manager OnDemand for OS/390 V2 (5655-A88) R1
CPCS (Check Processing Control System) V1 (5734-F11) R11
| CSFI (Communications Subsystem for Interconnection) V1 R3
(5688-132)
CSP/370AD (Cross System Product/370 Application Development) R1
V4 (5688-218)
CSP/370RS (Cross System Product/370 Runtime Services) V2 R1
(5688-206)
Data1 Fonts V1 (5771-ADA) R1.2
DataInterchange MVS and DataInterchange MVS/CICS V3 R1
(5655-B29 and 5655-B30)
| DataRefresher V1 (5696-703) R1
Data Stream Tuner for IMS/ESA V1 (5697-D69) R1
DB2 Administration Tool for MVS/ESA V1 (5688-515) R2
| DB2 Administration Tool for MVS/ESA V2 (5655-D52) R1
| DB2 Administration Tools V2 (5655-E70) R1
| DB2 Automated Utility Generator V1 (5695-077) R3
| DB2 Bind Manager V1 (5655-D38) R1
DB2 Buffer Pool Tool V1 (5697-D16) R1
| DB2 DataPropagator V7 (5655-E60) R1

Appendix C. Minimum Levels of IBM Software Products That Run with z/OS 219
 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
DB2 Forms for OS/390 V1 (5697-F09) R1
DB2 High Performance Unload V1 (5697-F44) R1
| DB2 High Performance Unload V1 (5655-E69) R1
DB2 Intelligent Miner for Data for OS/390 V6 (5655-IM3) R1
| DB2 Log Analysis Tool V1 (5655-E66) R1
| DB2 Object Restore V1 (5655-E72) R1
DB2 OLAP Server for OS/390 V1 (5640-OLP) R1
DB2 PM (Performance Monitor) for MVS V4 (5655-102) R1
| DB2 PM (Performance Monitor) for OS/390 V7 (5655-E61) R1
| DB2 Query Monitor for OS/390 V1 (5655-E67) R1
| DB2 Recovery Manager V1 (5697-F56) R1
DB2 Row Archive Manager for OS/390 V1 (5655-A31) R1
| DB2 Row Archive Manager V1 (5655-E65) R1
| DB2 SQL Performance Analyzer for OS/390 V1 (5697-F57) R1
| DB2 for MVS/ESA V4 (5695-DB2) R1 with PTFs
| Note: The ILM enablement PTF enables variable Workload UQ44086, UQ47202,
| License Charges and can be found at and an ILM
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/. enablement PTF
| DB2 Server for OS/390 V5 (5655-DB2) R1 with PTFs
| Note: The ILM enablement PTF enables variable Workload UQ44087, UQ47203,
| License Charges and can be found at and an ILM
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/. enablement PTF
| DB2 Universal Database Server for OS/390 V6 (5645-DB2) R1 with PTFs
| Note: The ILM enablement PTF enables variable Workload UQ34023, UQ42540,
| License Charges and can be found at UQ44088, and an ILM
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/. There is also enablement PTF
an ILM enablement PTF for the QMF feature.
| DB2 Universal Database Server for OS/390 V7 (5675-DB2) R1 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/. There is also
an ILM enablement PTF for the QMF feature.
DBICF (Data Base Integrity Control Facility) V6 (5697-B92) R1
DCF (Document Composition Facility) V1 (5748-XX9) R4 with PTFs
UN92385 and
UN92386
| Developer Kit for OS/390, Java 2 Technology Edition V1 SDK level 1.3.0 with
| (5655-D35) the PTF for APAR
| PQ42468
DFSMS/MVS V1 (5695-DF1) z/OS V1R1
Note: 5695-DF1 is the stand-alone product. In z/OS, use the base DFSMSdfp element
element DFSMSdfp and optional features DFSMSdss, DFSMShsm, and DFSMSdss,
and DFSMSrmm. DFSMShsm, and
DFSMSrmm features
DFSMS Optimizer for OS/390 and MVS/ESA V1 (5655-OPT) R2

220 z/OS V1R1.0 Planning for Installation

 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
DFSORT V1 (5740-SM1) z/OS V1R1 DFSORT
Note: 5740-SM1 is the stand-alone product. In z/OS, use the feature
optional feature DFSORT.
DISOSS/370 V3 (5665-290) R4
DISOSS Library Services - Extended (DLSE) V3 (5787-EDJ) R1.2
DisplayWrite/370 V2 (5685-101) R2
| DITTO/ESA for MVS V1 (5655-103) R3
Domino Go Webserver 4.6.1 for OS/390 (5697-C58), Domino Go z/OS V1R1 IBM HTTP
Webserver 5.0 for OS/390 (5697-D43) Server element
Note: 5697-C58 and 5697-D43 are the stand-alone products. In
z/OS, use the base element IBM HTTP Server.
Dynamic Resource Control (DRC) Facility for IMS/ESA V1 R1
(5697-D14)
Emulation Program V1 (5735-XXB) R4
eNetwork Host On-Demand for OS/390 V2 (5655-A81) 0.0
eNetwork Host On-Demand V3 (part number 31L2157, 31L2158, or 0.4
31L2159; order type number 5648-B40)
| ESCON Manager V1 (5688-008) R3 with PTF UN66946
Note: ESCON Manager is included in System Automation for
OS/390 (5645-005). The PTF provides support for the 9032-3
ESCON Director.
Extended Terminal Options Support for IMS/ESA (ETO Support) V1 R1
(5697-D68)
| Fault Analyzer for OS/390 V1 (5697-F19) R1
File Exchange/MVS User Interface V1 (5785-EEX) R3
| File Manager for OS/390 V1 (5697-F20) R1
Fortran. See z/OS Language Environment Run-Time Migration
Guide .
GAM/SP (Graphics Access Method/SP) V1 (5668-978) R3.1 with PTFs for
APAR II10939
GDDM/GKS V1 (5668-802) R1.3
GDDM/IMD V2 (5668-801) R1.3
GDDM/IVU V1 (5668-723) R1.3
GDDM-PGF V2 (5668-812) z/OS V1R1
Note: 5668-812 is the stand-alone product. In z/OS, use the GDDM-PGF feature
optional feature GDDM-PGF.
GDDM V3 (5695-167) z/OS V1R1 GDDM
Note: 5695-167 is the stand-alone product. In z/OS, use the base element
element GDDM.
GDQF (Graphical Display and Query Facility) V2 (5688-169) R2
geoManager V1 (5685-105) R1.6
| HCF (Host Command Facility) V2 (5668-985) R1
HLASM for MVS & VM & VSE V1 (5696-234) and HLASM Toolkit z/OS V1R1 HLASM
feature element, z/OS V1R1
Note: 5696-234 is the stand-alone product. In z/OS, use the base HLASM Toolkit feature
element HLASM and the optional feature HLASM Toolkit.

Appendix C. Minimum Levels of IBM Software Products That Run with z/OS 221
 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
ICSF/MVS (Integrated Cryptographic Service Facility/MVS) V2 z/OS V1R1
(5655-120) Cryptographic
Note: 5655-120 is the stand-alone product. In z/OS, use the Services element
exclusive base element Cryptographic Services.
ICSS (Internet Connection Secure Server) for OS/390 V2 z/OS V1R1 IBM HTTP
(5697-B14) Server element
Note: ICSS was a nonexclusive base element of OS/390 in R3 and
R4. As of OS/390 R9, it is the exclusive base element known as
IBM HTTP Server. In between, it was known as Lotus Domino Go
Webserver and WebSphere Application Server.
IGES Processor V3 (5648-001) R1.2
ImagePlus Folder Application Facility (IPFAF) MVS/ESA V2 R2
(5695-041)
ImagePlus Folder Application Facility (IPFAF) V3 (IPFAF) R1
(5655-A27)
ImagePlus Object Distribution Manager (IODM) MVS/ESA V2 R2
(5695-042)
ImagePlus Object Distribution Manager (IODM) V3 (5655-A26) R1
IMS/ESA Ad-Hoc Reporting Tool (Ad-Hoc Tool) V1 (5697-A05) R1
IMS/ESA ADF Tool Pak for MVS V1 (5655-A21) R1
IMS/ESA BTS (Batch Terminal Simulator) V2 (5655-A14) R1
IMS/ESA Database Control Suite for OS/390 V1 (5697-D15) R1
IMS/ESA DBRC (DataBase Recovery Control) Security Tool V1 R1
(5697-D87)
IMS/ESA DEDB (Data Entry Databases) Fast Recovery V1 R1
(5655-109)
IMS/ESA Index Builder for MVS/ESA V1 (5697-C33) R1
IMS/ESA Message Requeuer (IMS MRQ) for MVS/ESA V3 R1
(5655-136)
IMS/ESA Partition Support Product for MVS/ESA (Partition DB) V1 R1
(5697-A06)
IMS/ESA Partition Support Product for MVS/ESA (Partition DB) V2 R1
(5697-D85)
IMS/ESA Performance Analyzer for MVS/ESA V1 (5697-B89) R2
IMS/ESA Recovery Saver for MVS/ESA V1 (5655-A68) R1
IMS/ESA Year 2000 Exit Tool V1 (5697-E04) R1
| IMS/ESA V5 (5695-176) R1 with PTFs
| Note: The ILM enablement PTF enables variable Workload UQ48302, UQ48818,
| License Charges and can be found at and an ILM
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/. enablement PTF
| IMS/ESA V6 (5655-158) R1 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
| IMS V7 (5655-B01) R1 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.

222 z/OS V1R1.0 Planning for Installation

 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
| IMS Advanced ACB Generator V1 (5655-E05) R1
IMS Compression - Extended V1 (5655-085) R2
| IMS Connect V1 (5655-E51) R1
| IMS Data Base Integrity Control Facility V7 (5697-F61) R1
| IMS DataPropagator V2 (5696-705) R2
| IMS ETO (Extended Terminal Option) Support V2 (5655-E12) R1
| IMS Data Base Integrity Control Facility V7 (5697-F61) R1
| IMS Database Repair Facility V1 (5655-E03) R1
| IMS Fast Path Basic Tools V1 (5655-E30) R1
| IMS Fast Path Online Tools V1 (5655-E31) R1
| IMS Hardware Data Compression - Extended V2 (5655-E02) R1
| IMS High Performance Load V1 (5655-E07) R1
| IMS High Performance Pointer Checker V1 (5655-E09) R1
| IMS High Performance Prefix Resolution V1 (5655-E08) R1
| IMS High Performance Upload V1 (5655-E06) R1
| IMS Image Copy Extensions V1 (5655-E10) R1
| IMS Index Builder V2 (5655-E24) R1
| IMS Library Management Utilities V1 (5655-E04) R1
IMS PA (Performance Analyzer) V2 (5697-F02) R1
IMS Parallel Change Accumulation for IMS/ESA V1 (5697-E32) R1
| IMS Performance Analyzer for OS/390 V3 (5655-E15) R1
| IMS Program Restart Facility V2 (5655-E14) R1
| IMS Queue Control Facility for OS/390 V1 (5697-E99) R1
| IMS Recovery Saver V2 (5655-E16) R1
| IMS Sequential Randomizer Generator V1 (5655-E11) R1
IMS System Utilities/Data Base Tools (DBT) V2 (5685-093) R3
| Infoprint Server Transforms for OS/390 V1 (5697-F51) R1.1 with PTFs
| Note: The PTFs are necessary for enablement checking to function UW74473, UW74487,
| correctly on z/OS. You need not install all the PTFs; install only UW74488, UW74489,
| those that correspond to the features of Infoprint Server Transforms UW74490
| that you are using.
Item Capture Support (ICS) for MVS/ESA and OS/390 V1 R1
(5655-B23)
IXFP (IBM Extended Facilities Product) V2 (5648-A17) R1
| Java for OS/390 V1 (5655-A46) JDK level 1.1.8 with
| PTF UW72477
JES/328X Print Facility V3 (5785-BAZ) R2
| Lotus Domino for S/390 V5 (5655-B86) R5.0.7
MERVA CICS for MVS/ESA V3 (5655-039) R3
MERVA ESA Components V4 (5648-B30) R1
MERVA ESA V4 (5648–B29) R1
MERVA Extended Connectivity for MVS/ESA V3 (5655-110) R2

Appendix C. Minimum Levels of IBM Software Products That Run with z/OS 223
 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
MERVA IMS for MVS/ESA V3 (5655-040) R3
Millenium Runtime Windowing Tool for MVS and OS/390 V1 R1
(5697-E07)
MPSX/370 (Mathematical Programming System Extended/370) V2 R2
(5668-739)
| MQSeries for MVS/ESA V1 (5695-137) R2 with PTFs
| Note: The ILM enablement PTF enables variable Workload UQ16203, UQ16210,
| License Charges and can be found at UQ33429, UQ33430,
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/. The other UQ33432, UQ33433,
| PTFs are necessary in order for the distributed queuing feature to and an ILM
| function correctly when it is used with the IP Services component of enablement PTF
z/OS V1R1 Communications Server. You need not install all the
distributed queuing PTFs; install only those that correspond to the
optional features of MQSeries that you are using.
| MQSeries for OS/390 V2 (5655-A95) R1 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
| MQSeries for OS/390 V5 (5655-F10) R2 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
| License Charges and can be found at
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
MQSeries Integrator for OS/390 and DB2 V1 (5697-F45) R1
MQSeries Workflow for OS/390 V3 (5655-A96) R1
NETDA (Network Design and Analysis) V2 (5685-045) R2
Network Security Processor MVS Support Program V2 (5655-A16) R1
NetView Access Services for MVS V2 (5695-036) R1
NetView Distribution Manager for MVS V1 (5685-016) R6.2
NetView for MVS/ESA V3 (5655-007) R1
NetView FTP for MVS V2 (5685-108) R2.1
NetView MultiSystem Manager for MVS/ESA V2 (5655-126) R2
NetView Performance Monitor (NPM) V1 (5665-333) R6
| NetView Performance Monitor (NPM) V2 (5655-043) R2 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
Network Data Couplers for MVS/ESA and OS/390 V1 (5655-A99) R1
NRF (Network Routing Facility) V1 (5668-963) R6
NSI (Non-SNA Interconnection) V1 (5668-951) R6
NTO (Network Terminal Option) V1 (5735-XX7) R2.1
NTuneMON V1 (5648-077) R2
NTuneMON V2 (5648-141) R1
NTuneMON V3 (5648-D72) R1
NTuneNCP V1 (5648-089) R1
OGL/370 (Overlay Generation Language/370) V1 (5688-191) R1

224 z/OS V1R1.0 Planning for Installation

 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
OPC/ESA (Operations Planning and Control/ESA) V1 (5695-007) R3.1
Note: Successful communication between OPC controller and OPC
tracker agents on platforms connected via the IP Services
component of z/OS V1R1 Communications Server requires Tivoli
OPC (5697-OPC) instead of OPC/ESA. See Tivoli OPC later in this
table for its minimum level.
OpenEdition DCE Application Support for MVS/ESA V1 (5655-064) z/OS V1R1 DCE
Note: 5664-064 is the stand-alone product. In z/OS, use the base Application Support
element DCE Application Support. element
OS/VS DB/DC Data Dictionary V1 (5740-XXF) R6
OS PL/I Compiler, Library, and Interactive Test Facility V2 R3 with PTF UL94209
(5668-909, 5668-910, and 5668-911)
Note: To find out if your PL/I programs need to be re-link edited
with Language Environment, see z/OS Language Environment
Run-Time Migration Guide and PL/I for MVS & VM Compiler and
Run-Time Migration Guide.
OSI/CS (Communications Subsystem) for MVS V1 (5685-014) R1.1
OSI/FS (File Services) for MVS V1 (5685-046) R1
OSL (Optimization Subroutine Library) V1 (5688-137) R2
OV/MVS (OfficeVision/MVS) V1 (5685-106) R3
Parallel Reorganization for IMS/ESA V1 (5697-D13) R1
Payment Gateway for OS/390 V2 (5655-C57) R1
PCF (Programmed Cryptographic Facility) V1 (5740-XY5) R1
Pi and Specials Fonts V1 (5771-ABC) R1.1
PL/I for MVS & VM V1 (5688-235) R1.1
Note: To find out if your OS PL/I compiled and link-edited
programs need to be recompiled with this compiler or re-link edited
with Language Environment, see z/OS Language Environment
Run-Time Migration Guide and PL/I for MVS & VM Compiler and
Run-Time Migration Guide.
PPFA/370 (Page Printer Formatting Aid/370) V1 (5688-190) R1
Print Management Facility/MVS V1 (5665-307) R1.1
Program Restart Facility for IMS V1 (5697-F18) R1
| PSF (Print Services Facility) for OS/390 V3 (5655-B17) R1 with PTF
| UW64475
Notes:
1. The PTF is required to exploit the Printer Inventory Manager
and SNMP Subagent components of Infoprint Server.
2. PSF/MVS V2 (5695-040) is not supported on OS/390 R7 and
later.
Publishing Systems BookMaster V1 (5688-015) R4 with PTFs
UN90425 and
UQ04721
| QMF (Query Management Facility) V3 (5706-254) R3 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.

Appendix C. Minimum Levels of IBM Software Products That Run with z/OS 225
 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
RACF V2 (5695-039) z/OS V1R1
Note: 5695-039 is the stand-alone product. In z/OS, RACF is a SecureWay Security
component of the SecureWay Security Server optional feature. Server feature
Repository Manager/MVS V1 (5665-461) R1
REXX/370 Compiler V1 (5695-013), REXX/370 Library V1 R3
(5695-014)
REXX for CICS V1 (5655-B54) R1
RMDS (Report Management and Distribution System) V1 R4 with PTF
(5665-310) UQ26351
RMDS (Report Management and Distribution System) V2 R3
(5648-048)
RMF V5 (5655-084) z/OS V1R1 RMF
Note: 5655-084 is the stand-alone product. In z/OS, use the feature
optional feature RMF.
Runtime Analyzer for MVS and OS/390 V1 (5697-E06) R1
SDF II (Screen Definition Facility II) V1 (5665-366) R4
SDSF/MVS (System Display and Search Facility/MVS) V1 z/OS V1R1 SDSF
(5665-488) feature
Note: 5665-488 is the stand-alone product. In z/OS, use the
optional feature SDSF.
SearchManager/370 V1 (5695-070) R3
SecureWay Host On-Demand V4 (part number 41L1766, 41L1767, 0.1
41L1768, 0704820, 0704824, or 0704825)
SecureWay Host Publisher for OS/390 V2 (5639-I45) R1
SmartBatch for OS/390 V1 (5655-A17) R1
SnapShot (IBM RAMAC SnapShot for MVS/ESA) V1 (5648-A12) R2
Sonoran Sans Serif Condensed Font V1 (5771-AFL) R1.1
Sonoran Sans Serif Expanded Font V1 (5771-AFN) R1.1
Sonoran Sans Serif Font V1 (5771-ABB) R1.2
Sonoran Sans Serif Headliner Font V1 (5771-ADX) R1.1
Sonoran Serif Font V1 (5771-ABA) R1.2
Sonoran Serif Headliner Font V1 (5771-ADW) R1.1
StorWatch DFSMShsm Monitor V1 (5655-SWT) R1
| System Automation for OS/390 V1 (5645-005) R3 and an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
| System Automation for OS/390 V2 (5645-006) R1 and an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
| License Charges and can be found at
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
SystemView Automated Operations Network/MVS V1 (5695-178) R1
Note: This product is replaced by Tivoli NetView for OS/390
(5697-B82).

226 z/OS V1R1.0 Planning for Installation

 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
TCP/IP V3 (5655-HAL) z/OS V1R1
Note: 5655-HAL is the stand-alone product. In z/OS, use the base Communications
element Communications Server (IP Services component). Server element
| Tivoli Business Systems Manager V1 (5698-BSM) R1
| Tivoli Data Exchange V1 (5698-TDE) R1
| Tivoli Data Message Manager V1 (5698-TMM) R1
Tivoli Data Protection for Lotus Domino, S/390 Edition V1 R1
(5697-DPL)
| Tivoli Decision Support for OS/390 V1 (5698-TD9) R3
| Tivoli Decision Support for OS/390 Accounting Feature V1 R3
| (5698-TDW)
| Tivoli Enterprise Console V3 (5698-EAS) R7
Tivoli Information/Management for MVS/ESA V6 (5695-171) R3
Note: This product is now Tivoli Service Desk for OS/390 V1
(5648–142).
Tivoli Inventory for OS/390 V3 (5697-F04) R6.1
Tivoli Management Framework for OS/390 V3 (5697-D10) z/OS V1R1 Tivoli
Note: 5697-D10 is the stand-alone product. In z/OS, use the base Management
element Tivoli Management Framework. Framework element
Tivoli Manager for MQSeries for OS/390 V2 (5697-D30) R2
Tivoli Manager for OS/390 V1 (5697-TMS) R1
| Tivoli NetView for OS/390 V1 (5697-B82) R1 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
| Tivoli NetView Performance Monitor for TCP/IP (NPM/IP) V1 R1
| (5698-PMI)
| Tivoli OPC (Operations Planning and Control) V2 (5697-OPC) R1 with PTFs
| Note: The ILM enablement PTF enables variable Workload UQ19712, UQ21547,
| License Charges and can be found at and an ILM
| http://www.ibm.com/servers/eserver/zseries/zos/ilm/. The other enablement PTF
PTFs are necessary in order to have communication between OPC
controller and OPC tracker agents on platforms connected via the
IP Services component of z/OS V1R1 Communications Server.
Tivoli Performance Reporter for OS/390 V1 (5695-101) R3
Tivoli Security Management for OS/390 V3 (5697-SCM) R6
Tivoli Service Desk for OS/390 V1 (5648-142) R1
Tivoli Software Distribution for OS/390 V3 (5697-F03) R6.1
| Tivoli Software Distribution V4 (5698-SWD) R1
| Tivoli Storage Management Set, S/390 Edition (5697-TS9) R1
| Tivoli Storage Manager V4 (5698-TSM) R1
Tivoli Storage Manager, S/390 Edition, V3 (5697-TSO) R7.1.3
Tivoli User Administration for OS/390 V3 (5697-ADM) R6
TPNS (Teleprocessing Network Simulator) V3 (5688-121) R5
VisualAge COBOL Millenium Language Extensions for MVS & VM R1
V1 (5654-MLE)

Appendix C. Minimum Levels of IBM Software Products That Run with z/OS 227
 Table 19. Minimum levels of products that run with z/OS V1R1 (continued)
Product (and product number) Minimum release
VisualAge COBOL Millenium Language Extensions for OS/390 & R1
VM V1 (5648-MLE)
VisualAge for Java, Enterprise Edition for OS/390, V2 (5655-JAV) R1
VisualAge Generator Server V1 (5648-B02) R2
| VisualAge PL/I for OS/390 V2 (5655-B22) R2 with an ILM
| Note: The ILM enablement PTF enables variable Workload enablement PTF
License Charges and can be found at
http://www.ibm.com/servers/eserver/zseries/zos/ilm/.
VisualAge PL/I Millenium Language Extensions for MVS & VM V1 R1
(5648-MLX)
VisualAge Smalltalk Server for OS/390 V4 (5655-B14) R5
VS FORTRAN Compiler/Library/Interactive Debug V2 (5668-806), R6
VS FORTRAN Compiler/Library V2 (5688-087), VS FORTRAN
Library V2 (5668-805)
Note: To find out if your Fortran programs need to be re-link edited
with Language Environment, see z/OS Language Environment
Run-Time Migration Guide and Language Environment for MVS &
VM Fortran Run-Time Migration Guide.
VS Pascal Library V1 (5668-717), VS Pascal Compiler and Library R2
V1 (5668-767)
WebSphere Application Server V1 R01
WebSphere Application Server for OS/390 V3 (5655-A98) R02
| WebSphere Commerce Suite, Pro Edition for OS/390, V4 R1
| (5697-G05)
| WebSphere Host Publisher V2 for OS/390 (5655-D70) R2
WLR (Workload Router) V2 (5697-B87) R1
X.25 NPSI (NCP Packet Switching Interface) V2 (5668-719) R1
X.25 NPSI (NCP Packet Switching Interface) V3 (5688-035) R4
X.25 SNA Interconnection V1 (5685-005) R2
X.25 SNA Interconnection V2 (5685-035) R4
X.25 SNA NSF (Network Supervisory Function) V1 (5685-003) R5
XML Toolkit for OS/390 V1 (5655-D44) R1

228 z/OS V1R1.0 Planning for Installation

 Appendix D. Hardware Requirements for z/OS Elements and
Features
Hardware requirements for a target system are discussed in “Identifying Hardware
Requirements for the Target System” on page 62. Beyond these basic requirements,
certain elements and features have additional hardware requirements. This
appendix describes the additional requirements.

Note: For general information about requirements for a Parallel Sysplex

configuration, see the zSeries Parallel Sysplex Customization Wizard at
http://www.ibm.com/servers/eserver/zseries/zos/bkserv/wizards.html.
Table 20. Hardware requirements for z/OS elements and features
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
| BCP A z900 server is required to take advantage of the following z/OS BCP functions: 64-bit
| real storage support, Intelligent Resource Director (IRD), CPU LPAR management, I/O
| priority queuing, license management, and variable Workload License Charging. These
| functions are not available if z/OS is running on an S/390 server.

Automatic tape switching requirements:

v 3480 or 3490 tape drives. Note that a single I/O device should have a single device
number (defined through HCD) across the entire sysplex, and that number should not
be reused for any other device.
For ease of management, IBM recommends that you use the same device number
on all systems to represent an automatically switchable device. If an automatically
switchable device is a 3480 or a 3490 without the ’Read Configuration Data Capable’
function, you must use the same device number on all systems. Note that, if you
have not already applied C05566E, device numbers must be the same.
v All systems that want to share a tape device must be connected to the same
coupling facility.
To share tape drives across multiple z/OS images using LPARs on the same central
processor complex (CPC), physical links are not required. For testing, you could use
ICMF (Integrated Coupling Migration Facility) and emulated links.

| For coupling facility requirements, refer to S/390 Processor Resource/Systems Manager

| Planning Guide or zSeries 900 Processor Resource/Systems Manager Planning Guide.

Global resource serialization (GRS) requirements:

v If all systems in a GRS complex are also in a sysplex, global resource serialization
uses XCF signalling services to communicate between the systems. (Systems are in
the same sysplex if they share the same sysplex couple data set.)
v If any systems are in the GRS complex but not in the sysplex, GRS uses 3088s or
basic mode CTCs to communicate with those systems.

© Copyright IBM Corp. 1996, 2001 229

Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
BCP (continued) XCF (cross-system coupling facility) requirements in a sysplex configuration with one
processor:
v A Sysplex Timer (9037) is not required. However, to provide timing for all members of
the sysplex, one of the following must be true:
– The sysplex is a single-system sysplex on one processor.
– The sysplex runs in multiple logical partitions on a single CPC.
– The sysplex runs as a set of VM guests on the same VM image.
v Unless your system is running in XCF-local mode, a sysplex couple data set is
required.
v If you have more than one system image in the sysplex, XCF signalling connectivity
is required between each system in the sysplex.

In a sysplex configuration with two or more processors, XCF requires all of the
following:
v A Sysplex Timer (9037).
Note: If multiple z/OS systems are running on two or more processors, XCF requires
the processors in the sysplex to be connected to the same Sysplex Timer.
v Shared DASD for the sysplex couple data set. Certain functions require multiple
couple data sets. For more information, see z/OS MVS Setting Up a Sysplex.
v XCF signalling connectivity between each system in the sysplex and every other
system in the sysplex.
This signalling connectivity may be established using several different hardware
means. For z/OS, the signaling mechanisms that are supported are:
– IBM 3088 Multisystem Channel Communication Units
– ESCON Channels that are used as extended mode CTCs
– Coupling facility channels connected to a coupling facility with the use of XCF
signalling structures (supported only with z/OS).
BDT None
BDT File-to-File None
BDT SNA NJE None
BookManager BookServer None
BookManager BUILD None
BookManager READ None
C/C++ IBM Open Class None
Library
C/C++ with Debug Tool None
C/C++ without Debug Tool None
Communications Server See “Hardware Requirements for Communications Server” on page 239.
Communications Server None
NPF
Communications Server None
Security Level 1
Communications Server If hardware cryptography is available, it is used by Communications Server Security
Security Level 2 Level 2.

230 z/OS V1R1.0 Planning for Installation

 Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
Communications Server If hardware cryptography is available, it is used by Communications Server Security
Security Level 3 Level 3.

The use of hardware cryptography by Communications Server Security Level 3 requires

| the Cryptographic Coprocessor feature, which is standard on a z900 server and optional
on an S/390 Parallel Enterprise Server (Model G5 or G6).
Cryptographic Services In order for ICSF to provide cryptographic services, the Cryptographic Coprocessor
hardware feature is required. The feature is available on the following processors that
are supported by z/OS:
v S/390 Parallel Enterprise Server (Model G5 or G6) with feature code 0800 and one of
the following feature codes: 0811, 0812, 0813, 0814, 0815, 0832, 0833, 0834, 0835
| v z900 server with feature code 0800 plus either feature code 0874 or feature code
| 0875

The PCI Cryptographic Coprocessor (PCICC) hardware feature can be used to

supplement the Cryptographic Coprocessor feature with added functions and
performance. It is available on the following processors that are supported by z/OS:
v S/390 Parallel Enterprise Server Model G5 field upgrade or S/390 Parallel Enterprise
Server Model G6 with feature codes 0864 or 0865. Feature code 0860 is needed for
each PCICC.
| v z900 server with feature codes 0861 and 0865.
DCE Application Support For Transactional RPC (TRPC), a coupling cacility is required.
DCE Base Services None

Appendix D. Hardware Requirements for z/OS Elements and Features 231

Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
DFSMSdfp Catalog sharing enhancements (ECS) for sysplex environments: To use this function, a
coupling facility is required.

Data compression: For optimal performance, this support uses the data compression
feature that is available on some system processors. If the hardware is not available, it
uses the software compression facility to compress data.

Defining and accessing extended format sequential data sets through BSAM and
QSAM: Extended format data sets must reside on DASD attached through cached
storage controls and an ESCON or FICON channel adapter.

Extended remote copy (XRC): When migrating data with XRC, the primary storage
device must be attached to a remote copy-capable storage subsystem, such as an
Enterprise Storage Server.

OAM object tape support: To use this function, an IBM Tape Library Dataserver is
required.

OAM optical library support: To use this function, an IBM 3995 Optical Library
Dataserver is required.

OAM Parallel Sysplex support: To use this function, cross-system coupling facility (XCF)
hardware is required.

OAM virtual tape server support: To use this function, a virtual tape server subsystem in
an automated tape library (Magstar 3494 Tape Library) is required.

PDSE cross-system sharing support: If sharing PDSEs in a parallel sysplex

environment, cross-system coupling facility (XCF) hardware is required.

Storage management subsystem 32-name support: When defining more than 16

systems in an SMS complex, you must allocate the ACDS and the COMMDS on DASD
volumes that are capable of attaching to more than 16 systems.

Virtual Tape Server (VTS) export/import support: Requires a Virtual Tape Server model
B18 library that includes the extended high performance option (EHPO) feature, a
minimum of four 3590 native devices, and the convenience I/O station installed.

VSAM extended addressability: To use this function, an extended format KSDS must be
defined on DASD attached to a cached storage subsystem.

VSAM record level sharing (RLS): To use this function, a coupling facility is required.

232 z/OS V1R1.0 Planning for Installation

Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
DFSMSdss Concurrent copy: To use this function, data must reside on DASD volumes attached
through a concurrent copy-capable storage subsystem.

Defining and accessing extended format sequential data sets through BSAM and
QSAM: Extended format data sets must reside on DASD attached through cached
storage controls and an ESCON or FICON channel adapter.

Snapshot and virtual concurrent copy: To use this function, a snapshot-capable storage
device is required.

Storage management subsystem 32-name support: When defining more than 16

systems in an SMS complex, you must allocate the ACDS and the COMMDS on
volumes that are capable of attaching to more than 16 systems.

VSAM extended addressability: To use this function, an extended format KSDS must be
defined on DASD attached to a cached storage subsystem.

VSAM record level sharing (RLS): A coupling facility (at least one) must be connected to
all systems capable of VSAM RLS. For multiple coupling facilities, select one facility
with global connectivity to contain the master lock structure. The coupling facility must
be at control level 2. It must be large enough to contain either a lock or a cache
structure, or both, and have enough surplus space to allow the structures to be
modified. The cache structures must be defined to SMS to enable it for VSAM RLS.
DFSMShsm Control data set extended addressability: To use this function, a coupling facility is
required.

Control data set (CDS) record level sharing (RLS) serialization: To use this function, a
coupling facility is required.

Defining and accessing extended format sequential data sets through BSAM and
QSAM: Extended format data sets must reside on DASD attached through cached
storage controls and an ESCON or FICON channel adapter.

Storage management subsystem 32 name support: When defining more than 16

systems in an SMS complex, you must allocate the ACDS and the COMMDS on
volumes that are capable of attaching to more than 16 systems.

Storage management subsystem system groups: Some SMS complex configurations

might require DASD with enhanced connectivity. Because all systems in an SMS
complex share the same configuration data sets, the ACDS and the COMMDS must
reside on DASD devices that are accessible to the system activating the configuration.

VSAM extended addressability: To use this function, an extended format KSDS must be
defined on DASD attached to a cached storage subsystem.

VSAM partial release: To use this function, extended format data sets must reside on
DASD attached through cached storage subsystems.

VSAM record level sharing (RLS): A coupling facility (at least one) must be connected to
all systems capable of VSAM RLS. For multiple coupling facilities, select one facility
with global connectivity to contain the master lock structure. The coupling facility must
be at control level 2. It must be large enough to contain either a lock or a cache
structure, or both, and have enough surplus space to allow the structures to be
modified. The cache structures must be defined to SMS to enable it for VSAM RLS.
DFSMSrmm None
DFSORT If Japanese DFSORT/ISPF and DFSORT/ISMF panels are installed, the workstations
must support double-byte character set (DBCS) data (for example, IBM 5550 System).

Appendix D. Hardware Requirements for z/OS Elements and Features 233

Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
Distributed File Service None
Encina Toolkit Executive None
EREP None
ESCON Director Support None
FFST None
GDDM GDDM supports devices that use the 3270 Extended Data Stream, the architected
extensions to SNA character string (SCS), or IPDS. GDDM supports any other terminal
or terminal-attached printer and provides graphics and image functions if it is upwardly
compatible with the supported device. Certain non-IBM ASCII displays are supported
through the 3174 Controller or on an upgraded older model 3174 Controller.

GDDM host graphics are supported for viewing, printing, and plotting on OS/2 through
CM/2 1.11 solely, IBM Personal Communications/3270 for OS/2 V4, or GDDM/MVS V3
download for GDDM-OS/2 Link in addition to CM/2. For MS Windows, use either IBM
Personal Communications/3270 V3 or V4, the latter providing a native graphics
emulator.

GDDM host graphics are supported on DOS for viewing and printing/plotting to
GDDM-PCLK supported devices through IBM Personal Communications/3270 V2 or
later, and download of GDDM-PCLK from GDDM/MVS V3.

GDDM host graphics are supported for viewing on AIX terminals through the X3270
emulator or the TCP/IP GDDMXD facility.
GDDM-PGF None
GDDM-REXX None
HCD None
HCM Hardware that can be used to establish an APPC or TCP/IP connection from the
workstation to the z/OS host is required.

Workstation (PWS) requirements:

v Processor: 133 MHz Pentium®
v Memory: 32 MB
v Disk space: about 50 MB
v Network adapter
v SVGA adapter

HLASM To display or enter double-byte data, any of the following are required:
v DBCS 3270 emulation on RS/6000 or PS/55
v DBCS non-programmable terminal

To print double-byte data, any of the following are required:

v Advanced Function Printing (AFP) printers
v 3270 remote printing on RS/6000 or PS/55
HLASM Toolkit None
IBM HTTP Server A networked workstation with a web browser is required.
IBM HTTP Server NA If hardware encryption is desired, cryptographic hardware is required.
Secure
ICKDSF None

234 z/OS V1R1.0 Planning for Installation

 Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
| ILM ILM will be initially delivered on 30 March 2001 (as part of z/OS V1R1) for
| preproduction use, with Workload License Charges at full machine capacity. Customer
| production use of ILM, with Workload License Charges at less than full machine
| capacity, will be available when IBM completes full testing of ILM and you have applied
| the recommended z/OS service to make your system ILM production-ready. This testing
| by IBM is planned to be complete by the end of September 2001. The hardware
| requirements in this table apply to both the preproduction and production use of ILM.

| The host requirement is a z900 server so that you can activate ILM and take advantage
| of workload-based pricing.

| The management tool workstation requirements are:

| v For Windows NT: The minimum is a 200 MHz Pentium II processor with 64 MB of
| memory (but 96 MB is recommended).
| v For Windows 2000: The minimum is a 300 MHz Pentium III processor with 96 MB of
| memory (but 128 MB is recommended).
Infoprint Server Printer and connectivity requirements depend on the function to be performed:
| v To print output using IP PrintWay, a printer connected via z/OS V1R1
| Communications Server (either IP Services or SNA Services) is required. An IP
| connection requires a printer that supports the LPR protocol, the IPP protocol, or
| TCP/IP direct sockets. A SNA connection requires a printer that supports the SCS or
| DSC/DSE data streams.
v To print AFP data streams, an IPDS (Intelligent Printer Data Stream) printer
supported by PSF V3 is required, with the appropriate hardware attachment (channel,
SNA, or TCP/IP) for the printer.
v Line data can be printed on any printer supported by JES2 or JES3.
v To receive LPR print requests from a remote host, a TCP/IP connection is required
from the remote host to the z/OS host.

A workstation capable of running Windows 95, Windows 98, or Windows NT is required

to use the following client functions:
v AFP Printer Driver for Windows.
v AFP Viewer plug-in for Windows.
v OS/390 Printer Port Monitor for Windows. The OS/390 Printer Port Monitor also
requires a TCP/IP connection from the workstation to the z/OS host.
v SMB printing protocol.

The SNMP Subagent component requires IBM Network Printer Manager running on a
Windows NT workstation or Windows NT server. The minimum server hardware is:
v IBM-compatible personal computer with 100 MHz Pentium processor (133 MHz or
greater is recommended)
v Network interface card
v 16 MB RAM (32 MB or more is recommended)
v 7 MB free hard disk space

The following printers are supported directly by Network Printer Manager:

v IBM Infoprint 20, 32, and 40
v IBM Network Printer 12, 17, 24, and 24PS
v Other manufacturers’ network printers that comply with RFC1759, such as
Hewlett-Packard LaserJet 5Si or Lexmark Optra N

Appendix D. Hardware Requirements for z/OS Elements and Features 235

 Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
ISPF The ISPF base implementation requires a full-screen display terminal that supports
3270 data stream and provides a minimum interactive screen of 24 lines by 80
characters and a maximum interactive screen of 62 lines by 160 characters.

On the host, the ISPF Client/Server (ISPF C/S) implementation requires the following:
v A TCP/IP or APPC network connection from the workstation to the z/OS host

On the programmable workstation, the ISPF C/S implementation requires one of the
following:
v Any personal computer capable of running Windows 95, Windows 98, Windows 2000,
Windows NT, or OS/2 with 5 MB of available disk storage to contain the ISPF C/S
software and a VGA or higher resolution color display. The minimum recommended
processor type is a Pentium processor. The minimum memory required is 48 MB.
v Any RS/6000 machine capable of running AIX Version 4.1.5 with 8 MB of available
disk storage to contain the ISPF C/S software and a display device or x-station
capable of running Motif 1.2.
v Any HP/700 machine capable of running HP-UX Version 9.03 with 20 MB of available
disk storage to contain the ISPF C/S software and a display device or x-station
capable of running Motif 1.2.
v Any SPARC workstation capable of running Solaris Version 2.5.1 with 8 MB of
available disk storage space to contain the ISPF C/S software and a display device
or x-station capable of running Motif 1.2 or OpenLook.
JES2 A JES2 MAS with multiple z/OS images using multiple central processors requires a
Sysplex Timer to synchronize time across the processors.
JES3 A JES3 complex with multiple z/OS images using multiple central processors requires a
Sysplex Timer to synchronize time across the processors.
| LAN Server LAN Server is being removed from OS/390 because the prerequisite OS/2 software is
| no longer available. OS/390 R9 was the last release to include both the workstation (on
| diskettes) and host components. OS/390 R10 and z/OS V1R1 have only the host
| component. After z/OS V1R1, neither component will be available. For customers who
| want to migrate to z/OS V1R1 prior to migrating off LAN Server, the OS/2 Front End
| Processor configurations from previous releases of LAN Server are still supported on
| z/OS V1R1. See S/390 File and Print Serving, SG24-5330, for alternative solutions and
| migration guidance.
Language Environment None
| LANRES LANRES requires a PC capable of running Novell NetWare Version 3.x or later. Check
| NetWare documention to determine minimal hardware requirements.

| LANRES supports PCI ESCON adapters (9663-001) and PCI PARALLEL adapters
| (9663-002) that can be plugged into any PCI bus PC. Performance may improve with
| LANStreamer or Ethernet adapters because they can speed up data through the
| input/output bus. Additional hardware requirements depend on the communication
| method you choose for your system.

| LANRES provides minimal support for NETWARE for SAA. There is no support for SAA
| 4 or SAA 5. There is no Channel Driver Connection support for SAA 3.

| In addition to the basic hardware requirements, if you will be using TCP/IP protocols,
| you will need hardware to support TCP/IP protocols on the NetWare server. For more
| information, see the NetWare documentation.
MICR/OCR None

236 z/OS V1R1.0 Planning for Installation

 Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
| msys for Setup Minimum workstation requirements:
| v Processor: 266 MHz
| v Memory: 128 MB (192 MB recommended)
| v Disk space: 100 MB
| v Screen resolution: 800 x 600 (1024 x 768 recommended)

| Host requirements: none

Network File System None
OCSF Security Level 3 None
OSA/SF Foremost, OSA/SF requires an OSA. For information on the requirements for an OSA,
see S/390: OSA-Express Customer’s Guide and Reference or Planning for the
System/390 Open Systems Adapter Feature (OSA-1, OSA-2). However, note that:
| v OSA-1 is not supported on the z900 server. The only OSA-2 features supported on
| the z900 are the token ring and FDDI features. All OSA-Express features are
| supported on the z900, however, the FENET feature does not run in HPDT MPC
| mode on that server.
v Any OSA can be run in the TCP/IP Passthru and SNA modes except OSA-Express
Gigabit Ethernet.
v Only an FDDI OSA-2, a Fast Ethernet (FENET) OSA-2, or a FENET OSA-Express
feature can be run in the High Performance Data Transfer (HPDT) MPC mode.
v Only the OSA-Express features (Gigabit Ethernet, Fast Ethernet, and ATM running
Ethernet LAN emulation) support IP traffic using QDIO architecture working with the
IP Services component of z/OS V1R1 Communications Server.
v Only an Asynchronous Transfer Mode (ATM) OSA-2 or an ATM OSA-Express feature
can be run in ATM Native mode. Only ATM OSA-2 can be run in ATM IP Forwarding
mode.

If its OS/2 or Windows (GUI) interface is to be used, OSA/SF requires:

v A workstation with a Pentium 200 Mhz (or equivalent) processor, 32 MB RAM, and an
SVGA display with a resolution of 1024x768x16 colors is recommended. You might
be satisfied with OSA/SF GUI performance on the minimum processor required by
your OS/2 or Windows operating system, but the GUI might not display correctly at a
lesser resolution.
v One of the following communication adapters that are supported by OS/2 and the
microprocessor:
– EHLLAPI for 3270 communications protocol
– TCP/IP communications protocol
– APPC, or CPI-C, protocol for a node that supports LU 6.2
RMF For all RMF workstation functions:
v A workstation with a Pentium II or later processor
v A graphics adapter and monitor with a configured resolution of at least 1024x768
pixels
v At least 32 MB RAM (for Performance Monitoring of OS/390: 96 MB RAM)

SDSF None

Appendix D. Hardware Requirements for z/OS Elements and Features 237

Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
SecureWay Security Server If you run in data sharing mode in a Parallel Sysplex configuration, a coupling facility
must be configured for RACF’s use.

Firewall Technologies uses either the DES or triple-DES functions available with the
Cryptographic Coprocessor hardware feature (on a z900 server or S/390 Parallel
Enterprise Server, Model G5 or G6) and the z/OS Cryptographic Services software
feature to provide firewall encryption “tunneling”, which creates virtual private networks
(VPNs) in intranet or Internet environments.
SMP/E None
SOMobjects ADE None
SOMobjects RTL None
System SSL Security Level None
3
Text Search None
TIOC None
Tivoli Management None
Framework
TSO/E These requirements apply to interactive use of TSO/E, not to batch use. Any terminal
supported by base element Communications Server, or ACF/TCAM V2R4 (5735-RC3)
or later, is required. The full-screen LOGON, TRANSMIT and RECEIVE commands, the
Session Manager, and the Information Center Facility, which need a minimum screen
size of 24 by 80, require one of the following terminals:
v IBM 3270 Information Display System Terminals
– 3275 Models 2 and 12
– 3276 Models 2, 3, 4, 12, 13, and 14
– 3277 Model 2
– 3278 Models 2, 3, 4, and 5 (monochrome)
– 3279 Models 2A, 2B, 2X, 3A, 3B, 3X, S2A, S2B, and S3G (base color mode)
v IBM 3472 Family
v IBM 3178 Display Terminal Models C1, C2, C3, and C4
v IBM 3179 Display Terminal Model 1 and Model G (alphanumeric mode)
v IBM 3180 Display Terminal Models 100 and 110
v IBM 3191 Display Terminal Models A30, A40, B30, B40, D, E, and L
v IBM 3192 Color Display Terminal Models A, B, C, D, F, G, L, and W
v IBM 3194 Display Terminal
v IBM 3290 Information Panel
v IBM PS/2 family (configured for 3270 support)
v IBM Personal Computer (configured for 3278/79 support)
v IBM PS/55 family (configured for 3270 support)
v IBM 5550 family (configured for 3270 support)
v Any other terminal that functions in compatibility mode with the terminals listed
above.

The VM/PC servers (spool, disk, and file) available with the MVSSERV command
processor require the IBM Personal Computer Models XT/370 or AT/370 with an IBM
3278/79 Device Emulation Adapter.

238 z/OS V1R1.0 Planning for Installation

 Table 20. Hardware requirements for z/OS elements and features (continued)
Element or feature Additional hardware required beyond the basic hardware requirements for z/OS
V1R1
z/OS UNIX System The extended user interface support allows existing hardware (such as terminals and
Services workstations) and existing telecommunications software (such as VTAM and TCP/IP)
that run on z/OS to be used.

For 3270 support, most 3270 type terminals or 3270 emulators in a z/OS network from
which a user can interactively log on to TSO/E are supported by z/OS UNIX services
and include:
v Real and emulated 3270s in a VTAM SNA network which satisfy the following.
– The minimum screen size is 24x80.
– The terminal must be known to TSO/E and VTAM as a full-screen device. z/OS
UNIX services use full-screen mode.
– The terminal must support upper- and lower-case characters.
– A minimum of 12 PF keys are required.
v UNIX workstations and other workstations in a TCP/IP network that supports the
TELNET 3270 (TN3270) client function.
v The OMVS command supports customized PF keys to scroll backward/forward,
display HELP, hide input typed into the command line, refresh the screen, retrieve
previous commands, and enter TSO/E commands.

For ASCII control sequence support from 3270 Displays, the OMVS command, with the
pseudoterminal functions, maps and transforms a 3270 TSO/E terminal interface and
user externals to the POSIX 1003.1 defined terminal interface expected by POSIX
compliant user processes, including the POSIX 1003.2 Shell. This mapping consists of:
v Use of 3270 key sequences to emulate ASCII terminal control is supported.
A set of system-defined 3270 default key sequences that map to ASCII escape
control values is supplied. The user can tailor the system defaults.
v Execution in canonical (line-oriented) mode only.
v Conversion tables that map the 3270 data stream to a pseudoterminal device driver
for both control and data are provided. Users can customize these tables.

For ASCII Terminal Interface, UNIX workstations and other workstations in a TCP/IP
network that support the telnet or rlogin virtual terminal protocols can directly login to
the z/OS Shell through Communications Server. The supported ASCII terminal interface
conforms to X/OPEN Issue 4, Version 2.
3270 PC File Transfer An IBM or compatible PC with with appropriate communications device, such as a LAN
Program adapter or modem, is required.

Hardware Requirements for Communications Server

Hardware requirements for Communications Server are in two sections:
v “IP Hardware Requirements”
v “SNA Hardware Requirements” on page 242.

IP Hardware Requirements
| The z/OS Communications Server provides direct LAN communication and provides
| for point-to-point communication over S/390 channels (ESCON and/or Block
| Multiplex) to several IBM and equivalent other vendor devices.

| Direct LAN communication is provided by:

| v IBM Open Systems Adapter - Express
| v IBM Open Systems Adapter
| v IBM 3172 Interconnect Controller
| v IBM 8232 LAN Channel Station

Appendix D. Hardware Requirements for z/OS Elements and Features 239

| Point-to-point communication over z/OS or S/390 channels is supported with the
| following devices:
| v IBM RS/6000
| v IBM Channel-to-Channel Adapter
| v IBM 374X Communications Controller
| v IBM 2216 Multiaccess Connector
| v IBM Netfinity Server
| v Cisco 7200 and 7500-series Channel Attached Routers
| v NSC Hyperchannel A220

Network Attachments
To attach TCP/IP to the network you need one of the following network processors
and associated components or their equivalents:

2216 Multiaccess Connector Model 400

v To attach to the 2216 using MPC+ or LCS, an ESCON or parallel channel
adapter is required. For details, refer to 2216 ESCON Adapter Setup.

IBM 3172 Interconnect Controller with the Interconnect Controller Program

(ICP)
v IBM 3172 Interconnect Controller Model 001, 002, or 003
v IBM Interconnect Controller Program (5601-433 or 5621-425)
v One of the following types of adapters:
– 3172 Interconnect Controller Token-Ring Adapter (#2215)
– 3172 Interconnect Controller Ethernet Adapter (#2220)
– 3172 Interconnect Controller Ethernet Adapter (#2225)
– Auto LANStreamer MC 32 Adapter (#2235)
– EtherStreamer MC 32 Adapter (#2245)
– 3172 Interconnect Controller FDDI A Station Adapter (#2250)
– 3172 Interconnect Controller Network Baseband Adapter/A (#2270)
– 3172 Interconnect Controller Network Adapter II/A (#2271)
– 3172 Interconnect Controller Network Adapter II/A Frequency 2 (#2272)
– 3172 Interconnect Controller Network Adapter II/A Frequency 3(#2273)
– 3172 Interconnect Controller FDDI Adapter (#2300)
– TURBOWAYS 100 ATM Adapter for the 3172 Model 3 (#2310) (LAN emulation
for Token-Ring and Ethernet)
v One of the following channel adapters:
– PCA adapter (#2501)
– ESCON adapter (#2800)
v Standard System/370 I/O Channel Interface Cable

Note: The Pentium P90 Processor is supported.

IBM 8232 LAN Channel Station for LANs

v IBM 8232 LAN Channel Station Model 001 or 002
v One or more adapters for Token Ring, PC Network, or Ethernet
v Standard System/370 I/O Interface cable

IBM RISC System/6000 Channel Attachment

v To attach to the RISC System/6000 using CLAW, the following items are
required:
– IBM RISC System/6000 with the Block Multiplexer Channel Adapter (#2755)
– AIX V3R2.3 (5756-030), or later, with feature (#5056)

240 z/OS V1R1.0 Planning for Installation

 – Standard ESCON Adapter
v To attach to the RISC System/6000 using MPCPTP, the following items are
required:
– AIX 4.3 (or later)
– PCI ESCON Control Unit Connectivity Version 2.1

IBM Open Systems Adapter (OSA) Feature

v OSA-1 Feature supporting FDDI, Ethernet, and Token Ring
v OSA-2 Feature supporting FDDI, Ethernet, Token Ring, Fast Ethernet, and ATM
v OSA-Express supporting Gigabit Ethernet, Fast Ethernet, or ATM

z/OS V1R1 Communications Server Gigabit Ethernet support requires the

OSA-Express adapter.

For additional information about OSA, refer to the following publications:

| v OSA-1 and OSA-2: OSA Planning and z900: OSA-2 Planning Guide
| v OSA-Express:S/390: OSA-Express Customer’s Guide and Reference and z900:
| OSA-Express Customer’s Guide and Reference

IBM 37xx family of communication controllers for X.25, Systems Network

Architecture, and IP over Channel Data Link Control
v IBM 3745 Communication Controller for:
– X.25
– Ethernet
– Token Ring
– Frame Relay
v A microcode engineering change (EC) is required for the IP Dynamics (with
Ethernet) capabilities:
– C38006 for models 130, 150, 160, 170, and 17A
– C37967 for models 210, 310, 410, and 610
– C39888 for models 21A, 31A 41A, and 61A
v IBM 3746 or 3746–900 Communication Controller for:
– X.25
– ATM
– Token Ring
– Frame Relay
v A microcode engineering change (EC) is required for the IP-over-Channel
(CDLC) for the 3746
The 3746-900 requires microcode EC number D22510 at microcode change level
ECA 142 for communication across an ESCON channel. The microcode level is
shipped automatically with new 3746-900s. For installed machines running an
earlier level of microcode, microcode ECA 142 can be ordered by the service
representative.
v Standard System/370 I/O Channel Interface Cable

HYPERchannel A220 Processor Adapter 42990007

v HYPERchannel Series A devices

Appendix D. Hardware Requirements for z/OS Elements and Features 241

 v HYPERchannel Series DX devices, provided they function as Series A devices
(For additional information, refer to the appropriate Network Systems Corporation
documentation.)
v Standard System/370 I/O Interface cable

The ATTENTION+BUSY and unit check conditions are normally handled in the
background and can affect performance without any visible evidence. The
recommendations on Hyperchannel A222 and A223 Mode Switch Settings follow:
v The Disable Attentions setting on the Hyperchannel box eliminates the
ATTENTION+BUSY status in response to read commands. This setting reduces
overhead.
v The Enable Command Retry setting reduces the number of unit checks needed
because of a trunk connection. This setting improves performance because it
eliminates the need to perform sense operations and retry commands.

SNA Hardware Requirements

For communication with remote resources, one or more of the following products
supported by VTAM, or their equivalent, is required:
| v ^ zSeries 64-bit real
| v ^ zSeries HiperSockets
v Channel-to-channel adapter
| v FICON channel-to-channel adapter
v IBM 2216 NWays Multiaccess Connector
v IBM 3088 Multisystem Channel Communication Unit
v IBM 3172 Nways Interconnect Controller
v IBM 3174 Establishment Controller
v IBM 3720, 3725, or 3745 Communication Controller
v IBM 3746 Nways Multiprotocol Controller
v IBM Cross-System Coupling Facility (XCF)
v IBM Enterprise System Connection (ESCON) channel
| v IBM Open Systems Adapter-Express
v IBM Open Systems Adapter

APPN over native ATM requires:

v OSA-2 adapter
v 9672 Parallel Enterprise Server Model R2 or later processor
v ATM external private or public equipment. For example, IBM 8260 NWays
Multiprotocol Intelligent Switching Hub Multinode Persistent Sessions support
requires a coupling facility at CFLEVEL=1. VTAM Generic Resource support
requires a coupling facility with CFLEVEL=0. VTAM cryptographic enhancements,
when used with the extended recovery facility (XRF) and Transaction Security
System (TSS) family of products (4755), require 4755 Model 23 and later.

| Persistent Sessions support requires a coupling facility at CFLEVEL=1.

| VTAM Generic Resource support requires a coupling facility with CFLEVEL=0.

| VTAM cryptographic enhancements, when used with the extended recovery facility
| (XRF) and Transaction Security System (TSS) family of products (4755), require
| 4755 Model 23 and later.

SNA triple DES (TDES) session level encryption requires an S/390 Parallel
Enterprise Server Model G5 or later with the Cryptographic Coprocessor.

242 z/OS V1R1.0 Planning for Installation

 Appendix E. Data Set Placement Recommendations for Target
Volumes
This appendix contains tables referred to by the section “Recommended Data Set
Placement” on page 170. The tables map all the z/OS target libraries to either target
library volume 1 (TVOL1) or target library volume 2 (TVOL2). This mapping
comprises IBM’s recommended system layout.

The tables list the following for each data set:

v DDDEF name.
v The z/OS element or feature that uses each data set. When more than one
element or feature installs into the same library, the table lists all the element and
feature names.
v The type of order with which the data set is included:
– Base
– Priced
– Unpriced
– NLV (national language version)
– When more than one element or feature name is listed, the term “MULTI” is
used to specify that the different elements or features could include base
elements, optional priced features, or optional unpriced features.
v The recommended volume.
v The data set type.

| The easiest way to implement the data set layout described in this appendix (IBM’s
| recommended layout) is to assign your order’s data sets to DASD volumes
| automatically, using the CustomPac Installation Dialog’s Create a Recommended
| System Layout function. The alternative is to assign data sets manually using either
| (1) the View and Change Data Sets by Selected Attributes function or (2) the
| Summary Display commands on the Modify System Layout Options panel.

| Note: The TVOL1 and TVOL2 assignments shown in this appendix might not
| correspond exactly to your CustomPac configuration after the Create a
| Recommended System Layout function is complete. This is due to the
| CustomPac Installation Dialog’s ability to manage the space on your
| individual DASD, and assign the data sets in your customized order in a
| manner consistent with the recommended system layout. For example, your
| DASD volumes might be too small to allow the assignments shown in this
| appendix.
|
CLIST Libraries
Table 21 and Table 22 on page 244 list the z/OS libraries that contain CLISTs.
Table 21. CLIST libraries
DDDEF name Element or feature name Included Volume Type
with
ADFMAC1 TSO/E Base TVOL1 CLIST
DGTCLIB DFSMSdfp, DFSMSdss Base TVOL1 CLIST
HRFCLST SecureWay Security Server Priced TVOL1 CLIST
(RACF component)

© Copyright IBM Corp. 1996, 2001 243

 Table 21. CLIST libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
ICQCCLIB TSO/E Base TVOL1 CLIST
SBDTCLI0 BDT Base TVOL1 CLIST
SBLSCLI0 BCP and DFSMSdfp, contain Base TVOL1 CLIST
Change Migration CLISTs
SCBDCLST HCD, contains Change Migration Base TVOL1 CLIST
CLISTs
SCEECLST Language Environment Base TVOL1 CLIST
SCSFCLI0 Cryptographic Services (ICSF Base TVOL1 CLIST
component)
SEPHCLIB BookManager BookServer Base TVOL1 CLIST
SEPWCENU FFST Base TVOL1 CLIST
SERBCLS RMF Priced TVOL1 CLIST
SEZANCLS Communications Server (IP Base TVOL1 CLIST
Services component)
SEOYCLIB BookManager READ Base TVOL1 CLIST
SGIMCLS0 SMP/E Base TVOL1 CLIST
SIATCLI0 JES3, contains Change Priced TVOL1 CLIST
Migration CLISTs
SICECLIB DFSORT Priced TVOL1 CLIST
SISPCLIB ISPF Base TVOL1 CLIST
SISTCLS1 Communications Server (SNA Base TVOL1 CLIST
Services component) contains
Change Migration CLISTs

Table 22. NLV CLIST libraries

DDDEF name Element or feature name Included Volume Type
with
ICQGCLIB TSO/E (German) NLV TVOL1 CLIST
ICQKCLIB TSO/E (Japanese) NLV TVOL1 CLIST
ICQPCLIB TSO/E (Simplified Chinese) NLV TVOL1 CLIST

Data Libraries
Table 23 and Table 24 on page 249 list the z/OS libraries that contain data parts.
These data libraries may include workstation information, header files, or other
various types of data. Some of these data sets belong on the first target volume;
the rest belong on the second target volume.
Table 23. Data libraries
DDDEF name Element or feature name Included Volume Type
with
CBRDBRM DFSMSdfp Base TVOL1 Data
DBBLIB DFSMSdfp Base TVOL1 Data
IGDVBS1 DFSMSdfp Base TVOL1 Data

244 z/OS V1R1.0 Planning for Installation

Table 23. Data libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
NFSTARB Network File System Base TVOL1 Data
SADMCDA GDDM Base TVOL1 Data
SADMCFO GDDM Base TVOL1 Data
SADMDAT GDDM Base TVOL1 Data
SADMGDF GDDM Base TVOL1 Data
SADMIMG GDDM Base TVOL1 Data
SADMMAP GDDM Base TVOL1 Data
SADMPCF GDDM Base TVOL2 Data
SADMSYM GDDM Base TVOL2 Data
SADRYLIB DFSMSdss Base TVOL1 Data
SAPPDAT2 Communications Server (SNA Base TVOL1 Data
Services component)
SAPPDAT4 Communications Server (SNA Base TVOL1 Data
Services component)
SASMPUT2 HLASM Toolkit Priced TVOL2 Data
SASUACF DCE Application Support Base TVOL2 Data
SASUHDR DCE Application Support Base TVOL2 Data
SASUIDL DCE Application Support Base TVOL2 Data
SASUCIDL DCE Application Support Base TVOL2 Data
SBFSDBTB LAN Server Base TVOL2 Data
SBFSOBIN LAN Server Base TVOL2 Data
SBFSRBIN LAN Server Base TVOL2 Data
SBFSTTBL LAN Server Base TVOL2 Data
SBFSDBTB LAN Server Base TVOL2 Data
SBFSOBIN LAN Server Base TVOL2 Data
SBFSRBIN LAN Server Base TVOL2 Data
SBFSTTBL LAN Server Base TVOL2 Data
SCBDTEMP HCD Base TVOL1 Data
SCDRTABL DFSMSdfp Base TVOL1 Data
SCEECMAP Language Environment Base TVOL1 Data
SCEECPP Language Environment Base TVOL1 Data
SCEEGXLT Language Environment Base TVOL1 Data
SCEELIB Language Environment Base TVOL1 Data
SCEELKEX Language Environment Base TVOL1 Data
SCEELOCL Language Environment Base TVOL1 Data
SCEELOCX Language Environment Base TVOL1 Data
SCEEOBJ Language Environment Base TVOL1 Data
SCEESPCO Language Environment Base TVOL1 Data
SCEEUMAP Language Environment Base TVOL2 Data
SCEEUTBL Language Environment Base TVOL1 Data

Appendix E. Data Set Placement Recommendations for Target Volumes 245

 Table 23. Data libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
| SCIMXML msys for Setup Base TVOL1 Data
SCLBCPP C/C++ IBM Open Class Library Base TVOL1 Data
SCLBHC C/C++ IBM Open Class Library Base TVOL2 Data
SCLBHH C/C++ IBM Open Class Library Base TVOL2 Data
SCLBHI C/C++ IBM Open Class Library Base TVOL2 Data
SCLBHPP C/C++ IBM Open Class Library Base TVOL2 Data
SCLBSAC C/C++ IBM Open Class Library Base TVOL2 Data
SCLBSAH C/C++ IBM Open Class Library Base TVOL2 Data
SCLBSID C/C++ IBM Open Class Library Base TVOL1 Data
SCLBTUH C/C++ IBM Open Class Library Base TVOL2 Data
SCLBTUT C/C++ IBM Open Class Library Base TVOL1 Data
SCLBTUTD C/C++ IBM Open Class Library Base TVOL2 Data
SCLDBLD C/C++ with Debug Tool, C/C++ Priced TVOL1 Data
without Debug Tool
SCLDHC C/C++ with Debug Tool, C/C++ Priced TVOL1 Data
without Debug Tool
SCLDHCPP C/C++ with Debug Tool, C/C++ Priced TVOL1 Data
without Debug Tool
SCLDHCX C/C++ with Debug Tool, C/C++ Priced TVOL1 Data
without Debug Tool
SCLDHH C/C++ with Debug Tool, C/C++ Priced TVOL1 Data
without Debug Tool
SCLDHI C/C++ with Debug Tool, C/C++ Priced TVOL1 Data
without Debug Tool
SCLDHPP C/C++ with Debug Tool, C/C++ Priced TVOL1 Data
without Debug Tool
SCLDSRE C/C++ with Debug Tool, C/C++ Priced TVOL1 Data
without Debug Tool
SCMXDBRM z/OS UNIX System Services Base TVOL2 Data
SCSFHDRS Cryptographic Services (ICSF Base TVOL2 Data
component)
SCSFOBJ Cryptographic Services (ICSF Base TVOL2 Data
component)
SDFQPSRC DFSMShsm Base TVOL2 Data
SDGTPSRC DFSMSdfp, DFSMSdss Base TVOL2 Data
SDGTTSRC DFSMSdfp, DFSMSdss, Base TVOL2 Data
DFSMSrmm
SECNEXP Encina Toolkit Executive Base TVOL2 Data
SEDGPSRC DFSMSrmm Base TVOL2 Data
SEDGTSRC DFSMSrmm Base TVOL2 Data
SEEQINST HCM Priced TVOL2 Data
SEPHTAB BookManager BookServer Base TVOL1 Data

246 z/OS V1R1.0 Planning for Installation

Table 23. Data libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEPWSRC1 FFST Base TVOL2 Data
SERBPWSV RMF Priced TVOL2 Data
SEOYGENU BookManager READ Base TVOL2 Data
SEOYLENU BookManager READ Base TVOL2 Data
SEOYLEXS BookManager READ Base TVOL2 Data
SEUVACF DCE Base Services Base TVOL2 Data
SEUVDBRM DCE Base Services Base TVOL2 Data
SEUVEXP DCE Base Services Base TVOL2 Data
SEUVFEXP SecureWay Security Server Base TVOL2 Data
(Network Authentication and
Privacy Service component)
SEUVFHDR SecureWay Security Server Base TVOL2 Data
(Network Authentication and
Privacy Service component)
SEUVFLIB SecureWay Communications Base TVOL2 Data
Server (Network Authentication
and Privacy Service component)
SEUVHDR DCE Base Services Base TVOL2 Data
SEUVHDRK DCE Base Services Base TVOL2 Data
SEUVIDL DCE Base Services Base TVOL2 Data
SEWXSRVC LANRES Base TVOL2 Data
SEWXTLIB LANRES Base TVOL2 Data
SEWXHLTR LANRES Base TVOL2 Data
SEZADBCX Communications Server (IP Base TVOL1 Data
Services component)
SEZADBRM Communications Server (IP Base TVOL1 Data
Services component)
SEZADSIL Communications Server (IP Base TVOL1 Data
Services component)
SEZADSIM Communications Server (IP Base TVOL1 Data
Services component)
SEZANPNL Communications Server (IP Base TVOL1 Data
Services component)
SEZARNT1 Communications Server (IP Base TVOL1 Data
Services component)
SEZARNT2 Communications Server (IP Base TVOL1 Data
Services component)
SEZARNT3 Communications Server (IP Base TVOL1 Data
Services component)
SEZARNT4 Communications Server (IP Base TVOL1 Data
Services component)
SEZAROE1 Communications Server (IP Base TVOL1 Data
Services component)

Appendix E. Data Set Placement Recommendations for Target Volumes 247

 Table 23. Data libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEZAROE2 Communications Server (IP Base TVOL1 Data
Services component)
SEZAROE3 Communications Server (IP Base TVOL1 Data
Services component)
SEZATCPX Communications Server (IP Base TVOL1 Data
Services component)
SEZATELX Communications Server (IP Base TVOL1 Data
Services component)
SEZAXAWL Communications Server (IP Base TVOL1 Data
Services component)
SEZAXLD1 Communications Server (IP Base TVOL1 Data
Services component)
SEZAXLD2 Communications Server (IP Base TVOL1 Data
Services component)
SFOMDATA z/OS UNIX System Services Base TVOL1 Data
SFOMOBJ z/OS UNIX System Services Base TVOL1 Data
SGLDEXPC SecureWay Security Server Base TVOL2 Data
(LDAP Server component)
SGLDHDRC SecureWay Security Server Base TVOL2 Data
(LDAP Server component)
SGOSEFW SOMobjects RTL and ADE MULTI TVOL1 Data
SGOSIDL SOMobjects RTL and ADE MULTI TVOL2 Data
SGOSIMP SOMobjects RTL and ADE MULTI TVOL1 Data
SGOSSMPI SOMobjects RTL and ADE MULTI TVOL2 Data
SGOSSMPP SOMobjects RTL and ADE MULTI TVOL1 Data
SGOSSSIR SOMobjects RTL and ADE MULTI TVOL2 Data
| SILMDSD ILM Base TVOL2 Data
SIMWSDCK IBM HTTP Server Base TVOL2 Data
SIOAIBIN OSA/SF Base TVOL2 Data
SIOAWEUI OSA/SF Base TVOL2 Data
SIOAWIN OSA/SF Base TVOL2 Data
SISPALIB ISPF Base TVOL2 Data
SISPGENU ISPF Base TVOL2 Data
SISPGMLI ISPF Base TVOL2 Data
SISPGUI ISPF Base TVOL2 Data
SISTASGD Communications Server (SNA Base TVOL1 Data
Services component)
SISTASN1 Communications Server (SNA Base TVOL1 Data
Services component)
SISTCMIP Communications Server (SNA Base TVOL1 Data
Services component)
SISTDAT1 Communications Server (SNA Base TVOL1 Data
Services component)

248 z/OS V1R1.0 Planning for Installation

Table 23. Data libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SISTDAT2 Communications Server (SNA Base TVOL1 Data
Services component)
SISTGDMO Communications Server (SNA Base TVOL1 Data
Services component)
UADS TSO/E Base TVOL1 Data

Table 24. NLV Data libraries

DDDEF name Element or feature name Included Volume Type
with
SDFQPKSR DFSMShsm (Japanese) Base TVOL2 Data
SDGTPKSR DFSMSdfp (Japanese), Base TVOL2 Data
DFSMSdss (Japanese)
SEDGPKSR DFSMSrmm (Japanese) Base TVOL2 Data
SEOYGDEU BookManager READ (German) NLV TVOL2 Data
SEOYLDEU BookManager READ (German) NLV TVOL2 Data
SEOYGFRA BookManager READ (French) NLV TVOL2 Data
SEOYLFRA BookManager READ (French) NLV TVOL2 Data
SEOYGESP BookManager READ (Spanish) NLV TVOL2 Data
SEOYLESP BookManager READ (Spanish) NLV TVOL2 Data
SEOYGPTB BookManager READ (Brazilian NLV TVOL2 Data
Portuguese)
SEOYLPTB BookManager READ (Brazilian NLV TVOL2 Data
Portuguese)
SEOYGFRC BookManager READ (Canadian NLV TVOL2 Data
French)
SEOYLFRC BookManager READ (Canadian NLV TVOL2 Data
French)
SEOYGNLD BookManager READ NLV TVOL2 Data
(Netherlands Dutch)
SEOYLNLD BookManager READ NLV TVOL2 Data
(Netherlands Dutch)
SEOYGITA BookManager READ (Italian) NLV TVOL2 Data
SEOYLITA BookManager READ (Italian) NLV TVOL2 Data
SEOYGDAN BookManager READ (Danish) NLV TVOL2 Data
SEOYLDAN BookManager READ (Danish) NLV TVOL2 Data
SEPWBENU FFST NLV TVOL2 Data
SISPGDES ISPF (Swiss German) NLV TVOL2 Data
SISPGDEU ISPF (German) NLV TVOL2 Data
SISPGENP ISPF (Uppercase English) NLV TVOL2 Data
SISPGJPN ISPF (Japanese) NLV TVOL2 Data

Appendix E. Data Set Placement Recommendations for Target Volumes 249

EXEC Libraries
Table 25 lists the z/OS libraries that contain REXX EXECs.
Table 25. EXEC libraries
DDDEF name Element or feature name Included Volume Type
with
SAOPEXEC Infoprint Server Priced TVOL1 Exec
SASUEXEC DCE Application Support Base TVOL1 Exec
SBFSEXEC LAN Server Base TVOL1 Exec
SBFSEXEC LAN Server Base TVOL1 Exec
SBPXEXEC BCP Base TVOL1 Exec
SCBCUTL C/C++ with Debug Tool, C/C++ Priced TVOL1 Exec
without Debug Tool
SEDGEXE1 DFSMSrmm Base TVOL1 Exec
SEUVEXEC DCE Base Services Base TVOL1 Exec
SEUVFEXC SecureWay Security Server Base TVOL1 Exec
(Network Authentication and
Privacy Service component)
SEWXEXEC LANRES Base TVOL1 Exec
SGLDEXEC SecureWay Security Server Base TVOL1 Exec
(LDAP Server Component)
SGOSEXEC SOMobjects RTL and ADE MULTI TVOL1 Exec
SGOSREXX SOMobjects RTL and ADE MUTLI TVOL1 Exec
SIOEEXEC Distributed File Service Base TVOL1 Exec
SISFEXEC SDSF Priced TVOL1 Exec
SISPEXEC ISPF Base TVOL1 Exec
SISTCLI0 Communications Server (SNA Base TVOL1 Exec
Services component)

Font Libraries
Table 26 and Table 27 on page 251 list the z/OS libraries that contain fonts and data
sets required for printing.
Table 26. Font and printing libraries
DDDEF name Element or feature name Included Volume Type
with
SEOXFONT BookManager READ Base TVOL2 Font
SEOXIENU BookManager READ Base TVOL2 Font
SEOYIENU BookManager READ Base TVOL2 Font
SEWXFONT LANRES Base TVOL2 Font
SEWXPRT LANRES Base TVOL2 Font

250 z/OS V1R1.0 Planning for Installation

 Table 27. NLV font and printing libraries
DDDEF name Element or feature name Included Volume Type
with
SEOXIDAN BookManager READ (Danish) NLV TVOL2 Font
| SEOYIDAN BookManager READ (Danish) NLV TVOL2 Font
SEOXIDEU BookManager READ (German) NLV TVOL2 Font
SEOYIDEU BookManager READ (German) NLV TVOL2 Font
SEOXIESP BookManager READ (Spanish) NLV TVOL2 Font
SEOYIESP BookManager READ (Spanish) NLV TVOL2 Font
SEOXIFRA BookManager READ (French) NLV TVOL2 Font
SEOYIFRA BookManager READ (French) NLV TVOL2 Font
SEOXIFRC BookManager READ (Canadian NLV TVOL2 Font
French)
SEOYIFRC BookManager READ (Canadian NLV TVOL2 Font
French)
SEOXIITA BookManager READ (Italian) NLV TVOL2 Font
| SEOYITA BookManager READ (Italian) NLV TVOL2 Font
SEOXINLD BookManager READ NLV TVOL2 Font
(Netherlands Dutch)
SEOXIPTB BookManager READ (Brazilian NLV TVOL2 Font
Portuguese)
| SEOYINLD BookManager READ NLV TVOL2 Font
| (Netherlands Dutch)
SEOYIPTB BookManager READ (Brazilian NLV TVOL2 Font
Portuguese)

Help Libraries
Table 28 and Table 29 on page 252 list the z/OS libraries that contain help
information.
Table 28. Help and English help libraries
DDDEF name Element or feature name Included Volume Type
with
HELP BCP, DFSMSdfp, DFSMSrmm, MULTI TVOL1 Help
RMF, SDSF, SecureWay
Security Server (RACF
component), TSO/E, z/OS UNIX
System Services
HELPENP TSO/E Base TVOL1 Help
SBDTHELP BDT Base TVOL1 Help
SEDGHLP1 DFSMSrmm Base TVOL1 Help
SEZAHELP Communications Server (IP Base TVOL1 Help
Services component)
SISPHELP ISPF Base TVOL1 Help

Appendix E. Data Set Placement Recommendations for Target Volumes 251

 Table 29. NLV help libraries
DDDEF name Element or feature name Included Volume Type
with
GHELP TSO/E (German) NLV TVOL1 Help
HLPKLB DFSMSdfp (Japanese), NLV TVOL1 Help
DFSMSrmm(Japanese)
KHELP BCP, TSO/E, z/OS UNIX System NLV TVOL1 Help
Services (Japanese)
PHELP BCP, TSO/E, z/OS UNIX System NLV TVOL1 Help
Services (Simplified Chinese)

Load Module Libraries

Load module libraries (or “load libraries”), which are data sets containing load
modules, have been divided into several tables. Several tables are used because
load libraries with different characteristics must be managed differently. Some you
must put in specific places in the system-wide search order for programs, such as
in the link pack area (LPA) list. Others you can add anywhere in the search order
for programs; however, performance and virtual storage considerations will govern
appropriate placement for each installation.

The load library tables are:

v Required LPA and optional RMODE 31 LPA-eligible libraries. See Table 30.
v LPA-eligible RMODE 24 libraries. See Table 31 on page 253.
v Load libraries for change migration. See Table 32 on page 253.
v Load libraries for callable services. See Table 33 on page 254.
v Other load libraries. See Table 34 on page 255.

Some load libraries fall into more than one category and thus could be placed in
more than one table. However, we’ve selected the most likely tables for these load
libraries rather than listing them in multiple tables.

The first load library table, Table 30, lists z/OS libraries that contain required LPA
and optional RMODE 31 LPA-eligible modules. Because the only libraries listed in
this category are those that contain only RMODE 31 load modules, no virtual
storage below 16 MB is used when the libraries are included in the LPA list.
Table 30. Required LPA and optional RMODE 31 LPA-eligible load libraries
DDDEF name Element or feature name Included Volume Type
with
LPALIB BCP, DCE Base Services, MULTI TVOL1 LMOD
DFSMSdfp, DFSMSdss,
DFSMShsm, DFSMSrmm,
Encina Toolkit Executive, FFST,
Communications Server (SNA
Services component), ISPF,
SecureWay Security Server
(RACF component), SOMobjects
RTL, TIOC, TSO/E, z/OS UNIX
System Services
SCEELPA Language Environment Base TVOL1 LMOD
SEOYLPA BookManager READ Base TVOL1 LMOD

252 z/OS V1R1.0 Planning for Installation

Table 30. Required LPA and optional RMODE 31 LPA-eligible load libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEUVFLPA SecureWay Communications Base TVOL1 LMOD
Server (Network Authentication
and Privacy Service component)
SERBLPA RMF Priced TVOL1 LMOD
SFMELPA1 Tivoli Management Framework Base TVOL1 LMOD

Table 31 lists z/OS libraries that contain RMODE 24 LPA-eligible modules. All
RMODE 24 modules placed in LPA are loaded below 16 MB. Placing them in LPA
increases common area used below 16 MB and might decrease the private area
available below 16 MB. Some of the modules in these libraries need to be placed in
LPA to use a z/OS element or function. Other elements and functions can be used
without having their modules placed in LPA but perform better when their modules
are placed in LPA. For more information about placing modules in LPA and the
effects of doing so on performance and virtual storage, see z/OS MVS Initialization
and Tuning Guide.
Table 31. LPA-eligible RMODE 24 load libraries
DDDEF name Element or feature name Included Volume Type
with
ISAMLPA DFSMSdfp Base TVOL1 LMOD
SBDTLPA BDT Base TVOL1 LMOD
SEZALPA Communications Server (IP Base TVOL1 LMOD
Services component)
SIATLPA JES3 Priced TVOL1 LMOD
SICELPA DFSORT Priced TVOL1 LMOD
SISFLPA SDSF Priced TVOL1 LMOD
SISPLPA ISPF Base TVOL1 LMOD
SORTLPA DFSORT Priced TVOL1 LMOD

Table 32 lists z/OS libraries that contain load modules that are used from another
system for migration purposes. These libraries are used, or might be used, during
migration from one level of software to another. For example, the MIGLIB library
contains load modules used by IPCS to read dumps taken on one level of z/OS on
another level. Also included in this list are libraries containing WLM functions.
Table 32. Load libraries for change migration
DDDEF name Element or feature name Included Volume Type
with
MIGLIB BCP, BDT, Communications MULTI TVOL1 LMOD
Server (SNA Services
component), Cryptographic
Services (ICSF component),
DFSMSdfp, DFSMSdss,
DFSMShsm, DFSMSrmm,
SecureWay Security Server
(RACF component), SMP/E,
TSO/E

Appendix E. Data Set Placement Recommendations for Target Volumes 253

 Table 32. Load libraries for change migration (continued)
DDDEF name Element or feature name Included Volume Type
with
SCBDHENU HCD Base TVOL1 LMOD
SEZAMIG Communications Server (IP Base TVOL1 LMOD
Services component)
SHASMIG JES2 Base TVOL1 LMOD
SIATMIG JES3 Priced TVOL1 LMOD

Table 33 lists z/OS libraries that contain load modules that are used as callable
services from other elements and non-z/OS products.
Table 33. Load libraries for callable services
DDDEF name Element or feature name Included Volume Type
with
CSSLIB BCP, DFSMSdfp, Infoprint Base TVOL1 LMOD
Server
SAFHFORT Language Environment Base TVOL1 LMOD
SASUSTUB DCE Application Support Base TVOL1 LMOD
SCEEBIND Language Environment Base TVOL1 LMOD
SCEELKED Language Environment Base TVOL1 LMOD
SCEESPC Language Environment Base TVOL1 LMOD
SDMSSVM DFSMSdfp Base TVOL1 LMOD
SEUVLIB DCE Base Services Base TVOL1 LMOD
SEUVLIBK DCE Base Services Base TVOL1 LMOD
SEUVLIBS DCE Base Services Base TVOL1 LMOD
SEZACMTX Communications Server (IP Base TVOL1 LMOD
Services component)
SEZABPDM Communications Server (IP Base TVOL1 LMOD
Services component)
SEZADPIL Communications Server (IP Base TVOL1 LMOD
Services component)
SEZARPCL Communications Server (IP Base TVOL1 LMOD
Services component)
SIBMCAL2 Language Environment Base TVOL1 LMOD
SIBMCALL Language Environment Base TVOL1 LMOD
SIBMMATH Language Environment Base TVOL1 LMOD
SIBMTASK Language Environment Base TVOL1 LMOD
SIOAMMOD OSA/SF Base TVOL1 LMOD
SISPLOAD ISPF Base TVOL1 LMOD

Table 34 on page 255 lists z/OS libraries that do not fall into any of the categories in
the previous load module library tables.

254 z/OS V1R1.0 Planning for Installation

Table 34. Other load libraries
DDDEF name Element or feature name Included Volume Type
with
CHSLIB TSO/E NLV TVOL1 LMOD
CMDLIB BCP, DCE Application Services, Base TVOL1 LMOD
DFSMSdfp, TSO/E, z/OS UNIX
System Services, 3270 PC File
Transfer Program
DFQLLIB DFSMShsm Base TVOL1 LMOD
DGTLLIB DFSMSdfp, DFSMSrmm Base TVOL1 LMOD
GERLIB TSO/E NLV TVOL1 LMOD
IMAGELIB BCP, DFSMSdfp Base TVOL1 LMOD
KANLIB TSO/E NLV TVOL1 LMOD
LINKLIB BCP, Communications Server MULTI TVOL1 LMOD
(SNA Services component), DCE
Application Support, DCE Base
Services, DFSMSdfp,
DFSMSdss, DFSMShsm,
DFSMSrmm, EREP, ESCON
Director Support, HCD, ICKDSF,
Infoprint Server, IOCP,
MICR/OCR, SecureWay Security
Server, SMP/E, TSO/E, z/OS
UNIX System Services
NFSLIB Network File System Base TVOL1 LMOD
NUCLEUS BCP, Communications Server Base TVOL1 LMOD
(SNA Services component),
DFSMSdfp, ESCON Director
Support, HCD
SADMMOD GDDM Base TVOL1 LMOD
SAPPMOD1 Communications Server (SNA Base TVOL1 LMOD
Services component)
SASMMOD1 HLASM Base TVOL1 LMOD
SASMMOD2 HLASM Base TVOL1 LMOD
SBDTCMD BDT Base TVOL1 LMOD
SBDTLIB BDT Base TVOL1 LMOD
SBDTLINK BDT Base TVOL1 LMOD
SBFSLMOD LAN Server Base TVOL1 LMOD
SBFSLMOD LAN Server Base TVOL1 LMOD
SCBCCMP C/C++ with Debug Tool, C/C++ Priced TVOL1 LMOD
without Debug Tool
SCBDHENU HCD Base TVOL1 LMOD
SCBDHJPN HCD NLV TVOL1 LMOD
SCEECICS Language Environment Base TVOL1 LMOD
SCEERUN Language Environment Base TVOL1 LMOD
SCEERUN2 Language Environment Base TVOL1 LMOD
SCEERTLS Language Environment Base TVOL1 LMOD
SCLBDLL C/C++ IBM Open Class Library Base TVOL1 LMOD

Appendix E. Data Set Placement Recommendations for Target Volumes 255

 Table 34. Other load libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SCSFMOD0 Cryptographic Services (ICSF Base TVOL1 LMOD
component)
SCSFMOD1 Cryptographic Services (ICSF Base TVOL1 LMOD
component)
SCTVMOD C/C++ with Debug Tool Priced TVOL1 LMOD
SDMSSVMS DFSMSdfp Base TVOL1 LMOD
SIMOMOD1 Text Search Base TVOL1 LMOD
SEOYLOAD BookManager READ Base TVOL1 LMOD
SEPWMOD1 FFST Base TVOL1 LMOD
SEPWMOD2 FFST Base TVOL1 LMOD
SEPWMOD3 FFST Base TVOL1 LMOD
SEPWMOD4 FFST Base TVOL1 LMOD
SEQADUM C/C++ with Debug Tool Priced TVOL1 LMOD
SEQAMOD C/C++ with Debug Tool Priced TVOL1 LMOD
SERBLINK RMF Priced TVOL1 LMOD
SEUVFLNK SecureWay Communications Base TVOL1 LMOD
Server (Network Authentication
and Privacy Service component)
SEWXAUTH LANRES Base TVOL1 LMOD
SEWXLMOD LANRES Base TVOL1 LMOD
SEZADES Communications Server Base TVOL1 LMOD
SEZAKDB Communications Server Base TVOL1 LMOD
SEZAKRB Communications Server Base TVOL1 LMOD
SEZALIBN Communications Server Base TVOL1 LMOD
SEZALINK Communications Server Base TVOL1 LMOD
SEZALNK2 Communications Server Base TVOL1 LMOD
SEZAOLDX Communications Server Base TVOL1 LMOD
SEZATCP Communications Server Base TVOL1 LMOD
SEZAX11L Communications Server Base TVOL1 LMOD
SEZAXMLB Communications Server Base TVOL1 LMOD
SEZAXTLB Communications Server Base TVOL1 LMOD
SFMEMOD1 Tivoli Management Framework Base TVOL1 LMOD
SGIMLMD0 SMP/E Base TVOL1 LMOD
SGLDLNK SecureWay Security Server Base TVOL1 LMOD
(LDAP Server component)
SGOSLDA SOMobjects RTL and ADE MULTI TVOL1 LMOD
SGOSLNKL SOMobjects RTL and ADE MULTI TVOL1 LMOD
SGOSLOAD SOMobjects RTL and ADE MULTI TVOL1 LMOD
SGSKLOAD System SSL Security Level 3 Base TVOL1 LMOD
SHASLINK JES2 Base TVOL1 LMOD
SIATLIB JES3 Priced TVOL1 LMOD

256 z/OS V1R1.0 Planning for Installation

 Table 34. Other load libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SIATLINK JES3 Priced TVOL1 LMOD
SICALMOD SecureWay Security Server Priced TVOL1 LMOD
(Firewall Technologies
component)
SICELINK DFSORT Priced TVOL1 LMOD
SIFALIB BCP Base TVOL1 LMOD
SIOALMOD OSA/SF Base TVOL1 LMOD
SIOELMOD Distributed File Service Base TVOL1 LMOD
SISFLINK SDSF Priced TVOL1 LMOD
SISFLOAD SDSF Priced TVOL1 LMOD
SISPSASC ISPF Base TVOL1 LMOD
SISTCLIB Communications Server (SNA Base TVOL1 LMOD
Services component)
SISTDBUG Communications Server (SNA Base TVOL1 LMOD
Services component)
SVCLIB DFSMSdfp Base TVOL1 LMOD
VTAMLIB Communications Server (SNA Base TVOL1 LMOD
Services component)
SORTLIB DFSORT Priced TVOL1 LMOD

Macro Libraries
Table 35 and Table 36 on page 258 list the z/OS libraries that contain assembler
macros, header files, and other information identified in SMP/E as the element type
MACRO.
Table 35. Macro libraries
DDDEF name Element or feature name Included Volume Type
with
ICQABTXT TSO/E Base TVOL2 Macro
ICQILIB TSO/E Base TVOL2 Macro
MACLIB BCP, Communications Server MULTI TVOL2 Macro
(SNA Services component),
Cryptographic Services (ICSF
component), DFSMSdfp,
DFSMSdss, DFSMShsm,
DFSMSrmm, HCD, Infoprint
Server, MICR/OCR, RMF,
SMP/E, TIOC, TSO/E
MODGEN BCP, Cryptographic Services MULTI TVOL2 Macro
(ICSF component), DFSMSdfp,
DFSMSdss, DFSMShsm,
DFSMSrmm, ESCON Director
Support, HCD, SecureWay
Security Server (RACF
component), TSO/E
NFSMAC Network File System Base TVOL2 Macro

Appendix E. Data Set Placement Recommendations for Target Volumes 257

 Table 35. Macro libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SASMMAC1 HLASM Base TVOL2 Macro
SASMMAC2 HLASM Base TVOL2 Macro
SBDTMAC BDT Base TVOL2 Macro
SCEEMAC Language Environment Base TVOL2 Macro
SCEEHARP Language Environment Base TVOL2 Macro
SCEEHH Language Environment Base TVOL2 Macro
SCEEHNEI Language Environment Base TVOL2 Macro
SCEEHNET Language Environment Base TVOL2 Macro
SCEEHSYS Language Environment Base TVOL2 Macro
SEZACMAC Communications Server (IP Base TVOL2 Macro
Services component)
SEZANMAC Communications Server (IP Base TVOL2 Macro
Services component)
SEOYMC30 BookManager BUILD Priced TVOL2 Macro
SEOYMC40 BookManager BUILD Priced TVOL2 Macro
SEPWMAC1 FFST Base TVOL2 Macro
SFOMHDRS z/OS UNIX System Services Base TVOL2 Macro
SGOSH SOMobjects RTL and ADE MULTI TVOL2 Macro
SGOSHH SOMobjects RTL and ADE MULTI TVOL2 Macro
SGOSSH SOMobjects RTL and ADE MULTI TVOL2 Macro
SGOSSMPH SOMobjects RTL and ADE MULTI TVOL2 Macro
SGOSXH SOMobjects RTL and ADE MULTI TVOL2 Macro
SHASMAC JES2 Base TVOL2 Macro
SICESRCE DFSORT Priced TVOL2 Macro
SICEUSER DFSORT Priced TVOL2 Macro
SIEAHDR BCP Base TVOL2 Macro
SIATMAC JES3 Priced TVOL2 Macro
SISPMACS ISPF Base TVOL2 Macro
SISTMAC1 Communications Server (SNA Base TVOL2 Macro
Services component)

Table 36. NLV macro libraries

DDDEF name Element or feature name Included Volume Type
with
ICQGABTX TSO/E (German) NLV TVOL2 Macro
ICQKABTX TSO/E (Japanese) NLV TVOL2 Macro
ICQPABTX TSO/E (Simplified Chinese) NLV TVOL2 Macro
ICQKILIB TSO/E (Japanese) NLV TVOL2 Macro
ICQGILIB TSO/E (German) NLV TVOL2 Macro
ICQPILIB TSO/E (Simplified Chinese) NLV TVOL2 Macro

258 z/OS V1R1.0 Planning for Installation

Message Libraries
Table 37 and Table 38 on page 260 list the z/OS libraries that contain ISPF
messages and MMS source messages. The ISPF messages are on volume TVOL1,
and the MMS source messages are on TVOL2.
Table 37. Message and English message libraries
DDDEF name Element or feature name Included Volume Type
with
DFQMLIB DFSMShsm Base TVOL1 Message
DGTMLIB DFSMSdfp, DFSMSdss Base TVOL1 Message
HRFMSG SecureWay Security Server Priced TVOL1 Message
(RACF component)
ICQMLIB TSO/E Base TVOL1 Message
MSGENU BCP, Communications Server, Base TVOL2 Message
SOMobjects RTL, TSO/E, z/OS
UNIX System Services
SADMMSG GDDM Base TVOL1 Message
SAOPMENU Infoprint Server Priced TVOL1 Message
SASUMENU DCE Application Support Base TVOL1 Message
SBDTMSG BDT Base TVOL1 Message
SBFSMSGS LAN Server Base TVOL1 Message
SBFSMSGS LAN Server Base TVOL1 Message
SBLSMSG0 (BCP contains Change Migration Base TVOL1 Message
messages)
SBPXMENU BCP Base TVOL1 Message
SCBCIMG C/C++ with Debug Tool, C/C++ Priced TVOL1 Message
without Debug Tool
SCBDMENU HCD, contains Change Migration Base TVOL1 Message
messages
SCSFMSG0 Cryptographic Services (ICSF Base TVOL1 Message
component)
SEDGMENU DFSMSrmm Base TVOL1 Message
SEOYBENU BookManager READ Base TVOL1 Message
SEOYMENU BookManager READ Base TVOL1 Message
SERBMENU RMF Priced TVOL1 Message
SEUVMSG DCE Base Services Base TVOL1 Message
SEWXMLIB LANRES Base TVOL1 Message
SEWXMSGS LANRES Base TVOL1 Message
SEZAMENU Communications Server (IP Base TVOL1 Message
Services component)
SGIMMENU SMP/E Base TVOL1 Message
SGOSMSGS SOMobjects RTL and ADE MULTI TVOL1 Message
SHASMENU JES2 Base TVOL1 Message
SIATMSG0 JES3 Priced TVOL1 Message
SICEMENU DFSORT Priced TVOL1 Message

Appendix E. Data Set Placement Recommendations for Target Volumes 259

 Table 37. Message and English message libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SIOEMSGE Distributed File Service Base TVOL1 Message
SISFMLIB SDSF Priced TVOL1 Message
SISPMENU ISPF Base TVOL1 Message
SISTMSG0 Communications Server (SNA Base TVOL1 Message
Services component)

Table 38. NLV message libraries

DDDEF name Element or feature name Included Volume Type
with
DFQMKLB DFSMShsm (Japanese) NLV TVOL1 Message
DGTMKLB DFSMSdfp (Japanese), NLV TVOL1 Message
DFSMSdss (Japanese)
ICQGMLIB TSO/E (German) NLV TVOL1 Message
ICQKMLIB TSO/E (Japanese) NLV TVOL1 Message
ICQPMLIB TSO/E (Simplified Chinese) NLV TVOL1 Message
MSGCHS BCP (z/OS UNIX System NLV TVOL2 Message
Services kernel), TSO/E
(Simplified Chinese), z/OS UNIX
System Services
MSGDEU TSO/E (German) NLV TVOL2 Message
MSGENP TSO/E (Uppercase English) NLV TVOL2 Message
MSGJPN BCP, SOMobjects RTL NLV TVOL2 Message
(Japanese), TSO/E, z/OS UNIX
System Services
SAOPMESP Infoprint Server (Spanish) NLV TVOL1 Message
SAOPMJPN Infoprint Server (Japanese) NLV TVOL1 Message
SASUMJPN DCE Application Support NLV TVOL1 Message
(Japanese)
SBFSMSGJ LAN Server (Japanese) NLV TVOL1 Message
SBFSMSGJ LAN Server (Japanese) NLV TVOL1 Message
SBPXMCHS BCP (Simplified Chinese) NLV TVOL1 Message
SBPXMJPN BCP (Japanese) NLV TVOL1 Message
SCBDMJPN HCD (Japanese), contains NLV TVOL1 Message
Change Migration messages
SCEEMSGP Language Environment NLV TVOL1 Message
(Uppercase English)
SEDGMJPN DFSMSrmm (Japanese) NLV TVOL1 Message
SEOYBDAN BookManager READ (Danish) NLV TVOL1 Message
SEOYBDEU BookManager READ (German) NLV TVOL1 Message
SEOYBESP BookManager READ (Spanish) NLV TVOL1 Message
SEOYBFRA BookManager READ (French) NLV TVOL1 Message
SEOYBFRC BookManager READ (Canadian NLV TVOL1 Message
French)

260 z/OS V1R1.0 Planning for Installation

Table 38. NLV message libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEOYBITA BookManager READ (Italian) NLV TVOL1 Message
SEOYBNLD BookManager READ NLV TVOL1 Message
(Netherlands Dutch)
SEOYBPTB BookManager READ (Brazilian NLV TVOL1 Message
Portuguese)
SEOYMDAN BookManager READ (Danish) NLV TVOL1 Message
SEOYMDEU BookManager READ (German) NLV TVOL1 Message
SEOYMESP BookManager READ (Spanish) NLV TVOL1 Message
SEOYMFRA BookManager READ (French) NLV TVOL1 Message
SEOYMFRC BookManager READ (Canadian NLV TVOL1 Message
French)
SEOYMITA BookManager READ (Italian) NLV TVOL1 Message
SEOYMNLD BookManager READ NLV TVOL1 Message
(Netherlands Dutch)
SEOYMPTB BookManager READ (Brazilian NLV TVOL1 Message
Portuguese)
SEPHMSG1 BookManager READ (DBCS) NLV TVOL1 Message
SERBMJPN RMF (Japanese) NLV TVOL1 Message
SEUVMSGJ DCE Base Services (Japanese) NLV TVOL1 Message
SEWXMLBJ LANRES (Japanese) NLV TVOL1 Message
SEWXMSGJ LANRES (Japanese) NLV TVOL1 Message
SGIMMJPN SMP/E (Japanese) NLV TVOL1 Message
SGOSJMSG SOMobjects RTL and ADE NLV TVOL1 Message
(Japanese)
SHASMJPN JES2 (Japanese) NLV TVOL1 Message
SICEMJPN DFSORT (Japanese) NLV TVOL1 Message
SICHMJPN SecureWay Security Server NLV TVOL1 Message
(RACF component) (Japanese)
SIOEMSGJ Distributed File Service NLV TVOL1 Message
(Japanese)
SISPMDES ISPF (Swiss German) NLV TVOL1 Message
SISPMDEU ISPF (German) NLV TVOL1 Message
SISPMENP ISPF (Uppercase English) NLV TVOL1 Message
SISPMJPN ISPF (Japanese) NLV TVOL1 Message

Appendix E. Data Set Placement Recommendations for Target Volumes 261

Parameter Libraries (Parmlibs)
Table 39 lists the z/OS libraries that contain parameters that have been shipped by
z/OS elements. These libraries are not the libraries that have been customized by
the user.
Table 39. Parameter libraries (parmlibs)
DDDEF name Element or feature name Included Volume Type
with
PARMLIB BCP, Communications Server, Multi TVOL1 Parameter
Cryptographic Services (ICSF
component), DFSMSdfp,
DFSMSrmm, RMF
SEZADSIP Communications Server (IP Base TVOL1 Parameter
Services component)
SHASPARM JES2 Base TVOL1 Parameter
SIATPARM JES3 Priced TVOL1 Parameter

Panel Libraries
Table 40 and Table 41 on page 263 list the z/OS libraries that contain ISPF panels.
Table 40. Panel and English panel libraries
DDDEF name Element or feature name Included Volume Type
with
DFQPLIB DFSMShsm Base TVOL1 Panel
DGTPLIB DFSMSdfp, DFSMSdss Base TVOL1 Panel
HRFPANL SecureWay Security Server Priced TVOL1 Panel
(RACF component)
ICQPLIB TSO/E Base TVOL1 Panel
SADMPNL GDDM Base TVOL1 Panel
SAOPPENU Infoprint Server Priced TVOL1 Panel
SASUPENU DCE Application Support Base TVOL1 Panel
SBDTPNL0 BDT Base TVOL1 Panel
SBFSPLIB LAN Server Base TVOL1 Panel
SBFSPLIB LAN Server Base TVOL1 Panel
SBLSPNL0 BCP, Communications Server (IP Base TVOL1 Panel
Services component), and
DFSMSdfp; contain Change
Migration panels
SBPXPENU BCP Base TVOL1 Panel
SCBCPNL C/C++ with Debug Tool, C/C++ Priced TVOL1 Panel
without Debug Tool
SCBDPENU HCD, contains Change Migration Base TVOL1 Panel
panels
SCSFPNL0 Cryptographic Services (ICSF Base TVOL1 Panel
component)
SEDGPENU DFSMSrmm Base TVOL1 Panel
SEOYAENU BookManager BUILD Priced TVOL1 Panel

262 z/OS V1R1.0 Planning for Installation

Table 40. Panel and English panel libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEOYPENU BookManager READ Base TVOL1 Panel
SEPWPENU FFST Base TVOL1 Panel
SERBPENU RMF Priced TVOL1 Panel
SEUVPNL DCE Base Services Base TVOL1 Panel
SEWXPLIB LANRES Base TVOL1 Panel
SEZAPENU Communications Server (IP Base TVOL1 Panel
Services component)
SGIMPENU SMP/E Base TVOL1 Panel
SGOSPNLS SOMobjects RTL and ADE MULTI TVOL1 Panel
SHASPNL0 JES2 Base TVOL1 Panel
SIATPNL0 JES3 Priced TVOL1 Panel
SICEPENU DFSORT Priced TVOL1 Panel
SIOEPNLE Distributed File Service Base TVOL1 Panel
SISFPLIB SDSF Priced TVOL1 Panel
SISPPENU ISPF Base TVOL1 Panel
SISTPNL0 Communications Server (SNA Base TVOL1 Panel
Services component)
SISTPNL1 Communications Server (SNA Base TVOL1 Panel
Services component)

Table 41. NLV panel libraries

DDDEF name Element or feature name Included Volume Type
with
DFQPKLB DFSMShsm (Japanese) NLV TVOL1 Panel
DGTPKLB DFSMSdfp (Japanese), NLV TVOL1 Panel
DFSMSdss (Japanese)
ICQGPLIB TSO/E (German) NLV TVOL1 Panel
ICQKPLIB TSO/E (Japanese) NLV TVOL1 Panel
ICQPPLIB TSO/E (Simplified Chinese) NLV TVOL1 Panel
SAOPPESP Infoprint Server (Spanish) NLV TVOL1 Panel
SAOPPJPN Infoprint Server (Japanese) NLV TVOL1 Panel
SASUPJPN DCE Application Support NLV TVOL1 Panel
(Japanese)
SBFSPLBJ LAN Server (Japanese) NLV TVOL1 Panel
SBPXPCHS BCP (Simplified Chinese) NLV TVOL1 Panel
SBPXPJPN BCP (Japanese) NLV TVOL1 Panel
SCBDPJPN HCD (Japanese), contains NLV TVOL1 Panel
Change Migration panels
SEDGPJPN DFSMSrmm (Japanese) NLV TVOL1 Panel
SEOYADEU BookManager READ (German) NLV TVOL1 Panel
SEOYAESP BookManager READ (Spanish) NLV TVOL1 Panel

Appendix E. Data Set Placement Recommendations for Target Volumes 263

 Table 41. NLV panel libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEOYAFRA BookManager READ (French) NLV TVOL1 Panel
SEOYAFRC BookManager READ (Canadian NLV TVOL1 Panel
French)
SEOYAPTB BookManager READ (Brazilian NLV TVOL1 Panel
Portuguese)
SEOYPDAN BookManager BUILD (Danish) Priced/ NLV TVOL1 Panel
SEOYPDEU BookManager BUILD (German) Priced/ NLV TVOL1 Panel
SEOYPESP BookManager BUILD (Spanish) Priced/ NLV TVOL1 Panel
SEOYPFRA BookManager BUILD (French) Priced/ NLV TVOL1 Panel
SEOYPFRC BookManager BUILD (Canadian Priced/ NLV TVOL1 Panel
French)
SEOYPITA BookManager BUILD (Italian) Priced/ NLV TVOL1 Panel
SEOYPNLD BookManager BUILD Priced/ NLV TVOL1 Panel
(Netherlands Dutch)
SEOYPPTB BookManager BUILD (Brazilian Priced/ NLV TVOL1 Panel
Portuguese)
SEPHPNL1 BookManager READ (DBCS) NLV TVOL1 Panel
SERBPJPN RMF (Japanese) NLV TVOL1 Panel
SEUVPNLJ DCE Base Services (Japanese) NLV TVOL1 Panel
SEWXPLBJ LANRES (Japanese) NLV TVOL1 Panel
SGIMPJPN SMP/E (Japanese) NLV TVOL1 Panel
SGOSJPNL SOMobjects RTL and ADE NLV TVOL1 Panel
(Japanese)
SICEPJPN DFSORT (Japanese) NLV TVOL1 Panel
SICHPJPN SecureWay Security Server NLV TVOL1 Panel
(RACF component) (Japanese)
SIOEPNLJ Distributed File Service NLV TVOL1 Panel
(Japanese)
SISPPDES ISPF (Swiss German) NLV TVOL1 Panel
SISPPDEU ISPF (German) NLV TVOL1 Panel
SISPPENP ISPF (Uppercase English) NLV TVOL1 Panel
SISPPJPN ISPF (Japanese) NLV TVOL1 Panel

264 z/OS V1R1.0 Planning for Installation

Procedure Libraries (Proclibs)
Table 42 lists the z/OS libraries that contain procedures that have been shipped by
z/OS elements. These libraries are not the libraries that have been customized by
the user.
Table 42. Procedure libraries (proclibs)
DDDEF name Element or feature name Included Volume Type
with
PROCLIB BCP, HCD, DFSMSdfp, Infoprint MULTI TVOL1 Procedure
Server, RMF, SecureWay
Security Server (RACF
component)
SBFSPROC LAN Server Base TVOL1 Procedure
SBFSPROC LAN Server Base TVOL1 Procedure
SCBCPRC C/C++ with Debug Tool, C/C++ Priced TVOL1 Procedure
without Debug Tool
SCEEPROC Language Environment Base TVOL1 Procedure
SEOYPROC BookManager READ Base TVOL1 Procedure
SEUVPRC DCE Base Services Base TVOL1 Procedure
SICAPROC SecureWay Security Server Priced TVOL1 Procedure
(Firewall Technologies
component)
SIOEPROC Distributed File Service Base TVOL1 Procedure

Sample Libraries
Table 43 lists the z/OS libraries that contain samples, header files, and JCL jobs.
Table 43. Sample libraries
DDDEF name Element or feature name Included Volume Type
with
NFSSAMP Network File System Base TVOL2 Sample
SACBCNTL DFSMSdfp Base TVOL2 Sample
SADMOPS GDDM Base TVOL2 Sample
SADMSAM GDDM Base TVOL2 Sample
SAMPLIB BCP, Communications Server MULTI TVOL2 Sample
(SNA Services component),
Cryptographic Services (ICSF
component), DCE Base
Services, DFSMSdfp,
DFSMShsm, DFSMSrmm,
Encina Toolkit Executive, HCD,
HCM, ICKDSF, Infoprint Server,
RMF, SecureWay Security
Server (RACF component),
SMP/E, TSO/E, z/OS UNIX
System Services
SAPPSAMP Communications Server (SNA Base TVOL2 Sample
Services component)
SASMSAM1 HLASM Base TVOL2 Sample

Appendix E. Data Set Placement Recommendations for Target Volumes 265

 Table 43. Sample libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SASMSAM2 HLASM Base TVOL2 Sample
SASUSAMP DCE Application Support Base TVOL2 Sample
SBDTSAMP BDT Base TVOL2 Sample
SBFSCNFG LAN Server Base TVOL2 Sample
SBFSCSRC LAN Server Base TVOL2 Sample
SBFSSAMP LAN Server Base TVOL2 Sample
SCBCJCL C/C++ with Debug Tool, C/C++ Priced TVOL2 Sample
without Debug Tool
SCBCSAM C/C++ with Debug Tool, C/C++ Priced TVOL2 Sample
without Debug Tool
SCDSSAMP Cryptographic Services Base TVOL2 Sample
SCEESAMP Language Environment Base TVOL2 Sample
SCLBJCL C/C++ IBM Open Class Library Base TVOL2 Sample
SCLBSAM C/C++ IBM Open Class Library Base TVOL2 Sample
SCLDJCL C/C++ with Debug Tool, C/C++ Priced TVOL2 Sample
without Debug Tool
SCTVJCL C/C++ with Debug Tool Priced TVOL2 Sample
SIMOJCL1 Text Search Base TVOL2 Sample
SEPHSAMP BookManager BookServer Base TVOL2 Sample
SEPWSRC2 FFST Base TVOL2 Sample
SEQASAMP C/C++ Debug Tool Priced TVOL2 Sample
SEOYIPRF BookManager BUILD Priced TVOL2 Sample
SEOYSAMP BookManager READ Base TVOL2 Sample
SEUVFSAM SecureWay Security Server Base TVOL2 Sample
(Network Authentication and
Privacy Service component)
SEWXSAMP LANRES Base TVOL2 Sample
SEZAINST Communications Server (IP Base TVOL2 Sample
Services component)
SFMESMP1 Tivoli Management Framework Base TVOL2 Sample
SGLDSAMP SecureWay Security Server Base TVOL2 Sample
(LDAP Server component)
SGOSJCL SOMobjects RTL and ADE MULTI TVOL2 Sample
SGOSMISC SOMobjects RTL and ADE MULTI TVOL2 Sample
SGOSPROF SOMobjects RTL and ADE MULTI TVOL2 Sample
SGOSSMPC SOMobjects RTL and ADE MULTI TVOL2 Sample
SGOSSMPD SOMobjects RTL and ADE MULTI TVOL2 Sample
SGOSSMPX SOMobjects RTL and ADE MULTI TVOL2 Sample
SGSKSAMP Cryptographic Services Base TVOL2 Sample
SHASSAMP JES2 Base TVOL2 Sample
SIATSAMP JES3 Priced TVOL2 Sample

266 z/OS V1R1.0 Planning for Installation

 Table 43. Sample libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SICASAMP SecureWay Security Server Priced TVOL2 Sample
(Firewall Technologies
component)
SICEPROC DFSORT Priced TVOL2 Sample
SICESAMP DFSORT Priced TVOL2 Sample
| SILMSAMP ILM Base TVOL2 Sample
SIOASAMP OSA/SF Base TVOL2 Sample
SIOESAMP Distributed File Service Base TVOL2 Sample
SISFJCL SDSF Priced TVOL2 Sample
SISPSAMP ISPF Base TVOL2 Sample

Skeleton Libraries
Table 44 and Table 45 list the z/OS libraries that contain ISPF skeletons.
Table 44. Skeleton and English skeleton libraries
DDDEF name Element or feature name Included Volume Type
with
DGTSLIB DFSMSdfp, DFSMSdss Base TVOL1 Skeleton
HRFSKEL SecureWay Security Server Priced TVOL1 Skeleton
(RACF component)
ICQSLIB TSO/E Base TVOL1 Skeleton
SBLSKEL0 BCP and DFSMSdfp, contain Base TVOL1 Skeleton
Change Migration skeletons
SCBCSKL C/C++ with Debug Tool, C/C++ Priced TVOL1 Skeleton
without Debug Tool
SCSFSKL0 Cryptographic Services (ICSF Base TVOL1 Skeleton
component)
SEWXSLIB LANRES Base TVOL1 Skeleton
SGIMSENU SMP/E Base TVOL1 Skeleton
SGOSSKEL SOMobjects RTL and ADE MULTI TVOL1 Skeleton
SISFSLIB SDSF Priced TVOL1 Skeleton
SICESLIB DFSORT Priced TVOL1 Skeleton
SISPSENU ISPF Base TVOL1 Skeleton
SISPSLIB ISPF Base TVOL1 Skeleton

Table 45. NLV skeleton libraries

DDDEF name Element or feature name Included Volume Type
with
SISPSDES ISPF (Swiss German) NLV TVOL1 Skeleton
DGTSKLB ICKDSF (Japanese) NLV TVOL1 Skeleton
SISPSDEU ISPF (German) NLV TVOL1 Skeleton

Appendix E. Data Set Placement Recommendations for Target Volumes 267

 Table 45. NLV skeleton libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SISPSENP ISPF (Uppercase English) NLV TVOL1 Skeleton
SISPSJPN ISPF (Japanese) NLV TVOL1 Skeleton

Softcopy Libraries
Table 46 and Table 47 list the z/OS libraries that contain books, bookshelves, and
bookindexes.
Table 46. Softcopy libraries
DDDEF name Element or feature name Included Volume Type
with
SCBCDOC C/C++ with Debug Tool, C/C++ Priced TVOL2 Book
without Debug Tool
SEOXOENU BookManager READ Base TVOL2 Book
SEOX1ENU BookManager READ Base TVOL2 Book
SEOX2ENU BookManager READ Base TVOL2 Book
SEOX3ENU BookManager READ Base TVOL2 Book
SEOX4ENU BookManager READ Base TVOL2 Book
SEOYOENU BookManager BUILD Priced TVOL2 Book
SEOYSENU BookManager READ Base TVOL2 Book
SEOYXENU BookManager READ Base TVOL2 Book

Table 47. NLV softcopy libraries

DDDEF name Element or feature name Included Volume Type
with
SEOX1DAN BookManager READ (Danish) NLV TVOL2 Book
SEOX1DEU BookManager READ (German) NLV TVOL2 Book
SEOX1ESP BookManager READ (Spanish) NLV TVOL2 Book
SEOX1FRA BookManager READ (French) NLV TVOL2 Book
SEOX1FRC BookManager READ (Canadian NLV TVOL2 Book
French)
SEOX1ITA BookManager READ (Italian) NLV TVOL2 Book
SEOX1NLD BookManager READ NLV TVOL2 Book
(Netherlands Dutch)
SEOX1PTB BookManager READ (Brazilian NLV TVOL2 Book
Portuguese)
SEOX2DAN BookManager READ (Danish) NLV TVOL2 Book
SEOX2DEU BookManager READ (German) NLV TVOL2 Book
SEOX2ESP BookManager READ (Spanish) NLV TVOL2 Book
SEOX2FRA BookManager READ (French) NLV TVOL2 Book
SEOX2FRC BookManager READ (Canadian NLV TVOL2 Book
French)
SEOX2ITA BookManager READ (Italian) NLV TVOL2 Book

268 z/OS V1R1.0 Planning for Installation

Table 47. NLV softcopy libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEOX2NLD BookManager READ NLV TVOL2 Book
(Netherlands Dutch)
SEOX2PTB BookManager READ (Brazilian NLV TVOL2 Book
Portuguese)
SEOX3DAN BookManager READ (Danish) NLV TVOL2 Book
SEOX3DEU BookManager READ (German) NLV TVOL2 Book
SEOX3ESP BookManager READ (Spanish) NLV TVOL2 Book
SEOX3FRA BookManager READ (French) NLV TVOL2 Book
SEOX3FRC BookManager READ (Canadian NLV TVOL2 Book
French)
SEOX3ITA BookManager READ (Italian) NLV TVOL2 Book
SEOX3NLD BookManager READ NLV TVOL2 Book
(Netherlands Dutch)
SEOX3PTB BookManager READ (Brazilian NLV TVOL2 Book
Portuguese)
SEOX4DAN BookManager READ (Danish) NLV TVOL2 Book
SEOX4DEU BookManager READ (German) NLV TVOL2 Book
SEOX4ESP BookManager READ (Spanish) NLV TVOL2 Book
SEOX4FRA BookManager READ (French) NLV TVOL2 Book
SEOX4FRC BookManager READ (Canadian NLV TVOL2 Book
French)
SEOX4ITA BookManager READ (Italian) NLV TVOL2 Book
SEOX4NLD BookManager READ NLV TVOL2 Book
(Netherlands Dutch)
SEOX4PTB BookManager READ (Brazilian NLV TVOL2 Book
Portuguese)
SEOXODAN BookManager READ (Danish) NLV TVOL2 Book
SEOXODEU BookManager READ (German) NLV TVOL2 Book
SEOXOESP BookManager READ (Spanish) NLV TVOL2 Book
SEOXOFRA BookManager READ (French) NLV TVOL2 Book
SEOXOFRC BookManager READ (Canadian NLV TVOL2 Book
French)
SEOXOITA BookManager READ (Italian) NLV TVOL2 Book
SEOXONLD BookManager READ NLV TVOL2 Book
(Netherlands Dutch)
SEOXOPTB BookManager READ (Brazilian NLV TVOL2 Book
Portuguese)
SEOYODEU BookManager BUILD (German) Priced/ NLV TVOL2 Book
SEOYOESP BookManager BUILD (Spanish) Priced/ NLV TVOL2 Book
SEOYOFRA BookManager BUILD (French) Priced/ NLV TVOL2 Book
SEOYOFRC BookManager BUILD (Canadian Priced/ NLV TVOL2 Book
French)

Appendix E. Data Set Placement Recommendations for Target Volumes 269

 Table 47. NLV softcopy libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEOYOPTB BookManager BUILD (Brazilian Priced/ NLV TVOL2 Book
Portuguese)
SEOYSDAN BookManager READ (Danish) NLV TVOL2 Book
SEOYSDEU BookManager READ (German) NLV TVOL2 Book
SEOYSESP BookManager READ (Spanish) NLV TVOL2 Book
SEOYSFRA BookManager READ (French) NLV TVOL2 Book
SEOYSFRC BookManager READ (Canadian NLV TVOL2 Book
French)
SEOYSITA BookManager READ (Italian) NLV TVOL2 Book
SEOYSNLD BookManager READ NLV TVOL2 Book
(Netherlands Dutch)
SEOYSPTB BookManager READ (Brazilian NLV TVOL2 Book
Portuguese)
SEOYXDAN BookManager READ (Danish) NLV TVOL2 Book
SEOYXDEU BookManager READ (German) NLV TVOL2 Book
SEOYXESP BookManager READ (Spanish) NLV TVOL2 Book
SEOYXFRA BookManager READ (French) NLV TVOL2 Book
SEOYXFRC BookManager READ (Canadian NLV TVOL2 Book
French)
SEOYXITA BookManager READ (Italian) NLV TVOL2 Book
SEOYXNLD BookManager READ NLV TVOL2 Book
(Netherlands Dutch)
SEOYXPTB BookManager READ (Brazilian NLV TVOL2 Book
Portuguese)

Source Libraries
Table 48 lists the z/OS libraries that contain source code.
Table 48. Source libraries
DDDEF name Element or feature name Included Volume Type
with
SHASSRC JES2 Base TVOL2 Source
SIATSRC JES3 Priced TVOL2 Source
SISFSRC SDSF Priced TVOL2 Source

270 z/OS V1R1.0 Planning for Installation

Table Libraries
Table 49 and Table 50 list the z/OS libraries that contain ISPF tables.
Table 49. Table and English table libraries
DDDEF name Element or feature name Included Volume Type
with
DGTTLIB DFSMSdfp, DFSMSdss Base TVOL1 Table
ICQTABLS TSO/E Base TVOL1 Table
SASUTLIB DCE Application Support Base TVOL1 Table
SBFSTLIB LAN Server Base TVOL1 Table
SBLSTBL0 BCP, contains Change Migration Base TVOL1 Table
tables
SBPXTENU BCP Base TVOL1 Table
SCBDTENU HCD, contains Change Migration Base TVOL1 Table
tables
SCSFTLIB Cryptographic Services (ICSF Base TVOL1 Table
component)
SERBT RMF Priced TVOL1 Table
SERBTENU RMF Priced TVOL1 Table
SEOYTENU BookManager READ Base TVOL1 Table
SGIMTENU SMP/E Base TVOL1 Table
SIATTBL0 JES3 Priced TVOL1 Table
SICETLIB DFSORT Priced TVOL1 Table
SIMWTBL1 IBM HTTP Server Base TVOL1 Table
SISFTLIB SDSF Base TVOL1 Table
SISPTENU ISPF Base TVOL1 Table

Table 50. NLV table libraries

DDDEF name Element or feature name Included Volume Type
with
ICQGTABL TSO/E (German) NLV TVOL1 Table
ICQKTABL TSO/E (Japanese) NLV TVOL1 Table
ICQPTABL TSO/E (Simplified Chinese) NLV TVOL1 Table
SBPXTCHS BCP (Simplified Chinese) NLV TVOL1 Table
SBPXTJPN BCP (Japanese) NLV TVOL1 Table
SCBDTJPN HCD (Japanese), contains NLV TVOL1 Table
Change Migration tables
SEOYTDAN BookManager READ (Danish) NLV TVOL1 Table
SEOYTDEU BookManager READ (German) NLV TVOL1 Table
SEOYTESP BookManager READ (Spanish) NLV TVOL1 Table
SEOYTFRA BookManager READ (French) NLV TVOL1 Table
SEOYTFRC BookManager READ (Canadian NLV TVOL1 Table
French)
SEOYTITA BookManager READ (Italian) NLV TVOL1 Table

Appendix E. Data Set Placement Recommendations for Target Volumes 271

 Table 50. NLV table libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEOYTNLD BookManager READ NLV TVOL1 Table
(Netherlands Dutch)
SEOYTPTB BookManager READ (Brazilian NLV TVOL1 Table
Portuguese)
SEPHTBL1 BookManager READ (DBCS) NLV TVOL1 Table
SERBTJPN RMF (Japanese) NLV TVOL1 Table
SGIMTJPN SMP/E (Japanese) NLV TVOL1 Table
SISPTDES ISPF (Swiss German) NLV TVOL1 Table
SISPTDEU ISPF (German) NLV TVOL1 Table
SISPTENP ISPF (Uppercase English) NLV TVOL1 Table
SISPTJPN ISPF (Japanese) NLV TVOL1 Table

Text Libraries
Table 51 and Table 52 list the z/OS libraries that contain text.
Table 51. Text libraries
DDDEF name Element or feature name Included Volume Type
with
SEOY1ENU BookManager BUILD Priced TVOL2 Text
SEOY2ENU BookManager BUILD Priced TVOL2 Text
SEOY4ENU BookManager BUILD Priced TVOL2 Text

Table 52. NLV text libraries

DDDEF name Element or feature name Included Volume Type
with
SEOY1DEU BookManager BUILD (German) Priced/ NLV TVOL2 Text
SEOY1ESP BookManager BUILD (Spanish) Priced/ NLV TVOL2 Text
SEOY1FRA BookManager BUILD (French) Priced/ NLV TVOL2 Text
SEOY1FRC BookManager BUILD (Canadian Priced/ NLV TVOL2 Text
French)
SEOY1PTB BookManager BUILD (Brazilian Priced/ NLV TVOL2 Text
Portuguese)
SEOY2DEU BookManager BUILD (German) Priced/ NLV TVOL2 Text
SEOY2ESP BookManager BUILD (Spanish) Priced/ NLV TVOL2 Text
SEOY2FRA BookManager BUILD (French) Priced/ NLV TVOL2 Text
SEOY2FRC BookManager BUILD (Canadian Priced/ NLV TVOL2 Text
French)
SEOY2PTB BookManager BUILD (Brazilian Priced/ NLV TVOL2 Text
Portuguese)
SEOY4DEU BookManager BUILD (German) Priced/ NLV TVOL2 Text
SEOY4ESP BookManager BUILD (Spanish) Priced/ NLV TVOL2 Text
SEOY4FRA BookManager BUILD (French) Priced/ NLV TVOL2 Text

272 z/OS V1R1.0 Planning for Installation

Table 52. NLV text libraries (continued)
DDDEF name Element or feature name Included Volume Type
with
SEOY4FRC BookManager BUILD (Canadian Priced/ NLV TVOL2 Text
French)
SEOY4PTB BookManager BUILD (Brazilian Priced/ NLV TVOL2 Text
Portuguese)

Appendix E. Data Set Placement Recommendations for Target Volumes 273

274 z/OS V1R1.0 Planning for Installation
Appendix F. Making a Copy of Your System Software
(Cloning)
At some point after you have finished installing z/OS you will probably need to
make a copy of it (“clone” it). Some reasons are:
v For backup. A backup copy is a copy of the z/OS product set (z/OS and other
products you have installed on the same set of volumes using the same SMP/E
zones) that:
– Resides on different volumes with different volume labels
– Includes copies of the associated SMP/E zones with different names that
point to the data sets on the new volumes
– Includes copies of the associated catalogs with different names
– Can be IPLed in place of the original copy when the necessary setup has
been done after making the copy.
v To move the software to another system.
v To create another SMP/E-serviceable copy for installing service or other
products.

This appendix describes how to make a copy of the system software in the z/OS
product set on different DASD volumes with different volume serials. To make a
copy, you must perform a number of tasks. The number and nature of the tasks
depend on how your system has been configured. In addition, many of the tasks
can be done using different techniques, and differing local standards and practices
add more variations to the process. Some of the factors that can affect the way you
copy your system are:
v Catalog-sharing boundaries (such as whether shared master catalogs are in use)
v Use of direct, indirect, or extended indirect catalog referencing
v Local versus central maintenance
v System software volume-sharing boundaries and their relationship to catalog and
sysplex boundaries
v Naming conventions
v Whether new data sets affect the existing environment
v Testing and migration procedures
v Whether the copy will be used in an existing environment or a new one.

The information in this appendix is based on the system layout described in

“Recommended Data Set Placement” on page 170. However, you should find this
appendix useful even if your system is configured differently. The techniques shown
here are designed to minimize the amount of work required to migrate software into
existing environments that use the recommended system layout. They will make a
complete copy of the software that can be serviced using SMP/E.

The topics in this appendix, which correspond to the steps involved in making a
copy of your system software, are:
v “Choosing Names” on page 276
v “Initializing the New Volumes” on page 277
v “Setting Up SMS” on page 278
v “Defining New Catalogs and CSI Data Sets” on page 278
v “Copying the Software Data Sets” on page 279

© Copyright IBM Corp. 1996, 2001 275

 v “Copying the SMP/E Zones” on page 280
v “Making the Copy Usable” on page 282
v “Testing” on page 282
v “Migrating to Another System” on page 282

This appendix refers to the following jobs in SYS1.SAMPLIB:

v IEACLNIN, which initializes volumes
v IEACLNSM, which converts an HFS volume to SMS management
v IEACLNCS, which defines catalogs and creates CSI data sets
v IEACLNCV, which copies volumes
v IEACLNMT, which creates a mount point directory and mounts the HFS at it
v IEACLNCZ, which copies zones

If you are migrating your software to another system and you can use the same
volume, catalog, and data set names, you need only one of the procedures in this
appendix. Use the full-volume physical dumps and restores to make the copy, and
then follow the steps in “Migrating to Another System” on page 282.

Choosing Names
The first step in preparing to make a copy of your system is choosing new names.
You must choose new names for:
v The new DASD volumes that will be the target of the copy:
– The IPL volume (TVOL1)
– The second and any other target library volumes (TVOL2-n)
– The HFS volume
– The DLIB volumes, if you are also copying the distribution libraries

Choose names that allow you to define system symbols for each target volume
based on the name of the IPL volume. For example, the name for TVOL1 might
be OS260 and the name for TVOL2 might be OS260X, using the scheme OSrrr for
TVOL1 and OSrrrX for TVOL2, where rrr is a level identifier and the system
symbols are &SYSR2.='&SYSR1(1:5).X'.
v User catalogs to manage the VSAM files, HFS files, and DLIB data sets. These
catalogs are:
– One for the second target library volume (TVOL2), to own the target zone CSI
data set and any MMS-compiled VSAM files
– One for the HFS volume, to own the HFS data sets
– One for the first DLIB volume, to catalog the distribution libraries.

Choose names using a convention that avoids having two catalogs with the same
name in the same catalog environment at the same time. IBM recommends that
you choose a naming convention based on the volume serial of a TVOLn
volume. You should pick one or more installation-wide high-level qualifiers and
reserve them for catalog naming. This prevents catalog names from conflicting
with any existing alias entry names. One example of such a convention is
USERCAT.volser. In this example, the high-level qualifier USERCAT is reserved
for naming catalogs.
v The SMP/E CSI data sets and SMP/E zones:
– Target zone CSI data set
– DLIB zone CSI data set
– Target zone
– DLIB zone

276 z/OS V1R1.0 Planning for Installation

 You should choose the CSI data set names using different high-level qualifiers
because they will be cataloged in different catalogs. You must pick
currently-unused high-level qualifiers to be able to define them as aliases and
access the CSI data sets without using JOBCAT or STEPCAT. IBM recommends
that you choose a high-level qualifier for CSI data set names based on the
volume serial of a TVOLn volume. For example, you might use OS26TZ.CSI as
the name of a target zone CSI data set.
v MMS data sets.
If you use MMS data sets, you should choose their names using different
high-level qualifiers because they will be cataloged in different catalogs. You
must pick currently-unused high-level qualifiers to be able to define them as
aliases and access the MMS data sets. The high-level qualifier you choose can
be defined as a system symbol to avoid other parmlib changes.
IBM recommends that you choose a high-level qualifier for MMS data sets that is
derived from the volume serial of a TVOLn volume. If you do, you will be able to
define a single symbol for all MMS data sets in the z/OS product set that will not
need to be updated in the future. For example, if:
– the MMS data sets are placed on TVOL2
– and the name of TVOL2 is derived from the name of TVOL1 (by defining a
system symbol for TVOL2 based on a substring of the system-supplied
symbol for the IPL volume label)
– and you choose a high-level qualifier based on the name of TVOL2 for the
MMS data sets

then you can define a system symbol based on the name of TVOL2 in an
IEASYMxx member of parmlib. This symbol would be resolved to the high-level
qualifier you used, and could be used as part of the data set name in an
MMSLSTxx member of parmlib to allocate the MMS data sets associated with
the IPL volume.
v HFS data sets.
HFS data sets can be optionally SMS-managed. They must be cataloged and
their names must be unique within the file system structure in order to be
mounted. In the IBM cloning samples, the HFS data sets are SMS-managed.
v Distribution libraries.
You can choose to use volume serials on the DLIB zone DDDEFs, or to name
the data sets differently and locate them through the user catalog on the first
DLIB volume. If you choose to locate them by name using the catalog, you must
rename them using a new high-level qualifier.

Initializing the New Volumes

To initialize the new volumes, use ICKDSF. The IEACLNIN job in SYS1.SAMPLIB
uses ICKDSF input as follows to perform a medial initialization (on most DASD
types) for each new volume:
INIT -
NOCHECK -
NOINDEX -
PURGE -
UNIT(0000) -
VALIDATE -
VERIFY(oldser) -
VOLID(newtv1) -
VTOC(0,1,44)

Appendix F. Making a Copy of Your System Software (Cloning) 277

 Note: The size and location of the VTOCs specified will be changed on some of
the new volumes by full-volume copy operations when sizes and locations of
the VTOCs on the volumes they are copied from are different. The VTOC
size and location remains as specified for new volumes that are not copied
using full-volume physical copy.

Because system software target volumes are crucial to system operation, IBM
recommends that you perform surface checking on all such volumes. Different
procedures are used for different DASD types. For more information about surface
checking, see Device Support Facilities User’s Guide and Reference.

Setting Up SMS
Because SMS must be active and the HFS data sets must be cataloged in order to
mount the HFS, some SMS setup is needed to prepare for copying the HFS
volumes. The IEACLNSM job in SYS1.SAMPLIB does a DFSMSdss CONVERTV to
convert the volume to an SMS-managed volume. The first step creates a VTOC
index, which is required for all SMS-managed volumes:
BUILDIX -
DDNAME(DASD) -
IXVTOC

The second step converts the volume to an SMS-managed volume:

CONVERTV -
DDNAME(DASD) -
SMS

Access to the STGADMIN.ADR.CONVERTV facility class profile or to a higher-level

profile (such as STGADMIN.*) is required to run CONVERTV.

Defining New Catalogs and CSI Data Sets

The next step in making the copy is allocating new user catalogs to manage the
VSAM files, HFS files, and distribution libraries. The IEACLNCS job in
SYS1.SAMPLIB defines three user catalogs:
v A user catalog on TVOL2 to own the SMP/E target zone CSI data set and MMS
data sets
v A user catalog on the HFS volume to own the HFS
v A user catalog on the first DLIB volume to manage the DLIB zone CSI data set
and distribution libraries.

The user catalogs are defined using IDCAMS commands, as shown below. These
catalogs will not contain a large number of entries, so it is not necessary to allocate
very much space for them.
DEFINE -
USERCATALOG -
(NAME(usercat.newtv2) -
CYLINDERS(1 1) -
VOLUME(newtv2) -
ICFCATALOG)

Alias entries are defined to relate the new high-level qualifiers you chose for the
VSAM files, HFS files, and distribution libraries to the new catalogs. This will
establish the new catalogs as the owning catalogs for the VSAM and HFS files,
making the volumes with their catalogs and data sets portable to other systems.
The aliases are defined this way:

278 z/OS V1R1.0 Planning for Installation

 DEFINE -
ALIAS -
(NAME(newtarg) -
RELATE (usercat.newtv2))

Next, new CSI data sets are defined, using the source data sets as models for
allocating the new ones, as shown here:
DEFINE -
CLUSTER -
(NAME(newtarg.csi) -
MODEL(oldtarg.csi) -
VOLUMES(newtv2))

Because SMP/E CSI data sets must be initialized with the GIMZPOOL record
before SMP/E can process them, both must be primed using the REPRO
command:
REPRO -
INFILE(ZPOOL) -
OUTDATASET(newtarg.csi)

Copying the Software Data Sets

The previous steps created the environment needed to copy the data on the z/OS
volumes. All the data except that in the SMP/E CSIs is copied using DFSMSdss.
The job in SYS1.SAMPLIB for copying volumes is IEACLNCV.

The PARALLEL parameter is used to let DFSMSdss multitask the copy and dump
operations so they can be done more quickly. The SERIAL parameter is used to
make sure that the HFS volume dump completes before the HFS volume restore.

Access to the STGADMIN.ADR.STGADMIN.COPY facility class profile, or to a

higher-level profile (such as STGADMIN.*), is required to use the ADMINISTRATOR
keyword. If you do not use the ADMINISTRATOR keyword, UPDATE or higher
access to all the data sets on the volume is required.

The data on each volume is copied differently, depending on the volume being
copied and its content:
v Because TVOL1 has no VSAM or SMS-managed data sets, it can be copied
using full-volume physical copy.

Note: Physical copy preserves the IPL text on TVOL1, so no steps are needed
to replace it. If you are copying the system software between volumes on
different device types, you will need to use copy-by-data-set rather than
full-volume copy. Copy-by-data-set does not preserve the IPL text, so you
have to replace the IPL text whenever you copy TVOL1 to a different
device type.
v TVOL2 contains a user catalog and VSAM data sets (the target zone CSI data
set and any MMS-compiled data sets). It is copied by data set, excluding the
user catalog, VTOC Index, SMP/E target zone CSI data set, and VSAM Volume
Data Set (VVDS). The VSAM data sets are renamed using the new high-level
qualifiers you chose.
The SMP/E CSI data sets are copied later using SMP/E commands.

Note: The RECATALOG parameter catalogs all the data sets during the copy of
TVOL2 in the user catalog on TVOL2. However, only the SMP/E CSI,
SMP/E non-VSAM, and MMS-compiled data sets will actually be accessed

Appendix F. Making a Copy of Your System Software (Cloning) 279

 using this catalog, because extended indirect cataloging is used to find
them in the normal catalog search order.
v The HFS volume cannot be copied because DFSMSdss does not support logical
copy for an HFS. Instead, it is dumped to a temporary dump data set on DASD
and restored. It is renamed using the new high-level qualifier you chose earlier
during the restore operation, and cataloged in the user catalog on the volume.
Remember that all HFS data sets that are associated with a particular system
should be cloned. This includes the root as well as the /etc and /var file systems.
When your clone system is IPLed, you will also need unique /dev and /tmp file
systems.
v The first DLIB volume is copied by data set, similar to the way TVOL2 is copied,
because it contains the DLIB zone CSI data set and user catalog. Its data sets
are renamed during the copy using the new high-level qualifier you chose. If you
prefer not to rename the data sets, remove the RENAMEU parameter.
v The second DLIB volume is copied by data set. Its data sets are renamed during
the copy using the new high-level qualifier you chose. If you prefer not to rename
the data sets, remove the RENAMEU parameter.

Note: The RECATALOG parameter catalogs all the data sets during the copies
of the DLIB volumes in the user catalog on DLIB1. However, only the
SMP/E CSI and SMP/E non-VSAM data sets will actually be accessed
using this catalog.

If you’re making a clone for the purpose of creating an SMP/E-serviceable copy,

make the HFS files accessible by mounting the filesystems at the mountpoint you
chose. To do this, you must first create the directory by issuing the MKDIR
command. For example, you could issue mkdir /service to create a directory
named SERVICE. Then, you could issue MOUNT commands from a TSO user ID
to mount the filesystems. The user ID must have superuser authority (either UID(0)
or READ access to an applicable RACF UNIXPRIV class profile) to issue the
MOUNT command. For more information about the MKDIR and MOUNT
commands, see z/OS UNIX System Services Command Reference. For a sample
job, see IEACLNMT in SYS1.SAMPLIB.

Copying the SMP/E Zones

The SMP/E zones are copied using ZONECOPY rather than IDCAMS REPRO so
that both the zones and the CSI data sets can be renamed. This makes it possible
to use both the old and new target and DLIB zones with a single global zone. The
IEACLNCZ job in SYS1.SAMPLIB shows how to do a ZONECOPY.

Before the zones are copied, the global zone’s ZONEINDEX entry must be updated
with the new CSI data set and zone names:
SET BDY(GLOBAL) .

UCLIN .
ADD GLOBALZONE
ZONEINDEX((newtgt,newtarg.csi,TARGET),
(newdlb,newdlib.csi,DLIB)) .
ENDUCL .

Next, the zones are copied using ZONECOPY commands, as shown below.
Because the SMP/E boundary is already set to do the ZONECOPY, the ZONEEDIT
commands to change the DDDEFs to reflect new volume serials (and data set

280 z/OS V1R1.0 Planning for Installation

names, for the DLIB zone) can be issued at the same time. This example shows
the ZONECOPY and ZONEEDIT for the target zone; similar commands are used for
the DLIB zone:
SET BDY(newtgt change (OLDTGT) INTO (NEWTGT) to (oldtgt) INTO (newtgt)) .

ZONECOPY
(OLDTGT) INTO (NEWTGT) .

UCLIN.
REP TARGETZONE(NEWTGT) RELATED(NEWDLB) .
ENDUCL.

ZONEEDIT DDDEF .
CHANGE UNIT(*,SYSALLDA) .
CHANGE VOLUME(OLDTV1,NEWTV1) .
CHANGE VOLUME(OLDTV2,NEWTV2) .
CHANGE VOLUME(OLDDL1,NEWDL1) .
CHANGE VOLUME(OLDDL2,NEWDL2) .
/* UNCOMMENT THE NEXT LINE IF YOU CATALOG YOUR DLIB DATA SETS
CHANGE DATASET(OLDDLB,NEWDLB) .
*/
ENDZONEEDIT .

REP TARGETZONE(newtgt) RELATED(newdlb) is an optional command, to be

added only if the DLIBs and DLIB zone will be copied at the same time as the
target libraries and zone.

As a rule, you should not install service or products on the same copy of the
system software that the system is using. This includes those parts of the system
software that reside in an HFS. The way to update a copy of an HFS is to mount it
on another mount point. The system will continue to use its own level of the HFS,
and the copy will be accessible using the other mount point.

Before making any updates to the copy with SMP/E, you should change the HFS
path DDDEFs to point to another directory, usually called a service directory, and
mount the copy’s HFS filesystems on that directory’s mount point. This assures that
SMP/E will update the correct HFS when products and service are installed.

To change the DDDEFs, use the SMP/E ZONEEDIT command. For example, the
following commands will add /service to the beginning of all HFS paths:
SET BDY(NEWTGT) .

ZONEEDIT DDDEF .

CHANGE PATH(*,'/service'*) .

ENDZONEEDIT .

Note that the HFS remains usable for backup no matter where the DDDEFs point. If
you IPL using a BPXPRMxx member that mounts the copy’s HFSs at their normal
mountpoints (not the service mountpoints), the system will function normally. The
DDDEFs only affect where SMP/E searches for or stores parts that reside in an
HFS.

For more information about servicing elements in the HFS, see the topic about
installing service with the Hierarchical File System in z/OS UNIX System Services
Planning.

Appendix F. Making a Copy of Your System Software (Cloning) 281

Making the Copy Usable
Once you have completed the preceding steps, you have a backup copy of the
z/OS product set. If you have used the recommended system layout (described in
“Recommended Data Set Placement” on page 170), used indirect and extended
indirect cataloging (described in “Using Indirect Catalog Entries” on page 184), used
a consistent TVOLn naming convention that lets you use system symbols to derive
the names of TVOL2-n, and avoided the use of explicit volume serials in the link,
LPA, and APF lists, there should be very few other actions you need to take to use
the copy as a backup suitable for IPL. Because the SMP/E zones were copied with
the software, you can also query the level of any SMP/E-maintained part of this
copy of the system at any time.

The one thing you will have to do is create another BPXPRMxx member of parmlib
to point to the new HFS data sets.

If you have not followed the recommendations mentioned above, you will have
additional work to do. For example:
v If you didn’t use indirect cataloging, you need to create a copy of the master
catalog to IPL with the new backup volumes. For information about creating a
copy of your master catalog, see z/OS DFSMS: Managing Catalogs.
v If you coded volume serials for z/OS product set volumes in the link, LPA, or APF
lists, you need to create new parmlib members.
v If your clone is for a new image, you need to copy image-related data sets. See
“Image-Related Data Sets” on page 177 for information.
v If your clone is for a sysplex, you need to copy sysplex-related data sets. See
“Cluster-Related Data Sets” on page 179 for information.

Testing
Never assume that the backup copy will work until it has been tested. Schedule a
test time on the system to be backed up to make sure that the copying process was
successful and that backup procedures work. If this isn’t possible, a slightly more
risky alternative is using a test system with copies of the production system’s
operational data sets.

Migrating to Another System

Note!

This section only lists actions you need to take to move a copy of software
from one system to another. It does not list the actions needed to install and
migrate new levels of software. See other sections of this book, z/OS MVS
Migration, and other z/OS elements’ installation planning and migration books
for that information.

If you want to move the copy to another system that also uses the recommended
system layout, there are only a few things left to do:
v If you chose to SMS-manage your HFS data sets, define the HFS volume to
SMS on the other system if the volume is not in the same SMS-plex. You can
define the HFS volume using ISMF, the same way it was defined in “Setting Up
SMS” on page 278.

282 z/OS V1R1.0 Planning for Installation

v Import the user catalogs and define the data set aliases if the target system for
migration is not sharing its master catalog with the system from which you made
the copy.
v Create a new BPXPRMxx member of parmlib on the other system to point to the
copy’s HFS files.
Copy the active BPXPRMxx member of parmlib to a new member. Also, update
the ROOT FILESYSTEM and MOUNT FILESYSTEM statements to point to the
copy’s HFS data sets.
v Install any system-specific usermods. Also, install any system-specific exits that
cannot be installed separately from the system software.
v Specify the master catalog name in LOADxx rather than in SYSCATxx members
of the NUCLEUS data set. This is IBM’s recommendation. However, if you
choose to specify it using SYSCATxx, you must add or update this member to
reflect the name of the intended image’s master catalog.

To import the user catalogs and define the aliases, use IDCAMS:
IMPORT -
CONNECT -
OBJECTS((usercat.newhfs VOLUMES(newhfs) DEVT(3390)))

IMPORT -
CONNECT -
OBJECTS((usercat.newtv2 VOLUMES(newtv2) DEVT(3390)))

IMPORT -
CONNECT -
OBJECTS((usercat.newdl1 VOLUMES(newdl1) DEVT(3390)))

DEFINE -
ALIAS -
(NAME(hfsnew) -
RELATE (usercat.newhfs))

DEFINE -
ALIAS -
(NAME(newtarg) -
RELATE (usercat.newtv2))

DEFINE -
ALIAS -
(NAME(newmms) -
RELATE (usercat.newtv2))

DEFINE -
ALIAS -
(NAME(newdlib) -
RELATE (usercat.newdl1))

Appendix F. Making a Copy of Your System Software (Cloning) 283

284 z/OS V1R1.0 Planning for Installation
Appendix G. Notices
This information was developed for products and services offered in the U.S.A. IBM
may not offer the products, services, or features discussed in this document in other
countries. Consult your local IBM representative for information on the products and
services currently available in your area. Any reference to an IBM product, program,
or service is not intended to state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However,
it is the user’s responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you any
license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
USA

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply to
you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this publication at any
time without notice.

Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:
IBM Corporation
Mail Station P300
2455 South Road
Poughkeepsie, NY 12601-5400
USA

© Copyright IBM Corp. 1996, 2001 285

 Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.

If you are viewing this information softcopy, the photographs and color illustrations
may not appear.

Trademarks
The following terms are trademarks of the IBM Corporation in the United States,
other countries, or both:
v 3090
v 3890/XP
v AD/Cycle
v Advanced Function Printing
v AFP
v AIX
v AnyNet
v APL2
v APPN
v AT
v BookManager
v BookMaster
v C/MVS
v C/370
v CallPath
v CallPath CICS/MVS
v CICS
v CICS/ESA
v CICS/MVS
v CICSPlex
v COBOL/370
v DataPropagator
v DataRefresher
v DB2
v DB2 OLAP Server
v DB2 Universal Database
v DFS
v DFSMS/MVS
v DFSMSdfp
v DFSMSdss
v DFSMShsm
v DFSMSrmm
v DFSORT
v DisplayWrite
v DPI
v e-business
v Encina
v Enterprise Storage Server
v Enterprise System/3090
v Enterprise System/4381
v Enterprise System/9000

286 z/OS V1R1.0 Planning for Installation

v Enterprise Systems Architecture/370
v ES/3090
v ES/4381
v ES/9000
v ESCON
v ^
v EtherStreamer
v Extended Services
v FFST
v FICON
v First Failure Support Technology
v FlowMark
v FunctionPac
v GDDM
v geoManager
v IBM
v IBMLink
v ImagePlus
v IMS
v IMS/ESA
v Infoprint
v Intelligent Miner
v Intelligent Printer Data Stream
v IP PrintWay
v IPDS
v Language Environment
v LANStreamer
v Magstar
v Micro Channel
v MQSeries
v Multiprise
v MVS
v MVS/ESA
v Net.Data
v NetSpool
v Network Station
v Nways
v OfficeVision/MVS
v Open Class
v OpenEdition
v OS/2
v OS/390
v Parallel Sysplex
v PR/SM
v Print Services Facility
v Processor Resource/Systems Manager
v ProductPac
v PS/2
v QMF
v RACF
v RAMAC
v Resource Measurement Facility
v RETAIN
v RISC System/6000
v RMF
v RS/6000

Appendix G. Notices 287

 v S/370
v S/390
v S/390 Parallel Enterprise Server
v SAA
v SecureWay
v ServicePac
v SOM
v SOMobjects
v SP
v SQL/DS
v StorWatch
v Sysplex Timer
v System/370
v System/390
v SystemView
v TURBOWAYS
v VisualAge
v VisualGen
v VisualLift
v VM/ESA
v VSE/ESA
v VTAM
v WebSphere
v WIN-OS/2
v XT
v z/Architecture
v z/OS
v z/VM
v zSeries

The e-business logo is a trademark of IBM.

Lotus is a trademark of Lotus Development Corporation in the United States, other

countries, or both.

NetView, Tivoli, Tivoli Management Framework, Tivoli Manager, TME, and TME 10
are trademarks of Tivoli Systems Inc. in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.

Pentium is a trademark of Intel Corporation in the United States, other countries, or

both. (For a complete list of Intel trademarks, see
http://www.intel.com/tradmarx.htm.)

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Other company, product, and service names may be trademarks or service marks
of others.

288 z/OS V1R1.0 Planning for Installation

Index
Special Characters application development environment
migrating 138
/etc directory
Application Enabling Technology (AET)
migrating files 138
no longer in OS/390 20
Application Map Generator
minimum version and release requirements 218
Numerics Application Support Facility V3
3172 Offload minimum version and release requirements 218
no longer in OS/390 20 Application Test Collection
3270 PC File Transfer Program minimum version and release requirements 218
element in z/OS 20 automatic tape switching
hardware requirements 239 hardware requirements 229
migration path from OS/390 R10 to z/OS V1R1 137
migration path from OS/390 R6 to z/OS V1R1 99
migration path from OS/390 R7 to z/OS V1R1 110
migration path from OS/390 R8 to z/OS V1R1 121
B
backout
migration path from OS/390 R9 to z/OS V1R1 130
in z/OS 160
software requirements 215
requires coexistence service and actions 72
4700 FCS Controller Resource Manager
base elements
minimum version and release requirements 217
introduction to 1
4700 Host Support Program
list of 3
minimum version and release requirements 217
removed from OS/390 and z/OS 20
64-bit
to be removed from z/OS 23
introduction 1
Basic Tape Library Support
real storage support in migration scenarios 83
minimum version and release requirements 218
required mode on z900 63
Batch Print Capability
requires z900 server 229
part of Infoprint Server 14
Batchpipes
minimum version and release requirements 218
A BCP
ACF/NCP element in z/OS 4
minimum version and release requirements 217 hardware requirements 229
ACF/SSP migration path from OS/390 R10 to z/OS V1R1 130
minimum version and release requirements 217 migration path from OS/390 R6 to z/OS V1R1 89
ACF/TCAM migration path from OS/390 R7 to z/OS V1R1 99
minimum version and release requirements 217 migration path from OS/390 R8 to z/OS V1R1 110
AD/Cycle C/370 migration path from OS/390 R9 to z/OS V1R1 121
minimum version and release requirements 217 software requirements 201
AD/Cycle Dictionary Services/MVS BDT
minimum version and release requirements 217 element in z/OS 4
AET hardware requirements 230
no longer in OS/390 20 migration path from OS/390 R10 to z/OS V1R1 130
AFP Century Schoolbook Font migration path from OS/390 R6 to z/OS V1R1 89
minimum version and release requirements 217 migration path from OS/390 R7 to z/OS V1R1 99
AFP Font Collection migration path from OS/390 R8 to z/OS V1R1 110
minimum version and release requirements 217 migration path from OS/390 R9 to z/OS V1R1 121
AFP Math and Science Font software requirements 202
minimum version and release requirements 217 BDT File-to-File
AFP Toolbox for MVS feature in z/OS 4
minimum version and release requirements 217 hardware requirements 230
alternate base migration path from OS/390 R10 to z/OS V1R1 131
description 60 migration path from OS/390 R6 to z/OS V1R1 89
APL2 migration path from OS/390 R7 to z/OS V1R1 99
minimum version and release requirements 217 migration path from OS/390 R8 to z/OS V1R1 110
APL2 Application Environment migration path from OS/390 R9 to z/OS V1R1 121
minimum version and release requirements 218 software requirements 202
APL2 Fonts BDT SNA NJE
minimum version and release requirements 217 feature in z/OS 4

© Copyright IBM Corp. 1996, 2001 289

BDT SNA NJE (continued)
hardware requirements 230
C
C/370 Compiler
migration path from OS/390 R10 to z/OS V1R1 131
minimum version and release requirements 218
migration path from OS/390 R6 to z/OS V1R1 89
C/370 Library
migration path from OS/390 R7 to z/OS V1R1 99
minimum version and release requirements 218
migration path from OS/390 R8 to z/OS V1R1 111
C/C++
migration path from OS/390 R9 to z/OS V1R1 121
migration actions 142
software requirements 202
C/C++ IBM Open Class Library
block sizes element in z/OS 5
for z/OS data sets 186 hardware requirements 230
BookManager BookServer migration path from OS/390 R10 to z/OS V1R1 131
element in z/OS 4 migration path from OS/390 R6 to z/OS V1R1 90
hardware requirements 230 migration path from OS/390 R7 to z/OS V1R1 100
migration actions 138 migration path from OS/390 R8 to z/OS V1R1 111
migration path from OS/390 R10 to z/OS V1R1 131 migration path from OS/390 R9 to z/OS V1R1 122
migration path from OS/390 R6 to z/OS V1R1 90 software requirements 203
migration path from OS/390 R7 to z/OS V1R1 100 C/C++ Productivity Tools
migration path from OS/390 R8 to z/OS V1R1 111 minimum version and release requirements 218
migration path from OS/390 R9 to z/OS V1R1 122 C/C++ with Debug Tool
minimum version and release requirements 218 enabling 156
software requirements 203 feature in z/OS 5
hardware requirements 230
BookManager BUILD migration path from OS/390 R10 to z/OS V1R1 131
enabling 156 migration path from OS/390 R6 to z/OS V1R1 90
feature in z/OS 5 migration path from OS/390 R7 to z/OS V1R1 100
hardware requirements 230 migration path from OS/390 R8 to z/OS V1R1 111
migration path from OS/390 R10 to z/OS V1R1 131 migration path from OS/390 R9 to z/OS V1R1 122
migration path from OS/390 R6 to z/OS V1R1 90 software requirements 203
migration path from OS/390 R7 to z/OS V1R1 100 C/C++ without Debug Tool
migration path from OS/390 R8 to z/OS V1R1 111 enabling 156
migration path from OS/390 R9 to z/OS V1R1 122 feature in z/OS 5
minimum version and release requirements 218 hardware requirements 230
software requirements 203 migration path from OS/390 R10 to z/OS V1R1 131
BookManager READ migration path from OS/390 R6 to z/OS V1R1 90
element in z/OS 5 migration path from OS/390 R7 to z/OS V1R1 100
hardware requirements 230 migration path from OS/390 R8 to z/OS V1R1 111
migration path from OS/390 R10 to z/OS V1R1 131 migration path from OS/390 R9 to z/OS V1R1 122
migration path from OS/390 R6 to z/OS V1R1 90 software requirements 203
migration path from OS/390 R7 to z/OS V1R1 100 CallPath/CICS
migration path from OS/390 R8 to z/OS V1R1 111 minimum version and release requirements 218
migration path from OS/390 R9 to z/OS V1R1 122 CBPDO
minimum version and release requirements 218 deciding if it’s for you 45
software requirements 203 driving system software requirements 54
how you order 39
BookMaster
introduction to 38
minimum version and release requirements 225 product-only option 33
books selective service option 33
for z/OS 34 what IBM does for you 40
redbooks 35 what you need to do 44
referred to by this book x what you receive from IBM 42
CCCA
Breeze for SCLM
minimum version and release requirements 218
minimum version and release requirements 218 CDMF algorithm
BTAM/SP in DCE Base Services 9
minimum version and release requirements 218 certificates, license
BTLS introduction to 2
changes, summary of
minimum version and release requirements 218
to this book for z/OS V1R1 xiii
BUILDMCS command to z/OS installation for V1R1 xiv
description 165 CICS Application Migration Aid
use of 165 minimum version and release requirements 218

290 z/OS V1R1.0 Planning for Installation

CICS/ESA Communications Server Security Level 1 (continued)
driving system software requirements 57 migration path from OS/390 R6 to z/OS V1R1 91
minimum version and release requirements 219 migration path from OS/390 R7 to z/OS V1R1 101
CICS Transaction Affinities Utility MVS/ESA migration path from OS/390 R8 to z/OS V1R1 112
minimum version and release requirements 218 migration path from OS/390 R9 to z/OS V1R1 123
CICS Transaction Server for OS/390 software requirements 204
minimum version and release requirements 218 Communications Server Security Level 2
CICS VSAM Recovery MVS/ESA V2 feature in z/OS 8
minimum version and release requirements 219 hardware requirements 230
CICSPlex SM migration path from OS/390 R10 to z/OS V1R1 132
minimum version and release requirements 219 migration path from OS/390 R6 to z/OS V1R1 91
cloning your system 275 migration path from OS/390 R7 to z/OS V1R1 101
Cloud 9 for SCLM migration path from OS/390 R8 to z/OS V1R1 112
minimum version and release requirements 219 migration path from OS/390 R9 to z/OS V1R1 123
cluster-related data sets software requirements 204
recommended placement 179 Communications Server Security Level 3
COBOL feature in z/OS 8
minimum version and release requirements 219 hardware requirements 231
COBOL for MVS & VM migration path from OS/390 R10 to z/OS V1R1 132
minimum version and release requirements 219 migration path from OS/390 R6 to z/OS V1R1 91
COBOL for OS/390 & VM migration path from OS/390 R7 to z/OS V1R1 101
minimum version and release requirements 219 migration path from OS/390 R8 to z/OS V1R1 112
COBOL Report Writer migration path from OS/390 R9 to z/OS V1R1 123
minimum version and release requirements 219 software requirements 205
COBOL Structuring Facility compatibility 71
minimum version and release requirements 219 compatibility, data
CODE/370 JES2 66
minimum version and release requirements 219 JES3 66
coexistence compatibility mode, WLM
description of 71 will be removed from z/OS 24
IBM’s policy 72 CONSOLE command
coexistence service saving user’s profile 215
JES2 81 copying your system 275
JES3 81 Corepoint Telephony
OS/390 R10 80 minimum version and release requirements 218
OS/390 R6 74
coupling facility
OS/390 R7 76
processor requirements 229
OS/390 R8 78
CPCS
OS/390 R9 79
minimum version and release requirements 219
Communications Server 6
Cryptographic Services
element in z/OS 6
element in z/OS 9
hardware requirements 239
hardware requirements 231
migration path from OS/390 R10 to z/OS V1R1 131
migration path from OS/390 R10 to z/OS V1R1 132
migration path from OS/390 R6 to z/OS V1R1 90
migration path from OS/390 R6 to z/OS V1R1 91
migration path from OS/390 R7 to z/OS V1R1 100
migration path from OS/390 R7 to z/OS V1R1 101
migration path from OS/390 R8 to z/OS V1R1 111
migration path from OS/390 R8 to z/OS V1R1 112
migration path from OS/390 R9 to z/OS V1R1 122
migration path from OS/390 R9 to z/OS V1R1 123
software requirements 204
software requirements 205
Communications Server NPF
CS z/OS 6
feature in z/OS 6
CSFI
hardware requirements 230
migration path from OS/390 R10 to z/OS V1R1 131 minimum version and release requirements 219
migration path from OS/390 R6 to z/OS V1R1 91 CSP
migration path from OS/390 R7 to z/OS V1R1 101 minimum version and release requirements 219
migration path from OS/390 R8 to z/OS V1R1 112 Customized Offerings Driver
migration path from OS/390 R9 to z/OS V1R1 122 introduction to 47
software requirements 204 CustomPac Installation Dialog
Communications Server Security Level 1 installing 51
feature in z/OS 7 introduction to 37
hardware requirements 230 what it does 42
migration path from OS/390 R10 to z/OS V1R1 132 what you do with it 44, 45

Index 291
D DB2 Row Archive Manager
minimum version and release requirements 220
DASD
DB2 SQL Performance Analyzer
placement discussion 167
minimum version and release requirements 220
recommended volumes 243
space utilization and performance 185 DBICF
storage requirements 63 minimum version and release requirements 220
data compatibility DCE Application Support
JES2 66 element in z/OS 9
JES3 66 hardware requirements 231
Data Dictionary, OS/VS DB/DC migration path from OS/390 R10 to z/OS V1R1 132
minimum version and release requirements 225 migration path from OS/390 R6 to z/OS V1R1 91
data sets migration path from OS/390 R7 to z/OS V1R1 101
names restructured 184 migration path from OS/390 R8 to z/OS V1R1 112
placement discussion 167 migration path from OS/390 R9 to z/OS V1R1 123
recommended volumes 243 software requirements 205
Data Stream Tuner for IMS/ESA DCE Base Services
minimum version and release requirements 219 element in z/OS 9
Data1 Fonts hardware requirements 231
minimum version and release requirements 219 migration path from OS/390 R10 to z/OS V1R1 132
DataInterchange migration path from OS/390 R6 to z/OS V1R1 92
minimum version and release requirements 219 migration path from OS/390 R7 to z/OS V1R1 102
DataPropagator, DB2 migration path from OS/390 R8 to z/OS V1R1 113
minimum version and release requirements 219 migration path from OS/390 R9 to z/OS V1R1 123
DataPropagator, IMS software requirements 205
minimum version and release requirements 223 DCE Security Server
DataRefresher part of SecureWay Security Server feature 18
minimum version and release requirements 219 DCE User Data Privacy CDMF
DB2 migration path from OS/390 R6 to z/OS V1R1 92
driving system software requirements 57 migration path from OS/390 R7 to z/OS V1R1 102
minimum version and release requirements 220 migration path from OS/390 R8 to z/OS V1R1 113
DB2 Administration Tool no longer in OS/390 20
minimum version and release requirements 219 DCE User Data Privacy DES/CDMF
DB2 Administration Tools migration path from OS/390 R6 to z/OS V1R1 92
minimum version and release requirements 219 migration path from OS/390 R7 to z/OS V1R1 102
DB2 Automated Utility Generator migration path from OS/390 R8 to z/OS V1R1 113
minimum version and release requirements 219 no longer in OS/390 20
DB2 Bind Manager DCF
minimum version and release requirements 219 enabling 159
DB2 Buffer Pool Tool minimum version and release requirements 220
minimum version and release requirements 219 Debug Tool
DB2 DataPropagator enabling 156
minimum version and release requirements 219 migration path from OS/390 R10 to z/OS V1R1 131
DB2 Forms for OS/390 migration path from OS/390 R6 to z/OS V1R1 90
minimum version and release requirements 220 migration path from OS/390 R7 to z/OS V1R1 100
DB2 High Performance Unload migration path from OS/390 R8 to z/OS V1R1 111
minimum version and release requirements 220 migration path from OS/390 R9 to z/OS V1R1 122
DB2 Intelligent Miner for Data part of C/C++ with Debug Tool feature 5
minimum version and release requirements 220 deleted from OS/390 and z/OS
DB2 Log Analysis Tool elements and features 20
minimum version and release requirements 220 deleting
DB2 Object Restore JES2 59
minimum version and release requirements 220 JES3 59
DB2 OLAP Server for OS/390 SDSF 59
minimum version and release requirements 220 delivery and packaging of z/OS 1
DB2 PM DES algorithm
minimum version and release requirements 220 in DCE Base Services 9
DB2 Query Monitor Developer Kit for OS/390
minimum version and release requirements 220 minimum version and release requirements 220
DB2 Recovery Manager device
minimum version and release requirements 220 I/O device support for z/OS 64

292 z/OS V1R1.0 Planning for Installation

DFSMS/MVS Network File System Distributed File Service (continued)
now called Network File System 16 hardware requirements 234
DFSMS Optimizer for OS/390 and MVS/ESA migration path from OS/390 R10 to z/OS V1R1 133
minimum version and release requirements 220 migration path from OS/390 R6 to z/OS V1R1 93
DFSMSdfp migration path from OS/390 R7 to z/OS V1R1 102
element in z/OS 10 migration path from OS/390 R8 to z/OS V1R1 113
hardware requirements 232 migration path from OS/390 R9 to z/OS V1R1 124
migration path from OS/390 R10 to z/OS V1R1 132 software requirements 206
migration path from OS/390 R6 to z/OS V1R1 92 distribution data sets
migration path from OS/390 R7 to z/OS V1R1 102 storage requirement 64
migration path from OS/390 R8 to z/OS V1R1 113 distribution libraries (DLIBs)
migration path from OS/390 R9 to z/OS V1R1 123 recommended placement 176
software requirements 205 DITTO/ESA for MVS
DFSMSdss minimum version and release requirements 221
feature in z/OS 10 DLIBs
hardware requirements 233 recommended placement 176
migration path from OS/390 R10 to z/OS V1R1 132 DOC APARs
migration path from OS/390 R6 to z/OS V1R1 92 on World Wide Web 35
migration path from OS/390 R7 to z/OS V1R1 102 documentation
migration path from OS/390 R8 to z/OS V1R1 113 for z/OS 34
migration path from OS/390 R9 to z/OS V1R1 124 from IBM Systems Centers 35
software requirements 205 referred to by this book x
DFSMShsm Domino Go Webserver
feature in z/OS 10 minimum version and release requirements 221
hardware requirements 233 now called IBM HTTP Server 13
migration path from OS/390 R10 to z/OS V1R1 132 downward compatibility 148
migration path from OS/390 R6 to z/OS V1R1 92 DRC Facility for IMS/ESA
migration path from OS/390 R7 to z/OS V1R1 102 minimum version and release requirements 221
migration path from OS/390 R8 to z/OS V1R1 113 driving system, installation
migration path from OS/390 R9 to z/OS V1R1 124 software requirements for CBPDO 54
software requirements 206 software requirements for ServerPac 48
DFSMSrmm software requirements for SystemPac
feature in z/OS 10 dump-by-data-set 48
hardware requirements 233 software requirements for SystemPac full volume
migration path from OS/390 R10 to z/OS V1R1 133 dump 53
migration path from OS/390 R6 to z/OS V1R1 92 driving system, msys for Setup
migration path from OS/390 R7 to z/OS V1R1 102 software requirements 212
migration path from OS/390 R8 to z/OS V1R1 113 dump-by-data-set SystemPac
migration path from OS/390 R9 to z/OS V1R1 124 introduction 38
software requirements 206 dynamic APF
DFSORT software requirements 201
enabling 158 dynamic enablement
feature in z/OS 10 introduction to 2
hardware requirements 233 migration action 142
migration path from OS/390 R10 to z/OS V1R1 133 procedures 151
migration path from OS/390 R6 to z/OS V1R1 93 relationship to national language 25
migration path from OS/390 R7 to z/OS V1R1 102 dynamic exits service
migration path from OS/390 R8 to z/OS V1R1 113 use in positioning to use ServerPac install
migration path from OS/390 R9 to z/OS V1R1 124 method 165
minimum version and release requirements 221 Dynamic Resource Control Facility for IMS/ESA
software requirements 206 minimum version and release requirements 221
disabling
what was enabled 159
DISOSS/370 E
minimum version and release requirements 221 education
DISOSS Library Services - Extended for z/OS 34
minimum version and release requirements 221 IBM Global Campus Web site 34
DisplayWrite/370 phone enrollment 34
minimum version and release requirements 221 elements
Distributed File Service introduction to 1
element in z/OS 11 list of 3

Index 293
elements (continued) expanded storage
removed from OS/390 and z/OS 20 not supported in z/Architecture 63
to be removed from z/OS 23 Express Plus Offering
Emulation Program for installing z/OS 39
minimum version and release requirements 221 extended indirect cataloging
enablement of priced features use of 184
introduction to 2 extended indirect volume serial support
migration action 142 use of 184
procedures 151 Extended Service Offering (ESO)
Encina Toolkit Executive for service delivery 32
element in z/OS 11 packages for ServerPac orders 29
hardware requirements 234 packages for SystemPac orders 30
migration path from OS/390 R10 to z/OS V1R1 133 Extended Terminal Options Support for IMS/ESA
migration path from OS/390 R6 to z/OS V1R1 93 minimum version and release requirements 221
migration path from OS/390 R7 to z/OS V1R1 103
migration path from OS/390 R8 to z/OS V1R1 114
migration path from OS/390 R9 to z/OS V1R1 124 F
software requirements 206 fallback
eNetwork Communications Server in z/OS 160
now named Communications Server 6 requires coexistence service and actions 72
eNetwork Host On-Demand Fault Analyzer
minimum version and release requirements 221 minimum version and release requirements 221
Enhanced HOLDDATA 31 features
Enterprise Server, S/390 Parallel introduction to 1
models not supported by z/OS xiv list of 3
models supported by z/OS 62 removed from OS/390 and z/OS 20
to be removed from z/OS 23
Entry Server Offering
fee installation methods
for installing z/OS 39
other 39
EREP
SystemPac 38
element in z/OS 11 FFST
hardware requirements 234 element in z/OS 11
migration path from OS/390 R10 to z/OS V1R1 133 hardware requirements 234
migration path from OS/390 R6 to z/OS V1R1 93 migration path from OS/390 R10 to z/OS V1R1 133
migration path from OS/390 R7 to z/OS V1R1 103 migration path from OS/390 R6 to z/OS V1R1 93
migration path from OS/390 R8 to z/OS V1R1 114 migration path from OS/390 R7 to z/OS V1R1 103
migration path from OS/390 R9 to z/OS V1R1 124 migration path from OS/390 R8 to z/OS V1R1 114
software requirements 206 migration path from OS/390 R9 to z/OS V1R1 124
ESCM software requirements 206
minimum version and release requirements 221 FICON devices
ESCON devices supported by z/OS 64
supported by z/OS 64 File Exchange/MVS User Interface
ESCON Director Support minimum version and release requirements 221
element in z/OS 11 File Manager
hardware requirements 234 minimum version and release requirements 221
migration path from OS/390 R10 to z/OS V1R1 133 Firewall Technologies
migration path from OS/390 R6 to z/OS V1R1 93 hardware requirements 238
migration path from OS/390 R7 to z/OS V1R1 103 part of SecureWay Security Server feature 18
migration path from OS/390 R8 to z/OS V1R1 114 software requirements 214
migration path from OS/390 R9 to z/OS V1R1 124 flashes, IBM Systems Center
software requirements 206 URLs 35
ESO (Extended Service Offering) four-digit device support
for service delivery 32 software requirements 210
packages for ServerPac orders 29 full system replacement
packages for SystemPac orders 30 introduction to 37
etc directory full volume dump SystemPac
migrating files 138 introduction 38
ETO Support FunctionPac
minimum version and release requirements 221 not available with z/OS 37
exclusive element or feature future removals from z/OS
introduction to 3 elements and features 23

294 z/OS V1R1.0 Planning for Installation

G hardware requirements (continued)
target system 62
G5
HCD
as a z/OS processor 62
element in z/OS 12
G6
hardware requirements 234
as a z/OS processor 62
migration path from OS/390 R10 to z/OS V1R1 133
GAM/SP
migration path from OS/390 R6 to z/OS V1R1 93
minimum version and release requirements 221
migration path from OS/390 R7 to z/OS V1R1 103
GDDM
migration path from OS/390 R8 to z/OS V1R1 114
element in z/OS 11
migration path from OS/390 R9 to z/OS V1R1 125
hardware requirements 234
HCM
migration path from OS/390 R10 to z/OS V1R1 133
feature in z/OS 12
migration path from OS/390 R6 to z/OS V1R1 93
hardware requirements 234
migration path from OS/390 R7 to z/OS V1R1 103
migration path from OS/390 R10 to z/OS V1R1 133
migration path from OS/390 R8 to z/OS V1R1 114
migration path from OS/390 R6 to z/OS V1R1 94
migration path from OS/390 R9 to z/OS V1R1 124
migration path from OS/390 R7 to z/OS V1R1 103
minimum version and release requirements 221
migration path from OS/390 R8 to z/OS V1R1 114
software requirements 206
migration path from OS/390 R9 to z/OS V1R1 125
GDDM/GKS
software requirements 207
minimum version and release requirements 221
HFS customization volume
GDDM/IMD
recommended data sets on 178
minimum version and release requirements 221
HFS target volume
GDDM/IVU
recommended data sets on 174
minimum version and release requirements 221
High Speed UDP facility
GDDM-PGF
no longer in OS/390 20
enabling 158
HLASM
feature in z/OS 12
element in z/OS 12
hardware requirements 234
hardware requirements 234
migration path from OS/390 R10 to z/OS V1R1 133
migration path from OS/390 R10 to z/OS V1R1 134
migration path from OS/390 R6 to z/OS V1R1 93
migration path from OS/390 R6 to z/OS V1R1 94
migration path from OS/390 R7 to z/OS V1R1 103
migration path from OS/390 R7 to z/OS V1R1 103
migration path from OS/390 R8 to z/OS V1R1 114
migration path from OS/390 R8 to z/OS V1R1 114
migration path from OS/390 R9 to z/OS V1R1 124
migration path from OS/390 R9 to z/OS V1R1 125
minimum version and release requirements 221
software requirements 207
software requirements 206
HLASM Toolkit
GDDM-REXX
enabling 158
feature in z/OS 12
feature in z/OS 12
hardware requirements 234
hardware requirements 234
migration path from OS/390 R10 to z/OS V1R1 133
migration path from OS/390 R10 to z/OS V1R1 134
migration path from OS/390 R6 to z/OS V1R1 93
migration path from OS/390 R6 to z/OS V1R1 94
migration path from OS/390 R7 to z/OS V1R1 103
migration path from OS/390 R7 to z/OS V1R1 104
migration path from OS/390 R8 to z/OS V1R1 114
migration path from OS/390 R8 to z/OS V1R1 115
migration path from OS/390 R9 to z/OS V1R1 125
migration path from OS/390 R9 to z/OS V1R1 125
software requirements 206
software requirements 207
GDQF
HOLDDATA 31
minimum version and release requirements 221
Host On-Demand
geoManager
minimum version and release requirements 221,
minimum version and release requirements 221
226
global data sets, SMP/E
no longer in OS/390 20
recommended placement 171
global resource serialization complex
hardware dependencies 229
XCF signalling 229 I
Global Services, IBM I/O device support
Web page 39 for z/OS 64
guest, z/OS as VM 201 IBM Global Services
Web page 39
IBM HTTP Server
H element in z/OS 13
hardware requirements hardware requirements 234
for each element and feature 229 migration path from OS/390 R10 to z/OS V1R1 134
minimum for driving system 57 migration path from OS/390 R6 to z/OS V1R1 94

Index 295
IBM HTTP Server (continued) IEBCOPY format tapes
migration path from OS/390 R7 to z/OS V1R1 104 containing ServerPac order 42
migration path from OS/390 R8 to z/OS V1R1 115 containing SystemPac order 43
migration path from OS/390 R9 to z/OS V1R1 125 IFAPRDxx parmlib member
software requirements 207 how to activate 159
IBM HTTP Server Export Secure how to update for dynamic enablement 154
migration path from OS/390 R6 to z/OS V1R1 94 migration action for dynamic enablement 142
migration path from OS/390 R7 to z/OS V1R1 104 IGES Processor
migration path from OS/390 R8 to z/OS V1R1 115 minimum version and release requirements 222
migration path from OS/390 R9 to z/OS V1R1 125 ILM (IBM License Manager)
no longer in OS/390 21 element in z/OS 13
IBM HTTP Server France Secure hardware requirements 235
migration path from OS/390 R6 to z/OS V1R1 94 migration actions 143
migration path from OS/390 R7 to z/OS V1R1 104 migration path from OS/390 R10 to z/OS V1R1 134
migration path from OS/390 R8 to z/OS V1R1 115 migration path from OS/390 R6 to z/OS V1R1 95
migration path from OS/390 R9 to z/OS V1R1 125 migration path from OS/390 R7 to z/OS V1R1 104
no longer in OS/390 21 migration path from OS/390 R8 to z/OS V1R1 115
IBM HTTP Server NA Secure migration path from OS/390 R9 to z/OS V1R1 126
feature in z/OS 13 production use 13
hardware requirements 234 software requirements 208
migration path from OS/390 R10 to z/OS V1R1 134 image-related data sets
migration path from OS/390 R6 to z/OS V1R1 95 recommended placement 177
migration path from OS/390 R7 to z/OS V1R1 104 ImagePlus Folder Application Facility
migration path from OS/390 R8 to z/OS V1R1 115 minimum version and release requirements 222
migration path from OS/390 R9 to z/OS V1R1 126 ImagePlus Object Distribution Manager
software requirements 207 minimum version and release requirements 222
IBM License Manager IMS
element in z/OS 13 minimum version and release requirements 222
hardware requirements 235 IMS Advanced ACB Generator
migration actions 143 minimum version and release requirements 223
migration path from OS/390 R10 to z/OS V1R1 134 IMS Compression - Extended
migration path from OS/390 R6 to z/OS V1R1 95 minimum version and release requirements 223
migration path from OS/390 R7 to z/OS V1R1 104 IMS Connect
migration path from OS/390 R8 to z/OS V1R1 115 minimum version and release requirements 223
migration path from OS/390 R9 to z/OS V1R1 126 IMS Data Base Integrity Control Facility
production use 13 minimum version and release requirements 223
software requirements 208 IMS Database Repair Facility
ICKDSF minimum version and release requirements 223
element in z/OS 13 IMS DataPropagator
hardware requirements 234 minimum version and release requirements 223
migration path from OS/390 R10 to z/OS V1R1 134 IMS/ESA
migration path from OS/390 R6 to z/OS V1R1 95 driving system software requirements 57
migration path from OS/390 R7 to z/OS V1R1 104 minimum version and release requirements 222
migration path from OS/390 R8 to z/OS V1R1 115 IMS/ESA Ad-Hoc Tool
migration path from OS/390 R9 to z/OS V1R1 126 minimum version and release requirements 222
software requirements 207 IMS/ESA ADF Tool Pak
ICLI (Integrated Call Level Interface) minimum version and release requirements 222
in z/OS UNIX System Services 20 IMS/ESA BTS
ICS minimum version and release requirements 222
now called IBM HTTP Server 13 IMS/ESA Database Control Suite
ICSF minimum version and release requirements 222
migration path from OS/390 R10 to z/OS V1R1 132 IMS/ESA DBRC Security Tool
migration path from OS/390 R6 to z/OS V1R1 91 minimum version and release requirements 222
migration path from OS/390 R7 to z/OS V1R1 101 IMS/ESA DEDB Fast Recovery
migration path from OS/390 R8 to z/OS V1R1 112 minimum version and release requirements 222
migration path from OS/390 R9 to z/OS V1R1 123 IMS/ESA Index Builder for MVS/ESA
minimum version and release requirements 222 minimum version and release requirements 222
part of Cryptographic Services 9 IMS/ESA Partition Support Product
ICSS minimum version and release requirements 222
minimum version and release requirements 222 IMS/ESA Performance Analyzer
now called IBM HTTP Server 13 minimum version and release requirements 222

296 z/OS V1R1.0 Planning for Installation

IMS/ESA Recovery Saver installing z/OS
minimum version and release requirements 222 definition of install ix
IMS/ESA Year 2000 Exit Tool elements you must install 59
minimum version and release requirements 222 entitled methods
IMS ETO Support CBPDO 38
minimum version and release requirements 223 ServerPac 37
IMS Fast Path Basic Tools features you must install 59
minimum version and release requirements 223 fee methods
IMS Fast Path Online Tools Entry Server Offering 39
minimum version and release requirements 223 Express Plus Offering 39
IMS Hardware Data Compression - Extended other 39
minimum version and release requirements 223 Rapid Migration Offering 39
IMS High Performance Load Software Management 39
minimum version and release requirements 223 SystemPac 38
IMS High Performance Pointer Checker z/OS Select 39
minimum version and release requirements 223 IBM’s recommendations 45
IMS High Performance Prefix Resolution Integrated Call Level Interface (ICLI)
minimum version and release requirements 223 in z/OS UNIX System Services 20
IMS High Performance Upload Integrated Server, S/390
minimum version and release requirements 223 not supported by z/OS xiv
IMS Image Copy Extensions integration testing by IBM
minimum version and release requirements 223 explanation of 27
IMS Index Builder Web site 27
minimum version and release requirements 223 Intelligent Resource Director (IRD)
IMS Library Management Utilities goal mode required 201
hardware requirements 229
minimum version and release requirements 223
introduction 1
IMS MRQ
Internet address
minimum version and release requirements 222
for downloading Enhanced HOLDDATA 32
IMS Parallel Change Accumulation
for IBM education information 34
minimum version and release requirements 223 for IBM Global Services 39
IMS Performance Analyzer for IBM Systems Center flashes 35
minimum version and release requirements 223 for ISV products that support z/OS 61
IMS Program Restart Facility for product catalogs 60
minimum version and release requirements 223 for reader comments ii
IMS Queue Control Facility for redbooks 35
minimum version and release requirements 223 for S/390 service information 32
IMS Recovery Saver for S/390 Service Update Facility 32
minimum version and release requirements 223 for ShopzSeries 39, 61
IMS Sequential Randomizer Generator for SMP/E Planning and Migration Assistant 18
minimum version and release requirements 223 for wizard edition of this book ix
IMS System Utilities/DBT for z/OS integration test 27
minimum version and release requirements 223 for z/OS product publications 35
indirect cataloging summary of addresses in this book x
use of 184 IODM
indirect volume serial support minimum version and release requirements 222
use of 184 IP
Infoprint Server hardware requirements 239
feature in z/OS 14 part of Communications Server element 6
hardware requirements 235 software requirements 204
migration actions 144 IP PrintWay
migration path from OS/390 R10 to z/OS V1R1 134 part of Infoprint Server 14
migration path from OS/390 R6 to z/OS V1R1 95 IP PrintWay feature of PSF
migration path from OS/390 R7 to z/OS V1R1 105 enabling 158
migration path from OS/390 R8 to z/OS V1R1 116 IP PrintWay/NetSpool
migration path from OS/390 R9 to z/OS V1R1 126 formerly in OS/390 14
software requirements 209 IP Security - CDMF
Infoprint Server Transforms for OS/390 now in Communications Server Security Level 1 7
enabling 159 IP Security - DES/CDMF
minimum version and release requirements 223 migration path from OS/390 R10 to z/OS V1R1 132
installation plan skeleton 189 migration path from OS/390 R7 to z/OS V1R1 101

Index 297
IP Security - DES/CDMF (continued) JES2 checkpoint volume
migration path from OS/390 R8 to z/OS V1R1 112 recommended data sets on 179
migration path from OS/390 R9 to z/OS V1R1 123 JES2 spool volume
now in Communications Server Security Level 2 8 recommended data sets on 179
IP Security - TDES JES3
migration path from OS/390 R6 to z/OS V1R1 91 coexistence service 81
now in Communications Server Security Level 3 8 data compatibility 66
IPFAF deleting 59
minimum version and release requirements 222 feature in z/OS 14
IPL, rolling hardware requirements 236
preparing for 161 levels supported with BCP 65
IRD (Intelligent Resource Director) migrating to current level of z/OS 69
goal mode required 201 migration path from OS/390 R10 to z/OS V1R1 135
hardware requirements 229 migration path from OS/390 R6 to z/OS V1R1 95
introduction 1 migration path from OS/390 R7 to z/OS V1R1 105
ISPF migration path from OS/390 R8 to z/OS V1R1 116
element in z/OS 14 migration path from OS/390 R9 to z/OS V1R1 126
hardware requirements 236 Parallel Sysplex requirements 81
migration path from OS/390 R10 to z/OS V1R1 134 placing existing JES3 in separate zone 67
migration path from OS/390 R6 to z/OS V1R1 95 ServerPac and SystemPac delivery of 66
migration path from OS/390 R7 to z/OS V1R1 105 software requirements 210
migration path from OS/390 R8 to z/OS V1R1 116 using existing level with z/OS V1R1 65
migration path from OS/390 R9 to z/OS V1R1 126
software requirements - with ISPF client/server 210
ISV products K
choosing 61 kernel, z/OS UNIX System Services
list on World Wide Web 61 in BCP 4
migrating 137
Item Capture Support
minimum version and release requirements 223 L
ITSO LAN Server
redbooks 35 element in OS/390 15
IXFP hardware requirements 236
minimum version and release requirements 223 migration path from OS/390 R10 to z/OS V1R1 135
migration path from OS/390 R6 to z/OS V1R1 95
migration path from OS/390 R7 to z/OS V1R1 105
J migration path from OS/390 R8 to z/OS V1R1 116
Java for OS/390 migration path from OS/390 R9 to z/OS V1R1 127
minimum version and release requirements 223 will be removed from z/OS 23
JES/328X Print Facility V3 Language Environment
minimum version and release requirements 223 element in z/OS 15
JES2 hardware requirements 236
coexistence service 81 migration actions 147
data compatibility 66 migration path from OS/390 R10 to z/OS V1R1 135
deleting 59 migration path from OS/390 R6 to z/OS V1R1 96
element in z/OS 14 migration path from OS/390 R7 to z/OS V1R1 106
hardware requirements 236 migration path from OS/390 R8 to z/OS V1R1 117
levels supported with BCP 65 migration path from OS/390 R9 to z/OS V1R1 127
migrating to current level of z/OS 69 software requirements 211
migration path from OS/390 R10 to z/OS V1R1 135 Language Environment Data Decryption
migration path from OS/390 R6 to z/OS V1R1 95 migration path from OS/390 R6 to z/OS V1R1 96
migration path from OS/390 R7 to z/OS V1R1 105 migration path from OS/390 R7 to z/OS V1R1 106
migration path from OS/390 R8 to z/OS V1R1 116 migration path from OS/390 R8 to z/OS V1R1 117
migration path from OS/390 R9 to z/OS V1R1 126 no longer in OS/390 21
placing existing JES2 in separate zone 67 LANRES
placing existing level in same zone with z/OS 67 element in z/OS 15
pre-Release 4 mode 147 hardware requirements 236
Release 4 mode 147 migration path from OS/390 R10 to z/OS V1R1 135
ServerPac and SystemPac delivery of 66 migration path from OS/390 R6 to z/OS V1R1 96
software requirements 210 migration path from OS/390 R7 to z/OS V1R1 106
using existing level with z/OS V1R1 65 migration path from OS/390 R8 to z/OS V1R1 117

298 z/OS V1R1.0 Planning for Installation

LANRES (continued) MICR/OCR (continued)
migration path from OS/390 R9 to z/OS V1R1 127 migration path from OS/390 R7 to z/OS V1R1 106
software requirements 211 migration path from OS/390 R8 to z/OS V1R1 117
will be removed from z/OS 24 migration path from OS/390 R9 to z/OS V1R1 127
layout, recommended system 243 software requirements 211
LDAP Server migration
part of SecureWay Security Server feature 18 application development actions 138
Librarian, SoftCopy 43 BookServer actions 138
license certificates C/C++ actions 142
introduction to 2 etc actions 138
License Manager, IBM hardware planning 83
element in z/OS 13 IFAPRDxx actions 142
hardware requirements 235 ILM actions 143
migration actions 143 Infoprint Server actions 144
migration path from OS/390 R10 to z/OS V1R1 134 JES2 actions 147
migration path from OS/390 R6 to z/OS V1R1 95 Language Environment actions 147
migration path from OS/390 R7 to z/OS V1R1 104 ServerPac and SystemPac actions 148
migration path from OS/390 R8 to z/OS V1R1 115 tables 83
migration path from OS/390 R9 to z/OS V1R1 126 virtual storage considerations actions 149
production use 13 migration tables
software requirements 208 OS/390 R10 to z/OS V1R1 130
licensed product DLIB volume OS/390 R6 to z/OS V1R1 89
recommended data sets on 177 OS/390 R7 to z/OS V1R1 99
licensed product target volume OS/390 R8 to z/OS V1R1 110
recommended data sets on 175 OS/390 R9 to z/OS V1R1 121
licensed program Millenium Runtime Windowing Tool
minimum levels for z/OS 217 minimum version and release requirements 224
logical parmlib MPSX/370
use of 185 minimum version and release requirements 224
LookAt
MQSeries
on CD-ROM 43
minimum version and release requirements 224
on Internet 35
MQSeries Integrator
Lotus Domino
minimum version and release requirements 224
minimum version and release requirements 223
Lotus Domino Go Webserver MQSeries Workflow
now called IBM HTTP Server 13 minimum version and release requirements 224
msys for Setup
driving system requirements 212
M element in z/OS 16
hardware requirements 237
maintenance, preventive
migration path from OS/390 R10 to z/OS V1R1 135
using RSUs 31
migration path from OS/390 R6 to z/OS V1R1 96
Managed System Infrastructure for Setup
migration path from OS/390 R7 to z/OS V1R1 106
element in z/OS 16
migration path from OS/390 R8 to z/OS V1R1 117
marketed, products no longer
migration path from OS/390 R9 to z/OS V1R1 127
reinstalling 165
software requirements 212
MAS
Multiprise, S/390
coexistence PTFs 81
master catalog as a z/OS processor 62
changes to use ServerPac 167 multisystem configuration
master catalog volume meaning of 71
recommended data sets on 179
MERVA
minimum version and release requirements 223, N
224 national language support
MERVA Extended Connectivity for MVS/ESA in z/OS 25
minimum version and release requirements 223 relationship to dynamic enablement 25
MICR/OCR NCP
element in z/OS 16 driving system software requirements 57
hardware requirements 236 minimum version and release requirements 217
migration path from OS/390 R10 to z/OS V1R1 135 NETDA
migration path from OS/390 R6 to z/OS V1R1 96 minimum version and release requirements 224

Index 299
NetQuestion
now a component of Text Search 19
O
OCEP (Open Cryptographic Enhanced Plug-ins)
NetSpool
part of SecureWay Security Server feature 18
part of Infoprint Server 14
OCSF France
NetSpool feature of PSF
migration path from OS/390 R7 to z/OS V1R1 106
enabling 158
migration path from OS/390 R8 to z/OS V1R1 117
NetView
no longer in OS/390 21
minimum version and release requirements 224
OCSF Security Level 1
NetView Access Services for MVS
migration path from OS/390 R7 to z/OS V1R1 107
minimum version and release requirements 224
migration path from OS/390 R8 to z/OS V1R1 118
NetView Distribution Manager for MVS
no longer in OS/390 21
minimum version and release requirements 224
OCSF Security Level 2
NetView FTP
migration path from OS/390 R7 to z/OS V1R1 107
minimum version and release requirements 224
migration path from OS/390 R8 to z/OS V1R1 118
NetView MultiSystem Manager for MVS/ESA
no longer in OS/390 21
minimum version and release requirements 224
OCSF Security Level 3
NetView Performance Monitor
feature in z/OS 16
minimum version and release requirements 224
hardware requirements 237
network attachments
migration path from OS/390 R10 to z/OS V1R1 136
hardware requirements 240
migration path from OS/390 R6 to z/OS V1R1 96
Network Authentication and Privacy Service
migration path from OS/390 R7 to z/OS V1R1 107
part of SecureWay Security Server feature 18
migration path from OS/390 R8 to z/OS V1R1 118
Network Data Couplers
migration path from OS/390 R9 to z/OS V1R1 128
minimum version and release requirements 224
software requirements 213
Network File System
Offload, 3172
element in z/OS 16
no longer in OS/390 20
hardware requirements 237
OGL/370
migration path from OS/390 R10 to z/OS V1R1 136
minimum version and release requirements 224
migration path from OS/390 R6 to z/OS V1R1 96
OnDemand
migration path from OS/390 R7 to z/OS V1R1 106
minimum version and release requirements 219
migration path from OS/390 R8 to z/OS V1R1 117
OPC/ESA
migration path from OS/390 R9 to z/OS V1R1 127
minimum version and release requirements 225
software requirements 213
Open Cryptographic Enhanced Plug-ins (OCEP)
Network Security Processor MVS Support Program
part of SecureWay Security Server feature 18
minimum version and release requirements 224
OpenEdition DCE Application Support
Network Station Client
minimum version and release requirements 225
no longer in OS/390 20
now called DCE Application Support 9
Network Station Manager
OpenEdition DCE Base Services
no longer in OS/390 20
now called DCE Base Services 9
Networking Systems Center flashes 35
OpenEdition DCE DFS
NLS (national language support)
now called Distributed File Service 11
in z/OS 25
operational data sets
relationship to dynamic enablement 25
in ServerPac software upgrade 44
NLV support
optional features
in z/OS 25
introduction to 1
relationship to dynamic enablement 25
list of 3
non-IBM products
removed from OS/390 and z/OS 20
choosing 61
to be removed from z/OS 23
nonexclusive element or feature
order checklist
introduction to 3
for SystemPac orders 40
Notices 285
OS/390 Print Server
NRF now called Infoprint Server 14
minimum version and release requirements 224 OS/VS DB/DC Data Dictionary
NSI minimum version and release requirements 225
minimum version and release requirements 224 OSA/SF
NTO element in z/OS 17
minimum version and release requirements 224 hardware requirements 237
NTuneMON migration path from OS/390 R10 to z/OS V1R1 136
minimum version and release requirements 224 migration path from OS/390 R6 to z/OS V1R1 97
NTuneNCP migration path from OS/390 R7 to z/OS V1R1 107
minimum version and release requirements 224 migration path from OS/390 R8 to z/OS V1R1 118

300 z/OS V1R1.0 Planning for Installation

OSA/SF (continued) preventive maintenance
migration path from OS/390 R9 to z/OS V1R1 128 using RSUs 31
software requirements 213 preventive service planning 30
OSI/CS priced features
minimum version and release requirements 225 introduction to 2
OSI/FS
Print Interface
minimum version and release requirements 225
part of Infoprint Server 14
OSL
minimum version and release requirements 225 Print Management Facility/MVS
OV/MVS minimum version and release requirements 225
minimum version and release requirements 225 Print Server, OS/390
now called Infoprint Server 14
Printer Inventory Manager
P part of Infoprint Server 14
packaging and delivery of z/OS 1 processor storage requirements
page data set volume 1 minimum to IPL 63
recommended data sets on 177 processors
page data set volume 2 not supported by z/OS xiv
recommended data sets on 178 required for z/OS 62
Parallel Enterprise Server, S/390 proclib
models not supported by z/OS xiv
changes to use ServerPac 167
models supported by z/OS 62
product-only CBPDO 33
Parallel Environment
in z/OS UNIX System Services 20 product policy statements
Parallel Reorganization for IMS/ESA introduction to 2
minimum version and release requirements 225 product registration service
Parallel Sysplex introduction to 2
rolling z/OS across systems 161 product set
parmlib definition of 167
changes to use ServerPac 167 ProductPac
parmlib concatenation not available with z/OS 37
control parmlib data sets 167 products no longer marketed
use of 185 reinstalling 165
parmlib symbolic preprocessor tool program directories
verify symbols 167 received with order 43
Payment Gateway for OS/390 Program Restart Facility for IMS
minimum version and release requirements 225
minimum version and release requirements 225
PC Server System/390
PSF
not supported by z/OS xiv
PCF minimum version and release requirements 225
minimum version and release requirements 225 PSP
PDF files buckets 30
on CD-ROMs 43 hardware upgrade identifiers 63
on World Wide Web 35 information received with order 43
Pi and Specials Fonts software upgrade identifiers 30
minimum version and release requirements 225 PTFs
PL/I JES3 coexistence 81
minimum version and release requirements 225 MAS coexistence 81
Planning and Migration Assistant, SMP/E OS/390 R10 coexistence 80
description 18 OS/390 R6 coexistence 74
used to plan order 61 OS/390 R7 coexistence 76
policy, IBM’s OS/390 R8 coexistence 78
coexistence 72 OS/390 R9 coexistence 79
installing all elements and features 59 to use existing JES2 66
service 28 publications
policy statements, product for z/OS 34
introduction to 2 redbooks 35
PPFA/370 referred to by this book x
minimum version and release requirements 225 Publishing Systems BookMaster
pre-Release 4 mode, JES2 147 minimum version and release requirements 225

Index 301
Q RS/6000 and System/390 Server-on-Board
not supported by z/OS xiv
QMF RSU
minimum version and release requirements 225 description of 31
in integration testing 28
in ServerPac order 29
R in SystemPac order 30
RACF RTLS
migration path from OS/390 R10 to z/OS V1R1 136 software requirements 202
migration path from OS/390 R8 to z/OS V1R1 119 Runtime Analyzer
migration path from OS/390 R9 to z/OS V1R1 128 minimum version and release requirements 226
minimum version and release requirements 226
part of SecureWay Security Server feature 18
Rapid Migration Offering S
for installing z/OS 39 S/390 Integrated Server
Recommended Service Upgrade (RSU) not supported by z/OS xiv
description of 31 S/390 Multiprise
in integration testing 28 as a z/OS processor 62
in ServerPac order 29 S/390 Parallel Enterprise Server
in SystemPac order 30 models not supported by z/OS xiv
recommended system layout 243 models supported by z/OS 62
red books S/390 servers
from IBM ITSO 35 supported by z/OS 62
RefreshPac 32 SDF II
Release 4 mode, JES2 147 minimum version and release requirements 226
removed from OS/390 and z/OS SDSF
elements and features 20 deleting 59
removing feature in z/OS 17
JES2 59 hardware requirements 237
JES3 59 migration path from OS/390 R10 to z/OS V1R1 136
SDSF 59 migration path from OS/390 R6 to z/OS V1R1 97
Repository Manager/MVS migration path from OS/390 R7 to z/OS V1R1 107
migration path from OS/390 R8 to z/OS V1R1 118
minimum version and release requirements 226
migration path from OS/390 R9 to z/OS V1R1 128
requirements for z/OS
minimum version and release requirements 226
driving system (CBPDO) 54
ServerPac and SystemPac delivery of 66
driving system (ServerPac) 48
software requirements 214
driving system (SystemPac dump-by-data-set) 48
using current SDSF with old JES2 68
driving system (SystemPac full volume dump) 53
SDSF/MVS
hardware 57
minimum version and release requirements 226
restructured data set names 184
SearchManager/370
REXX/370 minimum version and release requirements 226
minimum version and release requirements 226 SecureWay Communications Server
REXX for CICS now named Communications Server 6
minimum version and release requirements 226 SecureWay Host On-Demand
ripple minimum version and release requirements 226
definition of 42 SecureWay Host Publisher
RMDS minimum version and release requirements 226
minimum version and release requirements 226 SecureWay Security Server
RMF feature in z/OS 18
feature in z/OS 17 hardware requirements 238
hardware requirements 237 migration path from OS/390 R10 to z/OS V1R1 136
migration path from OS/390 R10 to z/OS V1R1 136 migration path from OS/390 R6 to z/OS V1R1 97
migration path from OS/390 R6 to z/OS V1R1 97 migration path from OS/390 R7 to z/OS V1R1 108
migration path from OS/390 R7 to z/OS V1R1 107 migration path from OS/390 R8 to z/OS V1R1 119
migration path from OS/390 R8 to z/OS V1R1 118 migration path from OS/390 R9 to z/OS V1R1 128
migration path from OS/390 R9 to z/OS V1R1 128 software requirements 214
minimum version and release requirements 226 Security Server, SecureWay
software requirements 214 feature in z/OS 18
rolling IPL hardware requirements 238
preparing for 161 migration path from OS/390 R10 to z/OS V1R1 136

302 z/OS V1R1.0 Planning for Installation

Security Server, SecureWay (continued) SMP/E
migration path from OS/390 R6 to z/OS V1R1 97 element in z/OS 18
migration path from OS/390 R7 to z/OS V1R1 108 hardware requirements 238
migration path from OS/390 R8 to z/OS V1R1 119 migration path from OS/390 R10 to z/OS V1R1 136
migration path from OS/390 R9 to z/OS V1R1 128 migration path from OS/390 R6 to z/OS V1R1 97
software requirements 214 migration path from OS/390 R7 to z/OS V1R1 108
Security Server LDAP Server DES migration path from OS/390 R8 to z/OS V1R1 119
migration path from OS/390 R6 to z/OS V1R1 97 migration path from OS/390 R9 to z/OS V1R1 128
migration path from OS/390 R7 to z/OS V1R1 108 software requirements 214
no longer in OS/390 21 SMP/E data sets
Select, z/OS storage requirement 64
for installing z/OS 39 SMP/E global data sets
selective service CBPDO 33 recommended placement 171
ServerPac SMP/E Planning and Migration Assistant
deciding if it’s for you 45 description 18
driving system software requirements 48 used to plan order 61
full system replacement 37 SMPPTS data set
how you order 39 storage requirement 64
introduction to 37 SMPTLIB data sets
migration actions 148 storage requirement 64
SMS active for allocation 50 SMS
software upgrade 37 active for allocation 50
target system preparation 51 SNA
what IBM does for you 40 hardware requirements 242
what you need to do 44 part of Communications Server element 6
what you receive from IBM 42 software requirements 204
SnapShot
servers
minimum version and release requirements 226
not supported by z/OS xiv
SNMP Subagent
required for z/OS 62
part of Infoprint Server 14
service softcopy books
distribution 32 on World Wide Web
driving system requirement (ServerPac and redbooks 35
SystemPac) 51 z/OS product 35
Enhanced HOLDDATA Web site 32 SoftCopy Librarian 43
for target system 64 Softcopy Print
IBM’s policy 28 migration path from OS/390 R6 to z/OS V1R1 97
level for CBPDO orders 29 migration path from OS/390 R7 to z/OS V1R1 108
level for ServerPac orders 29 migration path from OS/390 R8 to z/OS V1R1 119
level for SystemPac orders 30 migration path from OS/390 R9 to z/OS V1R1 128
preventive maintenance 31 no longer in OS/390 22
RefreshPac 32 softcopy volume
S/390 Service Update Facility 32
recommended data sets on 180
to use existing JES2 66
Software Management
Web page for information 32
for installing z/OS 39
service, coexistence
software requirements
JES2 81
driving system for CBPDO 54
JES3 81
driving system for ServerPac 48
OS/390 R10 80
driving system for SystemPac dump-by-data-set 48
OS/390 R6 74
driving system for SystemPac full volume dump 53
OS/390 R7 76
for each element and feature 201
OS/390 R8 78
software upgrade
OS/390 R9 79
introduction to 37
ShopzSeries 39, 61
SOMobjects ADE
Web page 39, 61
feature in z/OS 18
size hardware requirements 238
of blocks for best performance 185 migration path from OS/390 R10 to z/OS V1R1 136
of DASD required 63 migration path from OS/390 R6 to z/OS V1R1 97
skeleton installation plan 189 migration path from OS/390 R7 to z/OS V1R1 108
SmartBatch for OS/390 migration path from OS/390 R8 to z/OS V1R1 119
minimum version and release requirements 226 migration path from OS/390 R9 to z/OS V1R1 129

Index 303
SOMobjects ADE (continued) SYSRES
software requirements 215 changes to use ServerPac 166
will be removed from z/OS 24 handling overflow 170
SOMobjects RTL indirect cataloging 184
element in z/OS 19 indirect volume serial support 184
hardware requirements 238 logical extension volumes 184
migration path from OS/390 R10 to z/OS V1R1 136 System Automation for OS/390
migration path from OS/390 R6 to z/OS V1R1 98 minimum version and release requirements 226
migration path from OS/390 R7 to z/OS V1R1 108 system layout, recommended 243
migration path from OS/390 R8 to z/OS V1R1 119 System SSL Crypto
migration path from OS/390 R9 to z/OS V1R1 129 migration path from OS/390 R7 to z/OS V1R1 108
software requirements 215 now called System SSL Security Level 3 19
will be removed from z/OS 24 System SSL Security Level 2
SOMobjects Service Classes migration path from OS/390 R8 to z/OS V1R1 119
no longer in OS/390 22 migration path from OS/390 R9 to z/OS V1R1 129
Sonoran Sans Serif Cond Font no longer in OS/390 22
minimum version and release requirements 226 System SSL Security Level 3
Sonoran Sans Serif Expand Font feature in z/OS 19
minimum version and release requirements 226 hardware requirements 238
Sonoran Sans Serif Font migration path from OS/390 R10 to z/OS V1R1 136
minimum version and release requirements 226 migration path from OS/390 R6 to z/OS V1R1 98
Sonoran Sans Serif Head Font migration path from OS/390 R7 to z/OS V1R1 109
minimum version and release requirements 226 migration path from OS/390 R8 to z/OS V1R1 120
Sonoran Serif Font migration path from OS/390 R9 to z/OS V1R1 129
minimum version and release requirements 226 software requirements 215
system symbolics
Sonoran Serif Headline Font
with indirect volume serial support 184
minimum version and release requirements 226
SystemPac
space requirements
deciding if it’s for you 45
DASD 63
driving system software requirements
DASD utilization and performance 185
(dump-by-data-set) 48
minimum processor storage required to IPL 63
driving system software requirements (full volume
virtual storage migration considerations 149
dump) 53
SREL for installing z/OS 38
in CBPDO order 40 how you order 39
in ServerPac order 39 SMS active for allocation 50
in SystemPac order 40 target system preparation 51
statements, product policy what IBM does for you 40
introduction to 2 what you need to do 44
storage requirements what you receive from IBM 42
DASD 63 Systems Center, IBM
DASD space utilization and performance 185 flashes 35
minimum processor storage required to IPL 63 publications 35
virtual storage migration considerations 149 SystemView Automated Operations Network/MVS
StorWatch DFSMShsm Monitor minimum version and release requirements 226
minimum version and release requirements 226 SystemView for MVS Base
subsystem DLIB volume no longer in OS/390 22
recommended data sets on 177
subsystem target volume
recommended data sets on 175 T
subsystems target data sets
driving system software requirements 57 storage requirement 63
summary of changes target libraries (TLIBs)
to this book for z/OS V1R1 xiii recommended placement 172
to z/OS installation for V1R1 xiv TCP/IP
sysplex hardware requirements 239
rolling z/OS across systems 161 minimum version and release requirements 227
sysplex-related volume 1 part of Communications Server 6
recommended data sets on 180 software requirements 204
sysplex-related volume 2 TCP/IP for MVS CICS Sockets
recommended data sets on 180 software requirements 204

304 z/OS V1R1.0 Planning for Installation

TCP/IP for MVS IMS Sockets Tivoli NetView Performance Monitor for TCP/IP
software requirements 204 minimum version and release requirements 227
TCP/IP Kerberos DES Tivoli OPC
migration path from OS/390 R6 to z/OS V1R1 91 minimum version and release requirements 227
now in Communications Server Security Level 2 8 Tivoli Performance Reporter for OS/390
TCP/IP Kerberos Non-DES minimum version and release requirements 227
migration path from OS/390 R6 to z/OS V1R1 91 Tivoli Security Management
now in Communications Server Security Level 1 7 minimum version and release requirements 227
TCP/IP Offload Tivoli Service Desk for OS/390
no longer in OS/390 22 minimum version and release requirements 227
testing z/OS Tivoli Software Distribution
scheduling 160 minimum version and release requirements 227
Text Search Tivoli Software Distribution for OS/390
element in z/OS 19 minimum version and release requirements 227
hardware requirements 238 Tivoli Storage Manager
migration path from OS/390 R10 to z/OS V1R1 137 minimum version and release requirements 227
migration path from OS/390 R6 to z/OS V1R1 98 Tivoli User Administration
migration path from OS/390 R7 to z/OS V1R1 109 minimum version and release requirements 227
migration path from OS/390 R8 to z/OS V1R1 120 TLIBs
migration path from OS/390 R9 to z/OS V1R1 129 recommended placement 172
software requirements 215 TME 10 227
TIOC toleration 71
element in z/OS 19 TPNS
hardware requirements 238
minimum version and release requirements 227
migration path from OS/390 R10 to z/OS V1R1 137
training
migration path from OS/390 R6 to z/OS V1R1 98
for z/OS 34
migration path from OS/390 R7 to z/OS V1R1 109
IBM Global Campus Web site 34
migration path from OS/390 R8 to z/OS V1R1 120
phone enrollment 34
migration path from OS/390 R9 to z/OS V1R1 129
Transform Manager
software requirements 215
Tivoli Business Systems Manager part of Infoprint Server 14
minimum version and release requirements 227 TSO/E
Tivoli Data Exchange element in z/OS 20
minimum version and release requirements 227 hardware requirements 238
Tivoli Data Message Manager migration path from OS/390 R10 to z/OS V1R1 137
minimum version and release requirements 227 migration path from OS/390 R6 to z/OS V1R1 98
Tivoli Data Protection migration path from OS/390 R7 to z/OS V1R1 109
minimum version and release requirements 227 migration path from OS/390 R8 to z/OS V1R1 120
Tivoli Decision Support migration path from OS/390 R9 to z/OS V1R1 129
minimum version and release requirements 227 software requirements 215
Tivoli Enterprise Console TVOL1
minimum version and release requirements 227 recommended data sets on 172
Tivoli Information/Management TVOL2
minimum version and release requirements 227 recommended data sets on 173
Tivoli Inventory for OS/390 TVOLn
minimum version and release requirements 227 recommended data sets on 173
Tivoli Management Framework
element in z/OS 19
hardware requirements 238 U
migration path from OS/390 R10 to z/OS V1R1 137 Unicode 4
migration path from OS/390 R6 to z/OS V1R1 98 uninstalling
migration path from OS/390 R7 to z/OS V1R1 109 JES2 59
migration path from OS/390 R8 to z/OS V1R1 120 JES3 59
migration path from OS/390 R9 to z/OS V1R1 129 SDSF 59
software requirements 215 UNIX 20
Tivoli Manager for MQSeries unpriced features
minimum version and release requirements 227 introduction to 2
Tivoli Manager for OS/390 Upgrade Package
minimum version and release requirements 227 driving system software requirements 54
Tivoli NetView for OS/390 introduction to 38
minimum version and release requirements 227 ordering 62

Index 305
upgrades VisualLift RTE (continued)
hardware identifiers 63 migration path from OS/390 R9 to z/OS V1R1 130
software identifiers 30 no longer in OS/390 22
URL VM guest, z/OS as 201
for downloading Enhanced HOLDDATA 32 volume serial support, indirect
for IBM education information 34 use of 184
for IBM Global Services 39 volumes
for IBM Systems Center flashes 35 apportioning data sets to 170
for ISV products that support z/OS 61 VS FORTRAN
for product catalogs 60 minimum version and release requirements 228
for reader comments ii VS Pascal
for redbooks 35
minimum version and release requirements 228
for S/390 service information 32
VTAM
for S/390 Service Update Facility 32
hardware requirements 242
for ShopzSeries 39, 61
part of Communications Server 6
for SMP/E Planning and Migration Assistant 18
software requirements 204
for wizard edition of this book ix
for z/OS integration test 27
for z/OS product publications 35
summary of URLs in this book x
W
user exits Washington Systems Center flashes 35
positioning to use ServerPac 165 waves
user modifications definition of 42
positioning to use ServerPac 165 Wave 0 requirements 54
Wave 1 requirements 54
Wave 2 requirements 57
V Wave 3 requirements 57
vendor product DLIB volume Web address
recommended data sets on 177 for downloading Enhanced HOLDDATA 32
vendor product target volume for IBM education information 34
recommended data sets on 175 for IBM Global Services 39
vendor products for IBM Systems Center flashes 35
choosing 61 for ISV products that support z/OS 61
virtual storage required for product catalogs 60
migration considerations 149 for reader comments ii
VisualAge COBOL Millenium Language Extensions for for redbooks 35
MVS & VM for S/390 service information 32
minimum version and release requirements 227 for S/390 Service Update Facility 32
VisualAge COBOL Millenium Language Extensions for for ShopzSeries 39, 61
OS/390 & VM for SMP/E Planning and Migration Assistant 18
minimum version and release requirements 228 for wizard edition of this book ix
VisualAge for Java for z/OS integration test 27
minimum version and release requirements 228 for z/OS product publications 35
VisualAge Generator Server summary of addresses in this book x
minimum version and release requirements 228 WebSphere Application Server
VisualAge PL/I migration path from OS/390 R6 to z/OS V1R1 98
minimum version and release requirements 228 migration path from OS/390 R7 to z/OS V1R1 110
VisualAge PL/I Millenium Language Extensions migration path from OS/390 R8 to z/OS V1R1 120
minimum version and release requirements 228 migration path from OS/390 R9 to z/OS V1R1 130
VisualAge Smalltalk Server no longer in OS/390 23
minimum version and release requirements 228 WebSphere Application Server for OS/390
VisualLift ADE minimum version and release requirements 228
migration path from OS/390 R6 to z/OS V1R1 98 WebSphere Commerce Suite
migration path from OS/390 R7 to z/OS V1R1 109 minimum version and release requirements 228
migration path from OS/390 R8 to z/OS V1R1 120 WebSphere Host Publisher
migration path from OS/390 R9 to z/OS V1R1 129 minimum version and release requirements 228
no longer in OS/390 22 withdrawn products (from marketing)
VisualLift RTE reinstalling 165
migration path from OS/390 R6 to z/OS V1R1 98 wizards 35
migration path from OS/390 R7 to z/OS V1R1 109 WLM compatibility mode
migration path from OS/390 R8 to z/OS V1R1 120 will be removed from z/OS 24

306 z/OS V1R1.0 Planning for Installation

WLR z/VM guest, z/OS as 201
minimum version and release requirements 228 z900 servers
World Wide Web address BCP functions that require 229
for downloading Enhanced HOLDDATA 32 supported by z/OS 62
for IBM education information 34
for IBM Global Services 39
for IBM Systems Center flashes 35
for ISV products that support z/OS 61
for product catalogs 60
for reader comments ii
for redbooks 35
for S/390 service information 32
for S/390 Service Update Facility 32
for ShopzSeries 39, 61
for SMP/E Planning and Migration Assistant 18
for wizard edition of this book ix
for z/OS integration test 27
for z/OS product publications 35
summary of addresses in this book x

X
X.25 NPSI
minimum version and release requirements 228
X.25 SNA Interconnection
minimum version and release requirements 228
X.25 SNA NSF
minimum version and release requirements 228
XCF (cross-system coupling facility)
hardware requirements 230
XCF signalling in a global resource serialization
complex 229
XML Toolkit for OS/390
minimum version and release requirements 228

Z
z/Architecture
in migration scenarios 83
introduction 1
required mode on z900 63
z/OS
DASD storage requirements 63
installation methods 37
introduction 1
list of base elements 3
list of optional features 3
z/OS Select
for installing z/OS 39
z/OS UNIX System Services
element in z/OS 20
hardware requirements 239
kernel 4
migration path from OS/390 R10 to z/OS V1R1 137
migration path from OS/390 R6 to z/OS V1R1 99
migration path from OS/390 R7 to z/OS V1R1 110
migration path from OS/390 R8 to z/OS V1R1 121
migration path from OS/390 R9 to z/OS V1R1 130
software requirements 215
z/OS UNIX System Services Application Services
in z/OS UNIX System Services 20

Index 307
308 z/OS V1R1.0 Planning for Installation
Readers’ Comments — We’d Like to Hear from You
z/OS
Planning for Installation
Version 1 Release 1

Publication No. GA22-7504-01

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Overall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Accurate h h h h h
Complete h h h h h
Easy to find h h h h h
Easy to understand h h h h h
Well organized h h h h h
Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.
 ___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
GA22-7504-01 IBMR Along Line

_ _ _ _ _ _ _Fold
_ _ _ and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM Corporation
Department 55JA, Mail Station P384
2455 South Road
Poughkeepsie, NY 12601-5400

_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape

Cut or Fold
GA22-7504-01 Along Line
IBMR

Program Number: 5694-A01

Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.

GA22-7504-01