Demonstration Delivery & Support Vm/Esa 2.4.0 Demopkg System Reference Guide Release 4Q99

Demonstration Delivery & Support
VM/ESA 2.4.0 DEMOpkg System Reference Guide

Release 4Q99
Introduction to VM/ESA 2.4.0
2 VM/ESA 2.4.0 Reference Guide

VM/ESA 2.4.0 DEMOpkg System Reference Guide
Release 4Q99
Document Number VM4Q99R
4Q99
IBM Software Group

1507 LBJ Freeway

Dallas, TX 75234
ii VM/ESA 2.4.0 Reference Guide

Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Who Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Introduction to VM/ESA 2.4.0 DEMOpkg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
VM/ESA 2.4.0 DEMOpkg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
VM/ESA CMOS Product List by Market Segment . . . . . . . . . . . . . . . . . 5

Advanced Function Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - CMOS-VM . . . . . . . . . . . . . 5
Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Groupware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Networking Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Networking: Cooperative Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Systems Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
VM/ESA P/R390 Product List by Market Segment . . . . . . . . . . . . . . . 11

Advanced Function Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - P390-R390 . . . . . . . . . . . 11
Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Groupware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Networking Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Networking: Cooperative Software . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Systems Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Contents iii
System Component Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Accessing Common Minidisks . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
DirMaint Version 1.5.0 Customization . . . . . . . . . . . . . . . . . . . . . . . 19

DirMaint Version 1.5.0 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . 19
Customizing the CONFIG DATADVH File . . . . . . . . . . . . . . . . . . . . . . 19
Customizing the AUTHFOR CONTROL File . . . . . . . . . . . . . . . . . . . . 20
Customizing the EXTENT CONTROL File . . . . . . . . . . . . . . . . . . . . . 22
Customizing the USER INPUT File . . . . . . . . . . . . . . . . . . . . . . . . . 23
DirMaint Directory Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Rebuilding the DirMaint Directory Files . . . . . . . . . . . . . . . . . . . . . . . 25
Adding User IDs to the USER WITHPASS File . . . . . . . . . . . . . . . . . 25
Rebuilding the DirMaint Directory . . . . . . . . . . . . . . . . . . . . . . . . . 26
Checking DirMaint Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
DirMaint Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
CTRGEN Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Section 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Section 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Section 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Section 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Section 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Section 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Section 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Section 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Section 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Section 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
SYSTEM NETID File Customization . . . . . . . . . . . . . . . . . . . . . . . . 77

Changing the Node ID and CPU Serial Number . . . . . . . . . . . . . . . . . . 77
Changing the DIRECTORY Statement in the USER DIRECT File . . . . . . . . 78
Updating the Node ID in OfficeVision . . . . . . . . . . . . . . . . . . . . . . . . 79
Changing the HOSTS LOCAL File for TCP/IP . . . . . . . . . . . . . . . . . . . 80
Updating the Web Server IP Address . . . . . . . . . . . . . . . . . . . . . . . . 80
Migrating From An Existing CPU To A New CPU . . . . . . . . . . . . . . . . . 80
VM/ESA 2.4.0 DEMOpkg System Customization . . . . . . . . . . . . . . . . 81

VM/ESA System Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
CP Nucleus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
HCPSYS ASSEMBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
HCPBOX ASSEMBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
HCPRIO ASSEMBLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Customizing the HCPRIO File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Customizing the SYSTEM CONFIG File . . . . . . . . . . . . . . . . . . . . . . 82
Customizing the System Logos . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Accessing MAINT CF1 in Read/Write Mode . . . . . . . . . . . . . . . . . . . . 84
iv VM/ESA 2.4.0 Reference Guide

System Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
IPLing the VM/ESA 2.4.0 DEMOpkg System (Normally) . . . . . . . . . . . . 87

Retaining Existing Spool Files with a Cold/Warm Start . . . . . . . . . . . . . . 87
Changing the TOD Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Setting the Time and Date for the TOD Clock . . . . . . . . . . . . . . . . . . 87
Resetting the Time and Date for the TOD Clock . . . . . . . . . . . . . . . . 88
Continuing with the IPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
IPLing the VM/ESA 2.4.0 DEMOpkg (Optionally) . . . . . . . . . . . . . . . . 91

VM/ESA Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
RACF Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Changing Logon Passwords (Non-RACF) . . . . . . . . . . . . . . . . . . . . 95

Requirements for Changing Logon Passwords . . . . . . . . . . . . . . . . . . . 95
Using the GROUP_PW Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Verifying if Passwords Need to be Updated . . . . . . . . . . . . . . . . . . . 96
Defining the User ID Group Names . . . . . . . . . . . . . . . . . . . . . . . . 96
GROUP PASSWORD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
GROUP USERIDS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Invoking the GROUP_PW Exec . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Tips on Using the GROUP_PW Exec . . . . . . . . . . . . . . . . . . . . . . 98
VM/ESA 2.4.0 DEMOpkg System Backup . . . . . . . . . . . . . . . . . . . . 99

Using the DASD Dump/Restore (DDR) Program . . . . . . . . . . . . . . . . . . 99
Named Saved System (NSS) and IMG File Backup/Restore . . . . . . . . 103

Backing Up the NSS and IMG Data Files . . . . . . . . . . . . . . . . . . . . . 103
Restoring the NSS and IMG Data Files . . . . . . . . . . . . . . . . . . . . . . 104
Generating a New NCP for the 3745 . . . . . . . . . . . . . . . . . . . . . . 105

Loading the New NCP to the 3745 . . . . . . . . . . . . . . . . . . . . . . . . . 105
Loading an OS/390 Job to the 3745 . . . . . . . . . . . . . . . . . . . . . . . . 105
Web Server Demo Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Enterprise/View Text Browser Demo Access . . . . . . . . . . . . . . . . . . . 107
User ID Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
User ID Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Authorizing OfficeVision/VM Users . . . . . . . . . . . . . . . . . . . . . . . . . 111
Adding Users to the UAD File . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Authorizing Users for SQL/DS . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Authorizing Users for Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Contents v
Center Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
CCBACKUP System Version 1.3 . . . . . . . . . . . . . . . . . . . . . . . . . 117

Enhancements with Version 1.2 . . . . . . . . . . . . . . . . . . . . . . . . . 117
Enhancements with Version 1.3 . . . . . . . . . . . . . . . . . . . . . . . . . 117
Basic CCBACKUP Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
CCBACKUP Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Backup Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Auto/Manual Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
View Backup Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Problem Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
CCBACKUP Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Stream Update Error Reference . . . . . . . . . . . . . . . . . . . . . . . . . 126
System Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Master Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Field Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Group/Change Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
DASD Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Print Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Tape Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Using the QTAPE Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Using the VTAPE Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
CCCMD Control Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Using the CTRFMT DASD Formatting Tool . . . . . . . . . . . . . . . . . . 139

Formatting and Allocating Spool Packs . . . . . . . . . . . . . . . . . . . . . . 141
Using the CTRACNT Tool 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

First Time Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Changing CTRACNT Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
VTAMOPER User ID Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
FCONMON Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
VMLINK Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Emergency Operations Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Alternate Nucleus IPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Restoring from Backup Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Restoring a System Volume Example . . . . . . . . . . . . . . . . . . . . . . . 159
Restoring D240R1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Specific Minidisk Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Environmental Record Editing and Printing Program (EREP) . . . . . . . 165

Processing EREP Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
vi VM/ESA 2.4.0 Reference Guide

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Appendix A. DISKMAP of the VM/ESA 2.4.0 DEMOpkg System . . . . . 169
Appendix B. Standard Device Addresses for the IBM Center . . . . . . . 187
Appendix C. DB2/VM Database Machines . . . . . . . . . . . . . . . . . . . 193
Appendix D. Tips and Techniques . . . . . . . . . . . . . . . . . . . . . . . 195

Creating the Stand-Alone Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Listing a Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Saving a Trip to the Master Console . . . . . . . . . . . . . . . . . . . . . . . . 196
Finding Maintenance User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Using the USERID Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Appendix E. Logging On VMUSERnn . . . . . . . . . . . . . . . . . . . . . 199

Executing the Product Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Customizing the User ID for a Specific Demonstration . . . . . . . . . . . . . 199
VMLINK Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Appendix F. Summary of DirMaint Syntax Commands . . . . . . . . . . . 203
Appendix G. Shared File System (SFS) . . . . . . . . . . . . . . . . . . . . 205

SFS Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Adding Space to an Existing SFS . . . . . . . . . . . . . . . . . . . . . . . . . 206
Appendix H. QDIR PACKAGE . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Appendix I. VM/ESA DEMOpkg Support . . . . . . . . . . . . . . . . . . . . 209

VM/ESA DEMOpkg FAQs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
DEMOpkg Help Desk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Remote Demonstrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Contents vii
viii VM/ESA 2.4.0 Reference Guide

Figures
1. CTRGEN Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2. Step Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3. Step Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4. Step Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5. Save HELPINST Step Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6. Save CMS INSTSEG Step Menu . . . . . . . . . . . . . . . . . . . . . . . 35
7. CTRXEDIT Step Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8. CTRXEDIT Step 1 Response . . . . . . . . . . . . . . . . . . . . . . . . . 37
16. CTRGEN CP Nucleus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
17. CP Nucleus Step 1 Response . . . . . . . . . . . . . . . . . . . . . . . . . 48
24. CTRGEN CMS Nucleus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
25. CMS Nucleus Step 1 Response . . . . . . . . . . . . . . . . . . . . . . . . 57
34. CTRGEN GCS Nucleus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
35. GCS Nucleus Step 1 Response . . . . . . . . . . . . . . . . . . . . . . . . 67
36. GCS Group - Primary Option Menu Step 2 Response . . . . . . . . . . . 68
42. List Missing USERS in GROUP USERID Step Menu . . . . . . . . . . . . 73
43. Change You Password Step Menu . . . . . . . . . . . . . . . . . . . . . . 74
44. Check the GROUP Userid for Errors Step Menu . . . . . . . . . . . . . . 75
45. Contents of SYSTEM NETID on MAINT 190 . . . . . . . . . . . . . . . . 77
46. CCBACKUP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
47. CCBACKUP Stream Update Display . . . . . . . . . . . . . . . . . . . . 118
48. CCBACKUP Status Display . . . . . . . . . . . . . . . . . . . . . . . . . 119
49. CCBACKUP Grp/Auto Schedule Display 1 . . . . . . . . . . . . . . . . . 120
50. CCBACKUP Grp/Auto Schedule Display 2 . . . . . . . . . . . . . . . . . 120
Figures ix
51. CCBACKUP Scheduler Display1 . . . . . . . . . . . . . . . . . . . . . . 121

52. CCBACKUP Scheduler Display 2 . . . . . . . . . . . . . . . . . . . . . . 121
54. CCBACKUP Scheduler Display 3 with Pre/Post Schedule . . . . . . . . 122
56. CCBACKUP View/Log Display 1 . . . . . . . . . . . . . . . . . . . . . . . 123
57. CCBACKUP View/Log Display 2 . . . . . . . . . . . . . . . . . . . . . . . 124
58. CCBACKUP Stream Update Display . . . . . . . . . . . . . . . . . . . . 126
59. Master/Maintenace Display 1 . . . . . . . . . . . . . . . . . . . . . . . . . 128
60. Master/Maintenance Display 2 . . . . . . . . . . . . . . . . . . . . . . . . 128
63. CCBACKUP Label/Print Display 1 . . . . . . . . . . . . . . . . . . . . . . 130
64. Sample Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
65. CCBACKUP Configuration Display 1 . . . . . . . . . . . . . . . . . . . . 132
69. CCBACKUP Configuration Display 4A . . . . . . . . . . . . . . . . . . . 133
x VM/ESA 2.4.0 Reference Guide

Tables
1. DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - CMOS-VM . . . . . . . . . . . 5
8. DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - P390-R390 . . . . . . . . . . 11
15. Message Log Message Codes . . . . . . . . . . . . . . . . . . . . . . . . . 51
21. Replacement Files for HCPBOX ASSEMBLE . . . . . . . . . . . . . . . . 81
22. PF Key Settings to Colorize System Logos . . . . . . . . . . . . . . . . . 83
23. CCBACKUP Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . 125
24. Stream Update Error Messages . . . . . . . . . . . . . . . . . . . . . . . 126
25. Virtual Addresses for Minidisk Restore . . . . . . . . . . . . . . . . . . . 163
Tables xi
xii VM/ESA 2.4.0 Reference Guide

Preface
The VM/ESA 2.4.0 DEMOpkg System Reference Guide should be used as a refer-
ence during the installation and customizing of the Demonstration Delivery &
Support (DD&S) VM/ESA 2.4.0 P/390, R/390 and CMOS DEMOpkg Systems. A
copy of this book can be found on the VM DEMOpkg web site at:
http://w3.demopkg.ibm.com/vmdemopkg/index.html
Who Should Use This Book

Read this guide if you are installing or customizing your VM/ESA 2.4.0 DEMOpkg
System. You should have a good skill base with VM before attempting to install or
customize your VM/ESA DEMOpkg System.
Feedback
We are interested in your suggestions and comments. See Appendix I, “VM/ESA
DEMOpkg Support” on page 209 for more information.
Preface xiii
xiv VM/ESA 2.4.0 Reference Guide

Trademarks
The following terms denoted by an asterisk (*) in this publication are trademarks of
other companies:
EnterpriseWeb/VM Server, EnterpriseWeb/Calendar, and Enterprise View Text
Browser are registered trademarks of NEON Beyond Acquisition Corporation.
VM:Webgateway Server, VM:Webgateway OfficeVision Interface and
VM:Webgateway CGI Extensions are registered trademarks of Sterling Soft-
ware, Inc.
These products are sold by IBM under a cooperative software agreement in the
United States. For information about sales or marketing agreements in other coun-
tries, contact Carol Kudritz:
e-Mail: KUDRITZ@US.IBM.COM
Tieline: 852-5686
Outside: 1-607-752-5686
Trademarks xv
xvi VM/ESA 2.4.0 Reference Guide

Introduction to VM/ESA 2.4.0 DEMOpkg

VM/ESA 2.4.0 DEMOpkg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
VM/ESA CMOS Product List by Market Segment . . . . . . . . . . . . . . . . . 5

Advanced Function Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Groupware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Networking Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Networking: Cooperative Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Systems Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
VM/ESA P/R390 Product List by Market Segment . . . . . . . . . . . . . . . 11

Advanced Function Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Groupware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Networking Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Networking: Cooperative Software . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Systems Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Introduction to VM/ESA 2.4.0 DEMOpkg 1


VM/ESA 2.4.0 DEMOpkg
Overview
The VM/ESA system is provided for IBM Internal Use Only. Appropriate program
products and offerings have been installed for connectivity.
The following DASD volumes make up the VM/ESA system:
PACKID P/390 CD Name R/390 CD CMOS Optional Other Information

Name 3490 Required
Tapes
D240R1 VMBASE VMBASE 1 Required The spool and page
space are on this and
D240B1.
D240B1 VMBASE VMBASE 1 Required R1 and B1 packs are the
minimum IPL Run packs
D240R2 VMOPT VMOPT 1 Optional SES pack for products on
R1.
D240B2 VMOPT VMOPT 1 Optional SES pack for products on
B1.
D240L1 VMOPT VMOPT 1 Optional Required for Business
Intelligent product use.
D240O1 VMOVWEB VMOVWEB 1 Optional Required for OfficeVision
and Web Server pro-
ducts.
D240S1 Not Available Not Available 1 Optional Has German/Japanese
NLS source files.
D240P1 Not Available Not Available 1 Optional Other product disks. Like
Publishing, 3745,
COBOL, etc.
D240P2 Not Available Not Available 1 Optional Other product disks. Like
Publishing, 3745,
COBOL, etc.
D240L1 Not Available Not Available 1 Optional Other usable demo
userids.
D240SP Not Available Not Available N/A Optional User defined/Created for
extra Page/Spool/Temp
Space.
Notes:
1. The volumes distributed with the system are mapped by the USER MDISKMAP file,
which is stored on MAINT 191.
2. Check your packing list. Volume D240O1 is not distributed to all users
because of marketing and legal restrictions.
3. RACF/VM is installed and working on this DEMOpkg System. Tips on how to
remove RACF is found in the Commands for the RACF Challenged.
VM/ESA 2.4.0 DEMOpkg 3


VM/ESA CMOS Product List by Market Segment
Advanced Function Printing
DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - CMOS-VM

Table 1. DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - CMOS-VM
Abbrev. Product Name Version Number
DCF Doc Composition Facility (ODF & SMFF) 1.4.0 5748-XX9
FLSF Font Library Service Facility 1.1.0 5668-890
Font APL2 Fonts 1.1.1 5771-ADB
Font Century Schoolbook 1.1.0 5771-ADJ
Font DATA1 1.1.1 5771-ADA
Font ITC Avant Garde Gothic 1.1.0 5771-ADL
Font ITC Souvenir 1.1.0 5771-ADQ
Font Mathematics and Science 1.1.0 5771-ADT
Font Monotype Garamond 1.1.0 5771-AFK
Font Pi and Specials 1.1.1 5771-ABC
Font Sonoran Sans Headliner 1.1.0 5771-ADW
Font Sonoran Sans Serif 1.1.1 5771-ABB
Font Sonoran Sans Serif Cond 1.1.0 5771-AFL
Font Sonoran Sans Serif Exp 1.1.0 5771-AFN
Font Sonoran Sans Serif Headliner 1.1.0 5771-ADX
Font Sonoran Serif 1.1.1 5771-ABA
GDQF Graphical Display and Query Facility 2.2.0 5688-169
IOS3270 Input/Output System/3270 3.5.27 5785-HAX
OGL Overlay Generation Language/370 1.1.0 5688-191
PMF/VM Print Management Facility/VM 1.1.0 5664-310
PPFA PagePrinter Formatting Aid/370 1.1.0 5688-190
PrintMgr SAA PrintManager 1.1.0 5688-179
PSAF Print Services Access Facility/VM 1.1.0 5664-312
PSF/VM Print Services Facility/VM 2.1.1 5684-141
VM3812 IBM 3812 Pageprinter VM Support 1.3.1 5798-DTE
Application Development
VM/ESA CMOS Product List by Market Segment 5


AD/C C/370 AD/Cycle C/370 1.2.0 5688-216
APL2 APL2 2.2.0 5688-228
APL2 AE APL2 Application Environment 2.2.0 5688-229
AS Application System (AS) 4.2.0 5648-092
ASSEMBLER/V High Level Assembler/VM 1.2.0 5696-234
BASIC IBM BASIC 1.2.0 5668-996
COBOL COBOL for MVS & VM 1.2.0 5688-197
COBOL/SF COBOL Structure Facitity 2.2.0 5696-737
CODE/370 CODE/370 1.2.0 5688-194
C/370 C/370 Common Library 1.2.0 5688-082
C/370-LIB C/370 Library Compiler and Library 2.2.0 5688-188
C/390 IBM C for VM/ESA 3.1.0 5654-033
FORTRAN VS FORTRAN 2.5.0 5668-806
ISPF VM Interactive System Product Facility for VM 3.2.0 5684-043
ISPF/PDF Interactive System Product Facility for VM 3.2.0 5684-123
LE/370 Language Environment/370 1.8.0 5654-030
NEATWIND NEATWIND 7.4.0 Internal
Pascal Pascal Runtime Library 1.2.0 5668-767
PASCAL VS PASCAL 1.2.0 5688-767
PLI PLI 1.1.1 5688-235
REXX/370 COMP REXX/370 Compiler 1.3.0 5695-013
REXX/370 LIB REXX/370 Library 1.3.0 5695-014
RPG/VM Report Program Generator 1.1.0 5688-127
VS COBOL II VS COBOL II 1.3.2 5668-958
Data Management

Table 3 (Page 1 of 2). DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - CMOS-VM
Backup/Restore DB 2 for VM (Backup/Restore) 5.1.0 5648-158
Control Center DB 2 for VM (Control Center) 5.1.0 5648-158
DataRefresher DataRefresher 1.1.0 5696-703
DB Support DB 2 for VM(DB Support) 5.1.0 5648-158
DB2 DB 2 for VM 5.1.0 5648-158
DPROP R DB 2 for VM (DPROP R) 5.1.0 5648-158
DRDA-ARAS DB 2 for VM (DRDA-ARAS) 5.1.0 5648-158
GDDM/GKS GDDM Graphics Kernal System 1.1.3 5668-802
GDDM/IMD GDDM Interactive Map Definition 2.1.3 5668-801


GDDM/IVU GDDM Image View Utility 1.1.3 5668-723
GDDM/PGF GDDM Presentation Graphics Feature 2.1.3 5668-812
GDDM/VM GDDM with OS2LINK, PCLK, REXX, VMMM, NLS 3.2.0 5684-168
IGES Initial Graphics Exchange Spec Proc 2.3.0 5688-047
QMF Query Management Facility 3.3.0 5706-255
REXX/SQL DB 2 for VM (REXX/SQL) 5.1.0 5648-158
Groupware

BkMgr Build BookManager BUILD 1.3.0 5684-026
BkMgr READ BookManager READ 1.3.0 5684-062
BookMaster BookMaster 1.4.0 5688-015
BrowseMaster BrowseMaster 2.1.0 5688-224
CALS CALS Feature for Publishing 1.1.0 5664-387
DrawMaster DrawMaster 2.0.4 5664-388
DW/370 Displaywrite/370 2.1.0 5684-091
ESA/CAL ESA Calendar Feature 1.2.0 5684-084
IHF Image Handling Facility 2.1.2 5664-363
OV/VM OfficeVision/VM 1.4.0 5684-084
ProcessMaster ProcessMaster with Critique 1.3.1 5664-387
PSPSI Publishing System Postscript Interperter 1.3.2 5688-104
SearchManager SearchManager/370 for VM 1.1.0 5684-143
TextTagger TextTagger for Publishing/ESA 1.1.1 5648-010
Networking Systems

ACF/NCP Network Control Program 7.3.0 5684-063
ACF/SSP System Support Program 4.3.0 5654-009
APPC APPC Application Suite 1.1.0 5624-025
EP Emulator Program 1.11.0 5735-XXB
IBM Netwk Stn IBM Network Station 1.3.0 5648-C05
LFS/ESA LAN File Services/ESA 1.1.2 5648-039


PVM VM/Pass-Through Facility 2.1.1403 5684-100
RSCS Remote Spooling Communications Subsystems 3.2.0 5684-096
TCP/IP TCPIP/VM - KERB FL320 5654-030
TCP/IP Transmission Control Protocol/ Internet Protocol/VM FL320 5654-030
VM/ESA (GCS) VM/ESA GCS 2.4.0 5654-030
VM/ESA (OSA) VM/ESA Open System Architecture 2.4.0 5654-030
VTAM Virtual Telecommunications Access Method 4.2.0 5654-010
Networking: Cooperative Software

ECAL EnterpriseWeb/Calendar 1996, By Beyond Software Inc. 1.2.0
EVIEW Enterprise View Text Browser 1996, By Beyond Software 1.1.0
Inc.
EWEB EnterpriseWeb/VM Server 1996, By Beyond Software Inc. 1.4.0
VMWEB VM:Webgateway Web Server 1998, By Sterling Software 3.0
Inc.
VMWEBGW VM:Webgateway CGI Extentions 1998, By Sterling Soft- 3.0
ware Inc.
VMWEBOV VM:Webgateway OV/VM Interface 1998, By Sterling Soft- 3.0
ware Inc.
Systems Management

ADSM ADSTAR Distributed Storage Manager 3.1.0 5684-A09
CUF CMS Utilities Feature 1.1.1 5684-112
DFSORT DFSORT for CMS 2.1.0 5684-134
DITTO DITTO for VM/ESA 1.2.0 5654-029
DMS Display Management System 2.1.0 5684-113
EREP Error Record and Evironment Procedures 3.5.0 5654-260
FCONX FCON Performance Monitor 3.1.01
FFST First Failure Support Technology 1.2.0 5684-158
Font 3800 Printer Image Library n/a 5684-112
ICKDSF Device Support Facilities - Standalone 1.16.0 5747-DS1


ICKDSF/CMS Device Support Facilities/CMS 1.16.0 5684-042
IXFP IBM Extended Facilities Product (SJB2210) 2.1.0 5648-A17
LANRES LAN Resource Extension and Services/VM 1.1.0 5684-142
NetView NetView 2.3.0 5756-051
NFTP NetView File Transfer Program 1.1.0 5664-281
NLS-German German NLS Feature 2.4.0 5654-030
NLS-Kanji Kanji NLS Feature 2.4.0 5654-030
NV Perf Mon NetView Performance Monitor 2.1.0 5654-011
NVAS NetView/Access Services 1.3.2 5684-028
RACF/VM Resource Access Control Facility/VM 1.10.0 5740-XXH
RTM Real Time Monitor/ESA 1.5.2 5798-DWD
SAS SAS/C Run Time Library (SSKP112V) 1.2.1 5648-A17
SLM Software License Monitor 1.1.1 5648-038
SnapShot IBM RAMAC SnapShot 1.1.0 5654-A03
VM Batch VM Batch 2.1.0 5684-137
VM/DIRM VM/DIRMAINT 1.5.0 5748-XE4
VM/ESA VM/Enterprise System Architecture 2.4.0 5654-030
VM/ESA (CMS) VM/ESA Conversational Monitoring System 2.4.0 5654-030
VM/ESA (CP and DVF) VM/ESA Control Program and Dump View Facility 2.4.0 5654-030
VM/ESA (DCE) VM/ESA OpenEdition DCE 2.4.0 5654-030
VM/ESA (DCE) VM/ESA OpenEdition DCE - KERB DES 2.4.0 5654-030
VM/ESA (GUI) VM/ESA Graphical User Interface 2.4.0 5654-030
VM/ESA (Online VM/ESA Online Library 2.4.0 5654-030
Library)
VM/ESA (OpenE) VM/ESA Open Edition Shell & Utilities 2.4.0 5654-030
VM/ESA (RSCS) VM/ESA RSCS 2.4.0 5654-030
VM/ESA (S Disk VM/ESA (S Disk Extentions) 2.3.0 5654-030
Extentions)
VM/ESA (TCP/IP 320) VM/ESA TCP/IP 2.4.0 5654-030
VM/ESA (TSAF & AVS) VM/ESA TSAF & AVS 2.4.0 5654-030
VM/ESA (VMSES/E) VM/ESA VMSES/E 2.4.0 5654-030
VSAM Virtual Storage Access Method 6.1.0 5686-081


VM/ESA P/R390 Product List by Market Segment
Advanced Function Printing
DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - P390-R390

Table 8. DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - P390-R390
IOS3270 Input/Output System/3270 3.5.27 5785-HAX
Application Development

ASSEMBLER/V High Level Assembler/VM 1.2.0 5696-234
C/370 C/370 Common Library 1.2.0 5688-082
C/370-LIB C/370 Library Compiler and Library 2.2.0 5688-188
C/390 IBM C for VM/ESA 3.1.0 5654-033
ISPF VM Interactive System Product Facility for VM 3.2.0 5684-043
ISPF/PDF Interactive System Product Facility for VM 3.2.0 5684-123
LE/370 Language Environment/370 1.8.0 5654-030
NEATWIND NEATWIND 7.4.0 Internal
Pascal Pascal Runtime Library 1.2.0 5668-767
REXX/370 COMP REXX/370 Compiler 1.3.0 5695-013
REXX/370 LIB REXX/370 Library 1.3.0 5695-014
Data Management

Table 10 (Page 1 of 2). DEMOpkg VM/ESA 2.4.0 Products - 4Q99 - P390-R390
Backup/Restore DB 2 for VM (Backup/Restore) 5.1.0 5648-158
Control Center DB 2 for VM (Control Center) 5.1.0 5648-158
DB Support DB 2 for VM(DB Support) 5.1.0 5648-158
DB2 DB 2 for VM 5.1.0 5648-158
DPROP R DB 2 for VM (DPROP R) 5.1.0 5648-158
VM/ESA P/R390 Product List by Market Segment 11


DRDA-ARAS DB 2 for VM (DRDA-ARAS) 5.1.0 5648-158
GDDM/GKS GDDM Graphics Kernal System 1.1.3 5668-802
GDDM/IMD GDDM Interactive Map Definition 2.1.3 5668-801
GDDM/IVU GDDM Image View Utility 1.1.3 5668-723
GDDM/PGF GDDM Presentation Graphics Feature 2.1.3 5668-812
GDDM/VM GDDM with OS2LINK, PCLK, REXX, VMMM, NLS 3.2.0 5684-168
QMF Query Management Facility 3.3.0 5706-255
REXX/SQL DB 2 for VM (REXX/SQL) 5.1.0 5648-158
Groupware

ESA/CAL ESA Calendar Feature 1.2.0 5684-084
OV/VM OfficeVision/VM 1.4.0 5684-084
Networking Systems

APPC APPC Application Suite 1.1.0 5624-025
IBM Netwk Stn IBM Network Station 1.3.0 5648-C05
LFS/ESA LAN File Services/ESA 1.1.2 5648-039
PVM VM/Pass-Through Facility 2.1.1403 5684-100
RSCS Remote Spooling Communications Subsystems 3.2.0 5684-096
TCP/IP TCPIP/VM - KERB FL320 5654-030
TCP/IP Transmission Control Protocol/ Internet Protocol/VM FL320 5654-030
VM/ESA (OSA) VM/ESA Open System Architecture 2.4.0 5654-030
VTAM Virtual Telecommunications Access Method 4.2.0 5654-010

Networking: Cooperative Software

ECAL EnterpriseWeb/Calendar 1996, By Beyond Software Inc. 1.2.0
EVIEW Enterprise View Text Browser 1996, By Beyond Software 1.1.0
Inc.
EWEB EnterpriseWeb/VM Server 1996, By Beyond Software Inc. 1.4.0
VMWEB VM:Webgateway Web Server" 1998, By Sterling Software 3.0
Inc.
VMWEBGW VM:Webgateway CGI Extentions 1998, By Sterling Soft- 3.0
ware Inc.
VMWEBOV VM:Webgateway OV/VM Interface 1998, By Sterling Soft- 3.0
ware Inc.
Systems Management

ADSM ADSTAR Distributed Storage Manager 3.1.0 5684-A09
CUF CMS Utilities Feature 1.1.1 5684-112
DITTO DITTO for VM/ESA 1.2.0 5654-029
EREP Error Record and Evironment Procedures 3.5.0 5654-260
FCONX FCON Performance Monitor 3.1.01
FFST First Failure Support Technology 1.2.0 5684-158
ICKDSF Device Support Facilities - Standalone 1.16.0 5747-DS1
ICKDSF/CMS Device Support Facilities/CMS 1.16.0 5684-042
IXFP IBM Extended Facilities Product (SJB2210) 2.1.0 5648-A17
NFTP NetView File Transfer Program 1.1.0 5664-281
RACF/VM Resource Access Control Facility/VM 1.10.0 5740-XXH
SAS SAS/C Run Time Library (SSKP112V) 1.2.1 5648-A17
SLM Software License Monitor 1.1.1 5648-038
SnapShot IBM RAMAC SnapShot 1.1.0 5654-A03
VM/DIRM VM/DIRMAINT 1.5.0 5748-XE4
VM/ESA VM/Enterprise System Architecture 2.4.0 5654-030
VM/ESA (CMS) VM/ESA Conversational Monitoring System 2.4.0 5654-030
VM/ESA (CP and DVF) VM/ESA Control Program and Dump View Facility 2.4.0 5654-030
VM/ESA (DCE) VM/ESA OpenEdition DCE 2.4.0 5654-030
VM/ESA (DCE) VM/ESA OpenEdition DCE - KERB DES 2.4.0 5654-030
VM/ESA P/R390 Product List by Market Segment 13


VM/ESA (GUI) VM/ESA Graphical User Interface 2.4.0 5654-030
VM/ESA (Online VM/ESA Online Library 2.4.0 5654-030
Library)
VM/ESA (OpenE) VM/ESA Open Edition Shell & Utilities 2.4.0 5654-030
VM/ESA (RSCS) VM/ESA RSCS 2.4.0 5654-030
VM/ESA (S Disk VM/ESA (S Disk Extentions) 2.3.0 5654-030
Extentions)
VM/ESA (TCP/IP 320) VM/ESA TCP/IP 2.4.0 5654-030
VM/ESA (TSAF & AVS) VM/ESA TSAF & AVS 2.4.0 5654-030
VM/ESA (VMSES/E) VM/ESA VMSES/E 2.4.0 5654-030
VSAM Virtual Storage Access Method 6.1.0 5686-081

System Component Customization

Accessing Common Minidisks . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
DirMaint Version 1.5.0 Customization . . . . . . . . . . . . . . . . . . . . . . . 19

DirMaint Version 1.5.0 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . 19
Customizing the CONFIG DATADVH File . . . . . . . . . . . . . . . . . . . . . . 19
Customizing the AUTHFOR CONTROL File . . . . . . . . . . . . . . . . . . . . 20
Customizing the EXTENT CONTROL File . . . . . . . . . . . . . . . . . . . . . 22
Customizing the USER INPUT File . . . . . . . . . . . . . . . . . . . . . . . . . 23
DirMaint Directory Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Rebuilding the DirMaint Directory Files . . . . . . . . . . . . . . . . . . . . . . . 25
DirMaint Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
CTRGEN Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Section 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Section 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Section 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Section 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Section 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Section 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Section 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Section 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Section 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Section 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
SYSTEM NETID File Customization . . . . . . . . . . . . . . . . . . . . . . . . 77

Changing the Node ID and CPU Serial Number . . . . . . . . . . . . . . . . . . 77
Changing the DIRECTORY Statement in the USER DIRECT File . . . . . . . . 78
Updating the Node ID in OfficeVision . . . . . . . . . . . . . . . . . . . . . . . . 79
Changing the HOSTS LOCAL File for TCP/IP . . . . . . . . . . . . . . . . . . . 80
Updating the Web Server IP Address . . . . . . . . . . . . . . . . . . . . . . . . 80
Migrating From An Existing CPU To A New CPU . . . . . . . . . . . . . . . . . 80
VM/ESA 2.4.0 DEMOpkg System Customization . . . . . . . . . . . . . . . . 81

VM/ESA System Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Customizing the HCPRIO File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Customizing the SYSTEM CONFIG File . . . . . . . . . . . . . . . . . . . . . . 82
Customizing the System Logos . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
System Component Customization 15


Accessing Common Minidisks

An exec called CTRDISKS has been created and placed on the 19E Y-disk. This
exec accesses the following minidisks:
MAINT 325 as W/W
MAINT 31A as X/X
For compatibility, the old DTRIPF exec is also on the Y-disk, but it has been
changed to only call the CTRDISKS exec.
MAINT 325 is a 50 cylinder minidisk that contains products and tools, plus DD&S
written execs shipped with the system. ISPVM 192 contains the ISPF and ISPF/PDF
code.
Accessing Common Minidisks 17


DirMaint Version 1.5.0 Customization

The following four files, which affect the operation of the DirMaint virtual machine,
are distributed with the P/390 and R/390 System:
CONFIG DATADVH
AUTHFOR CONTROL
EXTENT CONTROL
USER INPUT
All of the files exist on the DirMaint maintenance machine called, P748XE4M.
Information about DirMaint Version 1.5.0 can be obtained from the manuals or from
the online help menus. To access the online help menus, Enter:
----> dirm help
DirMaint Version 1.5.0 Enhancements

The major differences between DirMaint Version 1.4.0 and Version 1.5.0 are:
The command syntax has changed from DIRM GET userid to DIRM FOR
userid GET.
The command to activate the current EXTENT CONTROL file has changed from
DIRM RLDD to DIRM RLDExtn. Version 1.5.0 no longer issues the RLDExtn func-
tion automatically after the RLDdata function.
It is much easier to initialize a new USER INPUT file with DirMaint Version 1.5.0
The start up command for the DirMaint and DATAMOVE machines has changed
to DVHBEGIN.
The maintenance user ID is P748XE4M.
We have installed DirMaint Version 1.5.0 with three DATAMOVE machines. The
user IDs are DATAMOVE, DATAMOV2, and DATAMOV3.
For information on how to add or delete the defined DATAMOVE machines, refer
to the DirMaint Tailoring and Administration Guide, SC23-0533.
Customizing the CONFIG DATADVH File

CONFIG DATADVH is the configuration file for DirMaint Version 1.5.0. Node or user ID
changes are not required to run your system. It contains installation specific cus-
tomizing options for the DirMaint system. For more information on the various
options available, refer to the Directory Maintenance VM/ESA Tailoring and Admin-
istration Guide, SC23-0533.
The most important specifications made in this file concern:

How is password monitoring, warning, and user lockout implemented?
To customize the CONFIG DATADVH file, complete the following steps:

1. Logon to DIRMAINT
DirMaint Version 1.5.0 Customization 19

There is no logmsg data

FILES: NO RDR, 7 PRT, NO PUN
RECONNECTED AT 13:52:32 CDT TUESDAY 5/ 4/99
2. Press Enter
DVHWAI2146I Wakeup caused by console attention on 99/ 5/ 4 at 13:53:26.
DVHWAI2 2A Manual re-start is required for DIRMAINT. Enter
DVHWAI2 2A "DVHBEGIN" or "DVHWAIT" when ready to re-start.
DIRMAINT DEMOVM.. - 1999/ 5/ 4; T= .29/ .32 13:53:27
3. To Xedit the CONFIG DATADVH file on the D-disk, Enter:
----> x config datadvh d

4. When you have finished editing the file, Enter:
----> dvhbegin
DIRMAINT DEMOVM.. - 1999/ 5/ 4; T=2.44/2.63 13:58:14
DVHWAI214 I Waiting for work on 99/ 5/ 4 at 13:58:14.

5. To disconnect from DirMaint, Enter:
----> #cp disc
Customizing the AUTHFOR CONTROL File

The AUTHFOR CONTROL file is used to add or remove authorized DirMaint administra-
tors. It controls the adminstrative user IDs, the command set they are allowed to
use, and the types of commands they can issue. For more information on the
command classes, their descriptions, and use, refer to the DirMaint Tailoring and
Adminstration Guide, SC23-0533.
To authorize a user ID to no longer need a password to execute DirMaint com-

mands, complete the following steps:
1. Copy the MAINT line and replace MAINT with your own user ID name
2. After DirMaint is restarted, Enter the command:
----> dirm for (userid) needpass no

By issuing this command the user will no longer be required to enter the user
ID password to execute any DirMaint commands.
To customize the AUTHFOR CONTROL file, complete the following steps:

There is no logmsg data
FILES: NO RDR, 7 PRT, NO PUN
RECONNECTED AT 13:52:32 CDT TUESDAY 5/ 4/99
2. Press Enter
DVHWAI2146I Wakeup caused by console attention on 99/ 5/ 4 at 13:53:26.
DVHWAI2 2A Manual re-start is required for DIRMAINT. Enter
DVHWAI2 2A "DVHBEGIN" or "DVHWAIT" when ready to re-start.
DIRMAINT DEMOVM.. - 1999/ 5/ 4; T= .29/ .32 13:53:27
3. To Xedit the AUTHFOR CONTROL file on the E-disk, Enter:

----> x authfor control e

4. When you have finished editing the file, Enter:
----> dvhbegin

----> #cp disc
Customizing the EXTENT CONTROL File

The EXTENT CONTROL file has a changed format, but is still used to tell DirMaint infor-
mation about the DASD volumes and the regions that DirMaint can use to map mini-
disks onto. If DirMaint is used to control entries in the USER DIRECT file, then
DirMaint needs to know information about the DASD under its' control.
The most important specifications made in the file concern:

The regions within each volume that DirMaint can control.
The groups that each volume is associated with.
The user exclude list.
To customize the EXTENT CONTROL file, complete the following steps:

1. Logon to MAINT
2. Enter the following commands:
----> dirm send extent control

DVHXMT1191I Your SEND request has been sent for processing.
Ready; T= .48/ .54 14:24:17
DVHREQ2288I Your SEND request for MAINT at has been accepted.
RDR FILE 6 SENT FROM DIRMAINT PUN WAS 7 RECS 83 CPY 1 A NOHOL
DVHREQ2289I Your SEND request for MAINT at has completed; with RC =
----> RECEIVE yyyy (REPLACE

where yyyy is the same file number that appears in step 2.
File EXTENT CONTROL A2 replaced by EXTENT CONTROL E2 received from
DIRMAT at DEMOVM
Ready; T= . 6/ .11 14:26:46
3. To Xedit the EXTENT CONTROL file on the A-Disk, Enter:
----> x extent control a

4. When finished and you have filed your changes, Enter:
----> dirm file extent control

PUN FILE 7 SENT TO DIRMAINT RDR AS 8 RECS 87 CPY 1 NOHOL
DVHXMT1191I Your FILE request has been sent for processing.
Ready; T= .53/ .62 14:3 :13
DVHREQ2288I Your FILE request for MAINT at has been accepted.
DVHRCV3821I File EXTENT CONTROL E2 has been received; RC = .
DVHREQ2289I Your FILE request for MAINT at has completed; with RC =

----> dirm rldextnt

DVHXMT1191I Your RLDEXTN request has been sent for processing.
Ready; T= .47/ .52 14:32:27
DVHREQ2288I Your RLDEXTN request for MAINT at has been accepted.
DVHILZ351 I Starting DVHINITL with directory: USER DIRECT E
DVHILZ351 I DVHINITL Parms: BLDMONO BLDDASD BLDLINK
DVHIZD3528W One or more DASD volume control files were created using
DVHIZD3528W default values for device characteristics.
DVHREQ2289I Your RLDEXTN request for MAINT at has completed; with R
DVHREQ2289I .
Customizing the USER INPUT File

The USER INPUT file loads the DirMaint machine with a current copy of the USER
DIRECT file. A current copy of this file labeled USER WITHPASS is kept on MAINT 191.
More information on how to load the DirMaint machine with the latest USER
WITHPASS file will be covered in “Rebuilding the DirMaint Directory Files” on
page 25.


DirMaint Directory Maintenance

DirMaint is the preferred way of performing directory maintenance. The P/390 and
R/390 may use a manual method of changing the VM/ESA directory statements, but
we choose to use DirMaint. The differences between DirMaint Version 1.4.0 and
Version 1.5.0 become evident the more you use the commands. You will find a list
of the more useful commands and their syntax in Appendix F, “Summary of
DirMaint Syntax Commands” on page 203.
When adding users to the directory, DirMaint Version 1.5.0 provides the submitter
with a greater number of messages. You will receive a message when you add a
user ID and also for each LINK or MDISK statement.
Rebuilding the DirMaint Directory Files

Sometimes adding a large number of users can be accomplished quicker by
rebuilding the DirMaint directory files. We did not choose to sort the directory with
this release of the VM/ESA 2.4.0 DEMOpkg System. Rebuilding the directory files
enables you to group the added user IDs into blocks or groups of user IDs that can
be easily moved. New entries are always placed at the end of the USER DIRECT file.
Adding User IDs to the USER WITHPASS File

To add user IDs to the USER WITHPASS file, complete the following steps:
1. Logon to either MAINT or ADMIN
2. To get a copy of the current directory from DirMaint, Enter:
----> dirm user w

3. Receive the USER WITHPASS file
You can also use a current copy of the USER DIRECT file.
4. To rename the USER WITHPASS file to USER INPUT, Enter:
----> rename user withpass a = input =

5. Xedit the USER INPUT file and update the file with your user IDs
6. Update the DIRECTORY statement to reflect your node ID choice
Note: DirMaint will not work until this has been done.
7. To send the USER INPUT file to your reader, Enter:
----> sendfile user input a to dirmaint

8. To rename the USER INPUT file to USER WITHPASS, Enter:
----> rename user withpass a = input =

9. Disconnect from MAINT or ADMIN
DirMaint Directory Maintenance 25

Rebuilding the DirMaint Directory

To rebuild the directory, complete the following steps:
2. To stop DirMaint, press Enter twice
3. To find the file ID of the USER INPUT file in DirMaint's PUN, Enter:
----> q pun
4. To transfer the USER INPUT file from the punch to the reader, Enter:
----> TRAN PUN yyyy TO DIRMAINT RDR

where yyyy is the pun file number found by the Q PUN command.
5. To receive the USER INPUT file onto the E-Disk, Enter:
----> RECEIVE yyyy (REPL

where yyyy is the pun file number found by the Q PUN command.
6. To erase the USER DIRECT file on the E-Disk, Enter:
----> erase user direct e

7. To restart the DirMaint machine, Enter:
----> DVHBEGIN
DVHILZ351 I Starting DVHINITL with directory: USER INPUT E
DVHILZ351 I DVHINITL Parms: BLDMONO NOCRCWARN
DVHILZ351 I Starting DVHINITL with directory: USER TEMPDIR G
DVHILZ351 I DVHINITL Parms: BLDCLUSTER BLDLINK BLDDASD
DVHIZD3528W One or more DASD volume control files were created using
DVHIZD3528W default values for device characteristics.

----> #cp disc
Checking DirMaint Operations

To make sure DirMaint is operating properly, complete the following steps:
1. Logon to either MAINT or ADMIN
2. To make sure DirMaint is working, Enter the following commands:
----> dirm enable

DVHXMT1191I Your ENABLE request has been sent for processing.
Ready; T= .46/ .51 15:38:57
DVHREQ2288I Your ENABLE request for MAINT at has been accepted.
DVHREQ2289I Your ENABLE request for MAINT at has completed; with RC
DVHREQ2289I = .

----> dirm online immed

DVHXMT1191I Your ONLINE request has been sent for processing.
Ready; T= .46/ .51 15:39:17
DVHREQ2288I Your ONLINE request for MAINT at has been accepted.
DVHRLA3891I Your DMVCTL request has been relayed for processing.
DVHREQ2289I Your ONLINE request for MAINT at has completed; with RC
DVHREQ2289I = .
----> dirm direct

DVHXMT1191I Your DIRECT request has been sent for processing.
Ready; T= .46/ .51 15:4 :49
DVHREQ2288I Your DIRECT request for MAINT at has been accepted.
DVHREQ2289I Your DIRECT request for MAINT at has completed; with RC
DVHREQ2289I = .
----> dirm direct

DVHXMT1191I Your DIRECT request has been sent for processing.
Ready; T= .48/ .53 15:42: 4
DVHREQ2288I Your DIRECT request for MAINT at has been accepted.
DVHREQ2289I Your DIRECT request for MAINT at has completed; with RC
DVHREQ2289I = .
DirMaint Books
The following DirMaint book is required reading for user tailoring:
DirMaint Tailoring and Administration Guide, SC23-0533
Nice to have but help files will suffice:

DirMaint Command Reference, SC20-1839
DirMaint Licensed Program Specifications, GC20-1837
DirMaint General Information, GC20-1836
DirMaint Messages, SC23-0437
All of the above books can be ordered by: SBOF-3298.
DirMaint Directory Maintenance 27


CTRGEN Process
Because of the changing nature of the IBM Center environment and the many
changes in VM/ESA 2.4.0, the VM staff at DD&S is providing a new process struc-
ture to help you with the generation and upkeep of the VM/ESA 2.4.0 DEMOpkg
System.
The CTRGEN process, with five sections, is the first of these. We hope to expand
the CTRGEN process to more items in the next update.
To use the CTRGEN process, logon to MAINT and then Enter:
----> CTRGEN
The following menu appears:
DEMOpkg: -CTRGEN- Section Selection Menu
Number Section Description

1) Save CMS.
2) Save HELPINST.
3) Save CMS INSTSEG.
4) CTRXEDIT Menu. (System files)
5) CP Nucleus: Build.
6) CMS Nucleus: Xedit and re-generate.
7) GCS Nucleus: Update and re-generate.
8) List Missing USERs in GROUP USERID
9) Change your passwords.
1 ) Check the GROUP USERID for errors
Enter the number of a specific section.
F12=Cancel
Section 4: CTRXEDIT Menu
Because of the nature of the VM/ESA 2.4.0 System implementation, this is the one
section that has changed the most.
A new CP nucleus must be generated whenever you have applied maintenance to

modules whose filenames begin with “HCP.” Before regenerating CP, ensure that the
D240R2 volume has been restored and attached to the system.
CTRGEN Process 29
Section 5: CP Nucleus: Build
We have provided you with specific steps to build the CP nucleus. The VM/ESA
2.4.0 DEMOpkg Reference Guide is not required to accomplish this task.
A new CP Load Module (nucleus) must be generated when you apply maintenance
to modules whose filenames begin with “HCP.” Before regenerating CP, ensure that
the D240R2 volume has been restored and attached to the system.
Section 6: CMS Nucleus: Xedit and re-generate
We have provided you with specific steps to build the CMS nucleus. The VM/ESA
A new CMS nucleus must be generated whenever you have applied maintenance to
modules whose filenames begin with “DMS.” Do not regenerate the CMS nucleus if
you have modified the contents of MAINT 190 or MAINT 19E. Before regenerating
CMS, ensure that the D240R2 volume has been restored and attached to the
system.
Section 7: GCS Nucleus: Update and re-generate
We have provided you with specific steps to build the GCS nucleus. The VM/ESA
A new GCS nucleus must be generated whenever maintenance has been applied to
the modules whose filenames begin with “GCT,” or if you need to authorize new
userids for the GCS group.
Before regenerating GCS, ensure that the D240R2 volume has been restored and
attached to the system. When you regenerate the new GCS nucleus, you will need
to shutdown your network. Ensure that all users are aware that the network
(including all SNA terminals) will not be available for a period of time.
Step Menu: After selecting the section from the Main menu you will be shown a
Step Menu. You select each step to implement a procedure or exec. (These
menus are provided by the file called, CTRGEN TASKS). If you don't complete all
the prerequisite steps, the CTRGEN process will inform you that those steps are
required to continue. If you are using a color display terminal and after the imple-
mentation of each step, the color of the step number will change so that you will
not get lost in the process. The step number colors are a reflection of the SESSION
GLOBALV file as to what steps have been run.
Located on each Step Menu is a step indicating how to reset the step number colors
to the original selections. Use this selection when you enter the Step Menu for the
first time. We chose not to reset or clear these colors in case that you had to
leave the process for a short time and are returning to finish. Please be careful not
to disturb the file linkages, and so on.

Menu PF Keys: The only PF keys that are presently active are PF3 and PF12.
PF3 Used to return to the previous menu.
PF12 Used to exit the CTRGEN process and return you to the VM Ready
message.
Data Entry: Please read and follow the instructions that are supplied with each
menu. Informational notes are preceded in this manual and on non-graphic termi-
nals by an (i), and on graphic terminals by a graphic i enclosed in a small circle.
Manual Layout: This explanation of the steps involved and the information dis-
played may be too much information. The decision to include more information
rather than less, was made to give you a feel how the process works.
What we intend to provide is the screen image (as best we can), the key or infor-
mation that is required to continue, and the output results as displayed on the
console. Take the following as an example:
The screen image of a previous action will be displayed inside a structure like this:
SCREEN IMAGE
Following this screen image will be an index to the screen or computer output that
should appear during the execution of each step, and also information on what you
did to get to this screen. We will also show you the FASTPATH command to get to
this screen directly from the Ready message.
Recommendation: When you enter a section for the first time and notice that the
step indicators are set, reset the STEP indicators.
DEMOpkg: -CTRGEN- Section Selection Menu
Number Section Description

1) Save CMS.
2) Save HELPINST.
3) Save CMS INSTSEG.
4) CTRXEDIT Menu. (System files)
5) CP Nucleus: Build.
6) CMS Nucleus: Xedit and re-generate.
7) GCS Nucleus: Update and re-generate.
8) List Missing USERs in GROUP USERID
9) Change your passwords.
1 ) Check the GROUP USERID for errors
Enter the number of a specific section.
F12=Cancel
Figure 1. CTRGEN Main Menu
CTRGEN Process 31
Fast Path: ctrgen

Main menu: Figure 1
Section 1: Save CMS; Figure 2 on page 33
Section 2: Save HELPINST Figure 5 on page 34
Section 3: Save CMS INSTSEG Figure 6 on page 35
Section 4: CTRXEDIT Menu (System Files) Figure 7 on page 36
Section 5: CP Nucleus: Build Figure 16 on page 47
Section 6: CMS Nucleus: Xedit and re-generate Figure 24 on page 56
Section 7: GCS Nucleus: Update and re-generate Figure 34 on page 66
Section 8: List Missing USERs in GROUP USERID Figure 42 on page 73
Section 9: Change your passwords Figure 43 on page 74
Section 10: Check the GROUP Userids for errors.

Section 1
DEMOpkg: -CTRGEN- Step Menu

Save CMS;
Number Step Description
1) Save CMS shared Segment
(i) Press PF12 at VM Read;.
2) Reset STEP indicators.
Enter the number of the step. __
F12=Cancel
Figure 2. Step Menu
Main Menu: Figure 1 on page 31

Enter the number: 1
Fast Path: ctrgen saveseg
Step Menu: Figure 2
Step 1: Save CMS shared Segment Figure 4
Step 2: Reset STEP indicators
NO FILES PURGED
1 FILE PENDING PURGE
HCPNSD44 I Named Saved System CMS successfully defined in fileid nnnn.
HCPNSS44 I Named Saved System CMS successfully saved in fileid nnnn.
VM/ESA 2.4. DEMOpkg: CMS
Figure 3. Step Response
When you see VM READ at the bottom the screen, press Enter
LOADPARM from last IPL is: CMSSAVE

Ready;
Figure 4. Step Response
CTRGEN Process 33
Section 2
DMSACC724I 5E5 replaces B (5E5)

DMSACC724I 51D replaces D (51D)
VMFBLD276 I VMFBLD processing started
VMFBLD1851I Reading build lists
VMFBLD2182I Identifying new build requirements
VMFBLD2182I New build requirements identified
VMFBLD1851I (1 of 1) VMFBDSEG processing SEGBLIST EXC D, target is BUILD
51D (D)
VMFBDS2115I Validating segment INSTSEG
VMFBDS2 2I A DEFSEG command will be issued for 1 segment(s).
VMFBDS2219I Processing object INSTSEG.SEGMENT
--------------------
51D (D)
HCPNSS44 I Saved segment INSTSEG was successfully saved in fileid 2 1.
--------------------
51D (D)
HCPNSS44 I Saved segment INSTSEG was successfully saved in fileid 2 1.
VMFBDS2 3W The SYSTEM SEGID D(51D) file has been changed and must
be moved to the S disk.
VMFBLD1851I (1 of 1) VMFBDSEG completed with return code
VMFBLD218 I There are build requirements remaining
Figure 5. Save HELPINST Step Menu

Enter the number: 2
Fast Path: ctrgen savhelp
This should be used to rebuild the HELPINST shared segment after making changes
to MAINT 19D minidisk.

Section 3

Save CMS INSTSEG.
1) Save CMS INSTSEG Segment
Enter the number of the step.
F12=Cancel
Figure 6. Save CMS INSTSEG Step Menu

Enter the number: 3
Fast Path: ctrgen savinst
This is used to rebuild the CMS INSTSEG shared segment after making changes to
selected CMS execs.
CTRGEN Process 35
Section 4

CTRXEDIT Menu.
1) CTRXEDIT: SYSTEM CONFIG file (HCPSYSL replacement)
2) CTRXEDIT: SYSTEM CONFIG file (HCPRIO replacement)
3) CTRXEDIT: (fname) LOGO files (HCPBOX replacements)
(i) Enter COLOR in the Cmd area to select
4) CTRXEDIT: All files on the CF1 disk
5) Copy (SYSTEM CONFIG LOGO ) files from CF1 to CF2
6) Copy (SYSTEM CONFIG LOGO ) files from CF2 to CF1
7) Copy ALL files from CF1 to CF2
8) Copy ALL files from CF2 to CF1
9) Reset STEP indicators
F12=Cancel
Figure 7. CTRXEDIT Step Menu

Enter the number: 3
Fast Path: ctrgen ctrx
Step Menu: Figure 7
Step 1: CTRXEDIT: SYSTEM CONFIG file (SYS) Figure 8 on page 37
Step 2: CTRXEDIT: SYSTEM CONFIG file (RIO) Figure 9 on page 38
Step 3: CTRXEDIT: (fname) LOGO files (BOX) Figure 10 on page 39
Step 4: CTRXEDIT: All files on the CF1 disk Figure 11 on page 42
Step 5: Copy (SYSTEM CONFIG LOGO ) Figure 12 on page 43
Step 6: Copy (SYSTEM CONFIG LOGO ) Figure 13 on page 44
Step 7: Copy ALL files from CF1 to CF2 Figure 14 on page 45
Step 8: Copy ALL files from CF2 to CF1 Figure 15 on page 46
Please refer to “VM/ESA System Enhancements” on page 81 for more information

concerning this section.

CPRELEASE request for disk A scheduled.

HCPZAC673 I CPRELEASE request for disk A completed.
Figure 8. CTRXEDIT Step 1 Response
SYSTEM CONFIG C1 F 8 Trunc=8 Size=259 Line= Col=1 Alt=

====>
|...+....1....+....2....+....3....+....4....+....5....+....6..
Top of File
1/ /
2/ SAMPLE SYSTEM CONFIG FILE /
3/ /
4/ /
5/ Rules of the config file: /
6/ /
7/ 1) REXX style comments are permitted /
8/ /
9/ 2) Configuration commands can be continued to next line via /
1 / trailing comma on the previous line /
11/ /
12/ 3) IMBED statements can be used to imbed other files that /
13/ reside on the PARMDISK into the configuration file /
14/ /
15/ 4) The IMBED record is of the format: IMBED fn ft /
16/ /
17/ 5) Tolerance record can be used to signal whether CP should /
18/ tolerate errors in some sections of CONFIG file or not; /
19/ default is to have tolerance on (to tolerate errors) /
2 / /
21/ 6) Format of tolerance is: TOLERATE_CONFIG_ERRors ON|OFF“ /
22/ /
23/ 7) A prefix of "systemid:" on front of any statement limits /
24/ the scope of the statement to apply to specific node or /
25/ a collection of nodes defined on previous EQUATE statemt /
26/ /
1=HLP 2=HME 3=QUIT 4=VER 5=SPL 6=JOIN 7=BWD 8=FWD 9== 1 =LFT 11=RHT
12=QUIT
DASD CF1 DETACHED

CPACCESS request for mode A scheduled.
HCPZAC6732I CPACCESS request for MAINT's CF1 in mode A completed.
CTRGEN Process 37

SYSTEM CONFIG C1 F 8 Trunc=8 Size=259 Line=166 Col=1 Alt=

====>
|...+....1....+....2....+....3....+....4....+....5....+....6
166/ /
167/ The following RDEV statements are examples.They are NOT /
168/ currently active. They have been commented out. /
169/ /
17
171/ Rdevice 12 Type Reader, /
172/ Class 6 /
173/ Rdevice 13 Type Punch, /
174/ Classes 6 , /
175/ Form PUNCH /
176 Rdevice 41- 48 Type Bsc_Adapter
177 Rdevice 6D- 6F Type Bsc_Adapter
178 Rdevice 2E Type 32 3,
179 Chars TNV,
18 Universal_Charset YES,
181 AFP NO,
182 Classes H
183 Rdevice 2F Type Impact_Printer,
185 AFP NO,
186 Classes H
187 Rdevice 1E Type Impact_Printer,
189 Classes H
19 Rdevice 51 - 517 Type CTCA
191 Rdevice 5C - 5DF Type CTCA
192 Rdevice 5E - 5FF Type CTCA
12=QUIT
DASD CF1 DETACHED



\MAINT FILELIST A V 1 8 Trunc=1 8 Size=13 Line=1 Col=1 Alt=

Cmd Filename Filetype Fm Format Lrecl Records Blocks Date Time
LOCAL LOGO C1 F 78 16 1 5/17/99 3:5 :44
SNA LOGO C1 F 78 16 1 7/ 2/99 7:42:25
MINIMUM LOGO C1 F 78 16 1 7/ 2/99 7:42:14
LDEV LOGO C1 F 78 16 1 7/ 2/99 7:41:47
DEFAULT LOGO C1 F 78 16 1 7/ 2/99 7:41:34
LOCAL O2LOGO C1 F 78 16 1 6/23/99 5:4 :58
PRINTSEP LOGO C1 F 49 16 1 6/23/99 5:34:42
LOCAL OLOGO C6 F 78 15 1 6/23/99 5: 5:26
SNA OLOGO C6 F 78 15 1 6/23/99 : :32
MINIMUM OLOGO C1 F 78 16 1 6/23/99 : :23
PRINTSEP OLOGO C1 F 49 16 1 6/23/99 : :11
LDEV OLOGO C6 F 78 15 1 6/23/99 9:59:47
DEFAULT OLOGO C1 F 78 15 1 6/23/99 9:59:39
1=Help 2=Refresh 3=Quit 4=Sort(type) 5=Sort(date) 6=Sort(size)

7=Backward 8=Forward 9=FL/n 1 = 11=XEDIT 12=Cursor
====>
X E D I T 1 File
CTRGEN Process 39
On the logo that you wish to XEDIT, Enter COLOR:
MAINT FILELIST A V 1 8 Trunc=1 8 Size=13 Line=1 Col=1 Alt=

color LOCAL LOGO C1 F 78 16 1 1/21/99 13:5
SNA LOGO C1 F 78 16 1 1/ 2/99 17:42
MINIMUM LOGO C1 F 78 16 1 1/ 2/99 17:42
LDEV LOGO C1 F 78 16 1 1/ 2/99 17:41
DEFAULT LOGO C1 F 78 16 1 1/ 2/99 17:41
LOCAL O2LOGO C1 F 78 16 1 12/23/98 15:4
PRINTSEP LOGO C1 F 49 16 1 12/23/98 15:34
LOCAL OLOGO C6 F 78 15 1 12/23/98 15: 5
SNA OLOGO C6 F 78 15 1 12/23/98 1 :
MINIMUM OLOGO C1 F 78 16 1 12/23/98 1 :
PRINTSEP OLOGO C1 F 49 16 1 12/23/98 1 :
LDEV OLOGO C6 F 78 15 1 12/23/98 9:59
DEFAULT OLOGO C1 F 78 15 1 12/23/98 9:59

7=Backward 8=Forward 9=FL/n 1 = 11=XEDIT 12=Cursor
====>
X E D I T 1 File
Make your color changes on the following screen:
LOCAL LOGO C1 F 78 Trunc=78 Size=16 Line= Col=1 Alt=

====>
|...+....1....+....2....+....3....+....4....+....5....+....6..
Top of File
1 "D Welcome to the
2 "-
3 "- "-=========== "8=========== "H==== ====
4 "- "-=========== "8============ "H===== =====
5 "- "- === "8 ==== ==== "H ====== ======
6 "- "- === "8 ========== "H ======= =======
7 "- "- === "8 ========== "H === ======= ===
8 "- "- === "8 ==== ==== "H === ===== ===
9 "- "-=========== "8============ "H==== === ====
1 "- "-=========== "8=========== "H==== = ====
11 "-
12 "H Test
13 "8 Dallas Demo Delivery & Support
14 "8 VM/ESA 2.4. DEMOpkg System
15 "-
16 "HLocal For IBM Business Purposes Only
17 End of File
1=TOGL 2=HME 3=QUIT 4=DLTE 5=SPL 6=JOIN 7=BWD 8=FWD 9=RED 1 =GRN
11=BLU 12=WHI

When finished, your updated screen appears:
VM/ESA DEMOpkg On-line
Welcome to the
=========== =========== ==== ====

=========== ============ ===== =====
=== ==== ==== ====== ======
=== ========== ======= =======
=== ========== === ======= ===
=== ==== ==== === ===== ===
=========== ============ ==== === ====
=========== =========== ==== = ====
Test
Dallas Demo Delivery & Support
VM/ESA 2.4. DEMOpkg System
Local For IBM Business Purposes Only
Fill in your USERID and PASSWORD and press ENTER

(Your password will not appear when you type it)
USERID ===>
PASSWORD ===>
COMMAND ===>
DASD CF1 DETACHED

CTRGEN Process 41

The following is an example of the FILELIST that you will get:
MAINT FILELIST A V 1 8 Trunc=1 8 Size=25 Line=1 Col=1 Alt=

SYSTEM CONFIG C1 F 8 259 6 1/29/99 15:2
CPLOAD MODULE C1 V 65535 6 942 1/29/99 15: 2
LOCAL LOGO C1 F 78 16 1 12/21/98 13:5
SNA LOGO C1 F 78 16 1 12/ 2/98 17:42
MINIMUM LOGO C1 F 78 16 1 12/ 2/98 17:42
LDEV LOGO C1 F 78 16 1 12/ 2/98 17:41
DEFAULT LOGO C1 F 78 16 1 12/ 2/98 17:41
LOCAL MASTER C1 F 78 16 1 12/ 2/98 17:36
SYSTEM MASTER C1 F 8 233 5 11/3 /98 1 :58
LOCAL O2LOGO C1 F 78 16 1 11/23/98 15:4
PRINTSEP LOGO C1 F 49 16 1 11/23/98 15:34
LOCAL OLOGO C6 F 78 15 1 11/23/98 15: 5
ONMESS MASTER C1 F 78 1 1 11/23/98 14:24
ONMESS SAMPLE C1 F 78 1 1 11/23/98 14:24
LOGO CONFIG C1 V 69 63 1 11/23/98 14:19
LOGO MASTER C1 V 69 63 1 11/23/98 14:19
BKLOAD MODULE C1 V 65535 6 942 11/23/98 14:15
SNA OLOGO C6 F 78 15 1 11/23/98 1 :
MINIMUM OLOGO C1 F 78 16 1 11/23/98 1 :
PRINTSEP OLOGO C1 F 49 16 1 11/23/98 1 :
LDEV OLOGO C6 F 78 15 1 11/23/98 9:59
DEFAULT OLOGO C1 F 78 15 1 11/23/98 9:59
XXXLOAD MODULE C1 V 65535 6 942 1 /26/98 14:35
INPTAREA MASTER C1 F 78 6 1 1 /22/98 16:28
INPTAREA SAMPLE C1 F 78 6 1 1 /22/98 16:28
7=Backward 8=Forward 9=FL /n 1 = 11=XEDIT 12=Cursor
====>
X E D I T 1 File
DASD CF1 DETACHED


DASD 5555 DETACHED

DASD 5555 DEFINED
Temporary disk defined.
Now Formating Temporary disk...
Temporary disk formatted.

DASD CF1 DETACHED
CPRELEASE request for disk B scheduled.
HCPZAC673 I CPRELEASE request for disk B completed.
DASD CF2 DETACHED
CPACCESS request for mode B scheduled.
HCPZAC6732I CPACCESS request for MAINT's CF2 in mode B completed.
DASD 5555 DETACHED
CTRGEN Process 43
HCPDTV 4 E Device 5555 does not exist

DASD 5555 DEFINED

DASD CF2 DETACHED
DASD CF1 DETACHED
DASD 5555 DETACHED

DASD 5555 DETACHED

DASD 5555 DEFINED

DASD CF1 DETACHED
DASD CF2 DETACHED
DASD 5555 DETACHED
CTRGEN Process 45

DASD 5555 DEFINED

DASD CF2 DETACHED
DASD CF1 DETACHED
DASD 5555 DETACHED

Section 5

CP Nucleus: Build.
1) Setup; Ask about assembly of HCPxxx Modules.
2) Generate CP NUCLEUS.
3) Review the build message log ($VMFBLD $MSGLOG).
4) Review the install message log ($VMFINS $MSGLOG).
5) Copy the CPLOAD MAP to all required disks.
6) Find UNRESOLVED symbols in CPLOAD MAP.
7) CP NUC ok? Finish the process.
F12=Cancel
Figure 16. CTRGEN CP Nucleus

Enter the number: 5
Fast Path: ctrgen cp
Step Menu: Figure 16
Step 1: Setup; Ask about assembly Figure 17 on page 48
Step 2: Generate CP NUCLEUS Figure 18 on page 50
Step 3: Review the build message log Figure 19 on page 51
Step 4: Review the install message log Figure 20 on page 52
Step 5: Copy the CPLOAD MAP to all required disksFigure 21 on page 53
Step 6: Find UNRESOLVED symbols in CPLOAD MAP Figure 22 on page 54
Step 7: CP NUC ok? Figure 23 on page 55
After rebuilding CP, shutdown and re-IPL the system by Entering:
----> shutdown reipl
CTRGEN Process 47
DEMOpkg: -CTRGEN- Build CP NUCLEUS
Are assemblies required?(y/n) y
(i) HCPSYS, HCPRIO or HCPBOX DO NOT always require reassembly.

The only reason to assemble: After maintenance.
F12=Cancel
Figure 17. CP Nucleus Step 1 Response
If you answered yes to the question in Figure 17, the following screen appears:
DEMOpkg: -CTRGEN- Build CP NUCLEUS
What do you wish to assemble? (ALL HCPSYS HCPRIO HCPBOX)
For example, if you wish to reassemble all three

HCPxxx modules, simply enter: all
or for example, if you wish to reassemble only HCPSYS,

enter: hcpsys
Type your selection here:

hcpsys__ ________ ________
F12=Cancel

If you select HCPSYS, the following screen will appear:
Now executing VMFSETUP to setup the proper disk access order. . . .
VMFSET276 I VMFSETUP processing started

VMFUTL22 5I Minidisk|Directory Assignments:
String Mode Stat Vdev Label/Directory
VMFUTL22 5I LOCALMOD E R/W 2C4 MNT2C4
VMFUTL22 5I LOCALSAM F R/W 2C2 MNT2C2
VMFUTL22 5I APPLY G R/W 2A6 MNT2A6
VMFUTL22 5I H R/W 2A4 MNT2A4
VMFUTL22 5I I R/W 2A2 MNT2A2
VMFUTL22 5I DELTA J R/W 2D2 MNT2D2
VMFUTL22 5I BUILD7 K R/W 493 MNT493
VMFUTL22 5I BUILD6 L R/W 49 MNT49
VMFUTL22 5I BUILD5 M R/W 19D MNT19D
DVHUTL116I DVHRLY EXEC starting ' HOURLY ' log processing.
VMFUTL22 5I BUILD2 N R/W 193 MNT193
VMFUTL22 5I BASE2 O R/W 194 MNT194
VMFUTL22 5I -------- A R/W 191 MNT191
DVHUTL117I DVHRLY EXEC ended log processing - disposed of logs.
VMFUTL22 5I -------- B R/W 5E5 MNT5E5
VMFUTL22 5I -------- D R/W 51D MNT51D
VMFUTL22 5I -------- S R/O 19 MNT19
VMFUTL22 5I -------- Y/S R/O 19E MNT19E
VMFSET276 I VMFSETUP processing completed successfully
VMFASM276 I VMFHASM processing started
VMFSIP2473I No AUX files or VVT entries found for HCPSYS TXT
DMSUPD181E No update files were found
VMFASM19 7I Assembling HCPSYS
VMFASM25 7I HCPSYS TXT created on your A-disk for use in VMSES
environment
VMFASM276 I VMFHASM processing completed successfully
PRT FILE 81 SENT FRM MAINT PRT 81 RECS 5371 CPY 1 A NOHOLD NOKE
CTRGEN Process 49
VMFINS276 I VMFINS processing started

VMFREQ28 5I Product 6VMVMB2 component CP passed requisite checking
VMFUTL22 5I BASE2 O R/W 194 MNT194
VMFUTL22 5I -------- A R/W 191 MNT191
VMFUTL22 5I -------- S R/O 19 MNT19
VMFBLD1851I (1 of 1) VMFBDNUC processing CPLOAD EXEC
LOAD LIST: $$$TLL$$ EXEC A1 (MNT191)
CSECT'S WITH SIZE GREATER THAN CONDITIONAL PAGE BOUNDARY
@MAPSTRT 19 9 HCPGEN 145 HCPZSC 535C
VMFBLD1851I (1 of 1) VMFBDNUC completed with return code

VMFBLD276 I VMFBLD processing completed successfully
VMFINB2173I No verification exec found for this product
VMFINB2822I Product 6VMVMB2 CP built successfully
VMFINS276 I VMFINS processing completed successfully

===> VMFVIEW - Message Log Browse of $VMFBLD $MSGLOG A1 <===

You are viewing ¬ST: messages from the LAST run.
Number of messages shown = 1 <===> Number of messages not shown = 25
PPFNAME: ESA COMPNAME: CP BLDID: 6VMVMB2
Date: mm/dd/yy Time: hh:mm:ss
BD:VMFBLD218 I There are build requirements remaining

End of File
1=Help 2=All 3=Quit 4=Exception 5=Status 6=Build

7=Backward 8=Forward 9=OutCompRq 1 =Non-Stat 11=Requisite 12=Severe
====>
Refer to Table 15 for an explanation of the message prefixes. Correct any prob-
lems before going any further.
Table 15. Message Log Message Codes

Code Explanation
ST: A status message pertaining to the major function of the current process
WN: A warning message
CK: A message that you must investigate, because user action may be required
SV: A severe problem encountered
MS: Mismatched parts, such as AUX files and AUX entries in the front of text decks
RQ: A message pertaining to requisites
RO: A message pertaining to requisites outside the component
BD: An informational message issued during the build process
CTRGEN Process 51
===> VMFVIEW - Message Log Browse of $VMFINS $MSGLOG A1 <===

VMFINS286 I VMFINS processing started on userid MAINT.
Date: mm/dd/yy Time: hh:mm:ss
WN:VMFREQ28 5I Product 6VMVMB2 compont CP passed requisite checking

End of File

====>

Code Explanation

Ready;
CTRGEN Process 53
An Xedit screen of CPLOAD MAP appears:
Xedit msg: DMSXDC546E Target not found

This means there are no UNRESOLVED references in the CPLOAD MAP
and to complete this step type and enter QQUIT on command line.
If there are UNRESOLVED references, correct and re-do all of the

previous steps.


Ready; T= . 6/ .16 12:55:17
CTRGEN Process 55
Section 6

CMS Nucleus: Xedit and re-generate.
1) Setup for XEDIT only.
(i) Skip to Step 3 if no changes are to be made
(i) to DMSNGP ASSEMBLE.
2) XEDIT only.
3) Assemble DMSNGP ASSEMBLE.
4) Run VMFINS to create CMS NUCLEUS.
7) IPL the new CMS NUCLEUS
(i) Unless something is wrong, Step 7 and 8
(i) will automatically execute.
(i) At VM Read; Press ENTER.
8) Create the CMSNUC MAP.
9) Load new CMSNUC MAP; Check if ok?
(i) If OK: This step will continue and finish.
(i) If not OK: It will xedit CMSNUC MAP for you to
(i) review; make corrections; start over.
1 ) Reset STEP indicators.
F12=Cancel
Figure 24. CTRGEN CMS Nucleus

Enter the number: 6
Fast Path: ctrgen cms
Step 1: Setup for XEDIT only Figure 25 on page 57
Step 2: XEDIT only Figure 26 on page 58
Step 3: Assemble DMSNGP ASSEMBLE Figure 27 on page 59
Step 4: Run VMFINS to create CMS NUCLEUS Figure 28 on page 60
Step 7: IPL the new CMS NUCLEUS Figure 31 on page 63
Step 8: Create the CMSNUC MAP Figure 32 on page 64
Step 9: Load new CMSNUC MAP; Check if ok? Figure 33 on page 65


VMFUTL22 5I BASE2 O R/W 3B2 MNT3B2
VMFUTL22 5I BASE3 P R/W 393 MNT393
VMFUTL22 5I SYSTEM Q R/W 325 MNT325
VMFUTL22 5I -------- A R/W 191 MNT191
VMFUTL22 5I -------- S R/O 19 MNT19
DMSXUP178I Applying DMSNGP SL 1DS E1
DMSXUP18 W Missing PTF file DMSNGP SL 2DS A
Figure 25. CMS Nucleus Step 1 Response
CTRGEN Process 57
DEMOpkg: -CMS NUCLEUS GENERATION-
Press ENTER for the default: backup and continue.

-or-
Type RESTORE; Press ENTER for recovery of old DMSNGP.
-or-
Type BACKUP; Press ENTER for backup and continue.
Enter your reply here. ________
F12=Cancel
DMSNGP ASSEMBLE E1 F 8 Trunc=72 Size=3 Line=1 Col=1 Alt=

====>
|...+....1....+....2....+....3....+....4....+....5....+....6
1 DMSNGP CSECT D
11 DEFNUC SYSDISK=19 , S-disk address D
12 YDISK=19E, Y-disk address D
13 HELP=19D, Help disk address D
14 LANGID=AMENG, Default is American English D
15 DBCS=NO, Default is not a DBCS lang D
16 LANGLEV=S, Mult. lang. in saved seg.level ID D
17 BUFFSIZ=2 , File system R/W cache buffer size D
18 SAVESYS=NO, Save CMS as a named saved system D
19 SYSNAME=CMS, Name given to named saved system D
2 USEINST=YES, Use EXEC/XEDIT in a saved segment D
21 INSTSEG=CMSINST, Name of above saved segment D
22 USEMTSG=YES, Use VMMTLIB in a saved segment D
23 MTSEG=VMMTLIB, Name of above saved segment D
24 REWRITE=YES, Write nucleus to disk D
25 IPLADDR=19 , Address of where to write D
26 CYLADDR=12 , Cyl/Blk of where to write D
27 IPLCYL =YES, Write IPL text on cyl D
28 VERSION='&vmcms', D
29 INSTID='IBM Center VM/ESA 2.4. DEMOpkg: CMS'
3 END D
31 End of File
12=QUIT

VMFASM276 I VMFASM processing started

DMSUPD178I Updating DMSNGP ASSEMBLE A1
DMSUPD178I Applying DMSNGP SL 1DS E1
DMSUPD178I Applying DMSNGP SL 2DS E1
VMFASM19 7I Assembling DMSNGP
ASSEMBLER (XF) DONE

NO STATEMENTS FLAGGED IN THIS ASSEMBLY
VMFSIP25 9I The version vector table 6VMVMA21 VVTLCL E will be
updated for the part DMSNGP TXT using the information in AUX
file DMSNGP AUXLCL
VMFASM25 7I DMSNGP TXTL 2 created on your A-disk for use in a VMSES
environment
VMFASM276 I VMFASM processing completed successfully
PRT FLE 134 SNT FRM MAINT PRT 134 RECS 2 2 CPY 1 A NOHOLD
CTRGEN Process 59

VMFREQ28 5I Product 6VMVMA2 component CMS passed requisite checking
VMFUTL22 5I BASE2 O R/W 3B2 MNT3B2
VMFUTL22 5I -------- A R/W 191 MNT191
VMFUTL22 5I -------- S R/O 19 MNT19
VMFBLD1851I (1 of 1) VMFBDNUC processing CMSLOAD EXEC
RDR FILE 83 SNT FRM MAINT PUN 83 RECS 45K CPY 1 A NOHOLD NOKEEP
VMFINB2822I Product 6VMVMA2 CMS built successfully


PPFNAME: ESA COMPNAME: CMS BLDID: 6VMVMA2
Date: 5/14/99 Time: 16:27: 6

End of File

====>

Code Explanation
CTRGEN Process 61

Date: 5/14/99 Time: 16:26:29
WN:VMFREQ28 5I Product 6VMVMA2 component CMS pass requisite checking

End of File

====>

Code Explanation

1 FILE ORDERED
1 FILE CHANGED
LOADPARM from last IPL is: CMSNUC7
CTRGEN Process 63
1 FILE PURGED
RDR FLE 84 SNT FRM MAINT PRT 84 RECS 8682 CPY 1 A NOHOLD NOKEEP
LOADPARM from last IPL is: CMSNUC8

DMSACC724I 493 replaces E (2C4)

CMSNUC MAP E1 created
DMSRDC738I Record length is 132 bytes
File CMSNUC MAP E1 received from MAINT at DEMOTST sent(none)(none)A1
CTRGEN Process 65
Section 7

GCS Nucleus: Update and re-generate.
1) Setup for GROUP EXEC.
2) Execute GROUP EXEC; NO assembly.
3) Execute GROUP EXEC; then assemble.
4) Run VMFINS to create GCS NUCLEUS.
7) IPL the new GCS NUCLEUS
(i) This step will finish with a CP READ.
(i) Press PF12 to continue with STEP 8.
8) Create GCSNUC MAP and finish.
(i) If OK: This step will continue and finish.
(i) If not OK: It will xedit GCSNUC MAP for you to
(i) review; make corrections; start over.
F12=Cancel
Figure 34. CTRGEN GCS Nucleus

Enter the number: 7
Fast Path: ctrgen gcs
Step 1: Setup for GROUP EXEC Figure 35 on page 67
Step 2: Execute GROUP EXEC; NO assembly Figure 36 on page 68
Step 3: Execute GROUP EXEC; then assemble
Step 4: Run VMFINS to create GCS NUCLEUS Figure 37 on page 69
Step 7: IPL the new GCS NUCLEUS Figure 40 on page 72
Step 8: Create GCSNUC MAP and finish Figure 41 on page 72


VMFUTL22 5I LOCALMD2 F R/W 3C4 MNT3C4
VMFUTL22 5I LOCALSAM G R/W 6C2 MNT6C2
VMFUTL22 5I APPLY H R/W DIR VMSYS:MAINT.GCS.APPLYALT
VMFUTL22 5I I R/W DIR VMSYS:MAINT.GCS.APPLYINT
VMFUTL22 5I J R/W DIR VMSYS:MAINT.GCS.APPLYPROD
VMFUTL22 5I APPLY2 K R/W 3A6 MNT3A6
VMFUTL22 5I L R/W 3A4 MNT3A4
VMFUTL22 5I M R/W 3A2 MNT3A2
VMFUTL22 5I DELTA N R/W DIR VMSYS:MAINT.GCS.DELTAPROD
VMFUTL22 5I DELTA2 O R/W 3D2 MNT3D2
VMFUTL22 5I BUILD3 P R/W 595 MNT595
VMFUTL22 5I BUILD7 Q R/W 493 MNT493
VMFUTL22 5I BUILD5 R R/W 19D MNT19D
VMFUTL22 5I BUILD2 T R/W 193 MNT193
VMFUTL22 5I BASE2 U R/W DIR VMSYS:MAINT.GCS.OBJECT
VMFUTL22 5I BASE4 V R/W 3B2 MNT3B2
VMFUTL22 5I -------- A R/W 191 MNT191
VMFUTL22 5I -------- C R/W 2C2 MNT2C2
VMFUTL22 5I -------- S R/O 19 MNT19
Figure 35. GCS Nucleus Step 1 Response
CTRGEN Process 67
GRP1 GCS GROUP - PRIMARY OPTION MENU Primary

-----------------------------------------------------------------
Fill in the blanks with the required information and press ENTER
Type/change the name of the saved system that is being defined.
SYSTEM NAME : GCS.....
Type one number from the list below to display/update the:
1. Authorized VM Userids.
2. Saved System Information.
3. Saved Segment Links.
4. VM Userids requiring reserved storage for VSAM.
Type your choice here: _
-------------------------------------------------------------------
PF: 1 HELP 2 CLEAR 3 END 4 ... 5 ... 6 ...
PF: 7 ... 8 ... 9 ... 1 ... 11 ... 12 CURSOR
====>
Figure 36. GCS Group - Primary Option Menu Step 2 Response


VMFREQ28 5I Product 6VMVML2 compont GCSSFS passed requisite checking
VMFUTL22 5I LOCALMD2 F R/W 3C4 MNT3C4
VMFUTL22 5I LOCALSAM G R/W 6C2 MNT6C2
VMFUTL22 5I APPLY H R/W DIR VMSYS:MAINT.GCS.APPLYALT
VMFUTL22 5I I R/W DIR VMSYS:MAINT.GCS.APPLYINT
VMFUTL22 5I J R/W DIR VMSYS:MAINT.GCS.APPLYPROD
VMFUTL22 5I APPLY2 K R/W 3A6 MNT3A6
VMFUTL22 5I L R/W 3A4 MNT3A4
VMFUTL22 5I M R/W 3A2 MNT3A2
VMFUTL22 5I DELTA N R/W DIR VMSYS:MAINT.GCS.DELTAPROD
VMFUTL22 5I DELTA2 O R/W 3D2 MNT3D2
VMFUTL22 5I BUILD3 P R/W 595 MNT595
VMFUTL22 5I BUILD7 Q R/W 493 MNT493
VMFUTL22 5I BUILD5 R R/W 19D MNT19D
VMFUTL22 5I BUILD2 T R/W 193 MNT193
VMFUTL22 5I BASE2 U R/W DIR VMSYS:MAINT.GCS.OBJECT
VMFUTL22 5I BASE4 V R/W 3B2 MNT3B2
VMFUTL22 5I -------- A R/W 191 MNT191
VMFUTL22 5I -------- C R/W 2C2 MNT2C2
VMFUTL22 5I -------- S R/O 19 MNT19
VMFBLD1851I (1 of 1) VMFBDNUC processing GCTLOAD EXEC
RDR FILE 85 SNT FRM MAINT PUN 85 RECS 1 K CPY 1 A NOHOLD NOKEEP
VMFINB2822I Product 6VMVML2 GCSSFS built successfully
CTRGEN Process 69

PPFNAME: ESA COMPNAME: GCSSFS BLDID: 6VMVML2
Date: 5/14/99 Time: 16:37:1

End of File

====>

Code Explanation


Date: 5/14/99 Time: 16:36:34
WN:VMFREQ28 5I Product 6VMVML2 component GCSSFS passed requisite

WN: checking
End of File

====>

Code Explanation
CTRGEN Process 71
1 FILE ORDERED
1 FILE CHANGED
When you see CP Read, Press PF12 to continue.
NO FILES PURGED
1 FILE PENDING PURGE
HCPNSD44 I Named Saved System GCS successfully defined in fileid 591
FILE FILENM FILETYP MINSIZE BEGPG ENDPG TYP CL #USERS PARMREGS VMGRP
548 GCS NSS 256K 9 EW P 9 OMITTED YES
4 461 ER
462 462 SW
463 5FF SN
1 12FF SN
591 GCS NSS 256K 9 EW S OMITTED YES
4 461 SR
462 462 SW
463 5FF SN
1 12FF SN
HCPNSS44 I Named Saved System GCS successfully saved in fileid 591.
RDR FLE 86 SNT FRM MAINT PRT 86 RECS 3313 CPY 1 A NOHOLD NOKEEP
Storage cleared - system reset.
CP Read DEMOTST
Press PF12
I 19 CLEAR LOADPARM GCSNUC7 PARM AUTOCR

LOADPARM from last IPL is: GCSNUC7

Section 8

List Missing USERs in GROUP USERID
1) XEDIT the GROUP PASSWORD file.
2) Create file of USERIDs not in GROUP USERID.
(i) This step will refresh the USER WITHPASS.
3) Create file of USERIDs not in GROUP USERID.
(i) This step will NOT refresh the USER WITHPASS.
(i) That should have been done in step two.
4) XEDIT file of USERIDs missing from GROUP USERID.
5) Release and detach the password MDISK.
F12=Cancel
Figure 42. List Missing USERS in GROUP USERID Step Menu

Enter the number: 8
Fast Path: ctrgen pswd0
These steps will refresh the USER WITHPASS file, and will allow you to update and
check the GROUP USERID file. For more information on this process, refer to
“Changing Logon Passwords (Non-RACF)” on page 95.
CTRGEN Process 73
Section 9

Change your passwords.
2) Change the passwords.
(i) This step will update the USER DIRECT file.
(i) Send USER INPUT to DIRMAINT.
(i) Then DISCONNECT.
(i) You must logon to DIRMAINT.
(i) Enter DIRMAINTs current password.
(i) Enter SETUP
(i) Return to MAINT to finish the process.
F12=Cancel
Figure 43. Change You Password Step Menu

Enter the number: 9
Fast Path: ctrgen pswd
These steps will refresh the USER PASSWORD file, and will allow you to change all of
the passwords in the system. For more information on this process, refer to

Section 10

Change your passwords.
2) Change the passwords.
(i) This step will update the USER DIRECT file.
(i) Send USER INPUT to DIRMAINT.
(i) Then DISCONNECT.
(i) You must logon to DIRMAINT.
(i) Enter DIRMAINTs current password.
(i) Enter SETUP
(i) Return to MAINT to finish the process.
F12=Cancel
Figure 44. Check the GROUP Userid for Errors Step Menu

Enter the number: 10
Fast Path: ctrgen
These steps will refresh the USER PASSWORD file, and will allow you to change all of
the passwords in the system. For more information on this process, refer to
CTRGEN Process 75

SYSTEM NETID File Customization

The SYSTEM NETID file on MAINT's 190 minidisk is used when you issue CMS com-
mands to communicate via the network. Some of the CMS commands that use this
file include: SENDFILE, RECEIVE, NOTE, and TELL. This file is also used when you
customize OfficeVision as described in the next section.
The SYSTEM NETID file must accurately specify your node name and CPU serial
number. A sample is shown in Figure 45:
CPUID NODEID NETID

1 DEMOXX RSCS
Figure 45. Contents of SYSTEM NETID on MAINT 190
As Figure 45 indicates, each record in the SYSTEM NETID file has the following
format:
psssss nodeid rscsid
where psssss is your processor number and your CPU serial number, nodeid is
your VM/ESA node name, and rscsid is the user ID of the RSCS virtual machine.
Changing the Node ID and CPU Serial Number

Note: The node ID shipped with the VM/ESA DEMOpkg System is DEMOXX.
To change the node ID, complete the following steps:

1. To determine your CPU serial number, Enter at the operator's console:
----> q cpuid
You will receive the following response:
CPUID = FFpsssssdddd
Ready;
where psssss is your CPU processor/ serial number and dddd is your CPU
device type.
Note: If your CPU has multiple processors, such as a Model 200, an entry
must be included for each processor. When operating in LPAR mode, the first
position of the serial number must equal your partition ID.
2. Logon to MAINT
SYSTEM NETID File Customization 77

3. To access MAINT's 190 minidisk in write mode, Enter:
----> i 190 parm autocr

Ready;
----> acc 190 b

19 ALSO = S-DISK
Ready;
----> x system netid b

4. Before making any changes to the file, Enter on the command line:
----> set case u

5. Edit the SYSTEM NETID file to correctly reflect your CPU serial number and node
ID
Specify RSCS as the rscsid.

6. To file your changes, Enter:
----> file
Changing the DIRECTORY Statement in the USER DIRECT File

The DIRECTORY statement in the USER DIRECT file must be changed to reflect the
new node ID. More than one DIRECTORY statement can exist in the USER DIRECT
file if the serial number-model is different.
To change the statement, complete the following steps:

1. To query the existing DIRECTORY statements, Enter:
----> dirm directory ?

The following message appears:
DVHXMT1191I Your DIRECTORY request has been sent for processing.
Ready; T= .54/ .59 16: 6:49
DVHREQ2288I Your DIRECTORY request for MAINT at has been accepted.
DVHDRY3386I The following are your DIRECTORY control statements. Note
DVHDRY3386I that the first field is the ordinal associated with each
DVHDRY3386I statement.
DVHDRY3386I 1 : DIRECTORY 123 339 D24 R1 18-9672 DEMOXX
DVHREQ2289I Your DIRECTORY request for MAINT at has completed; with R
DVHREQ2289I = .
2. To get to the DirMaint DIRECTORY screen, Enter:
----> dirm directory

The following screen appears:
--------------------DirMaint DIRECTORY----------------------
Query or update the DIRECTORY directory control statement.
Select or fill in one of the following:

_ ? (Query)
_ ADD
CHANGE Directory Statement Number ===>
DELETE Directory Statement Number ===>
For ADD or CHANGE, fill in the following:

Virtual Device Number ===>
Device Type ===>
Volume Serial Number ===>
Also, either fill in the following:
Alternate Virtual Device Number ===>
Processor ID ===> (nnnnnn-xxxx; option
System (affected by SYSAFFIN) ===> (optional)
or select:
_ EDIT
5748-XE4 (c) Copyright IBM Corporation 1979, 1995.

1= Help 2= Prefix Operands 3= Quit 5=Submit 12=Curor
===>
Macro-read
Updating the Node ID in OfficeVision

The node IDs are on pack D240O1. To update the IDs in OfficeVision, complete
the following steps:
1. Logon to SYSADMIN
2. To access the shared file system, make sure OFFSERV is running
3. Shutdown the following OfficeVision service machines:
TSTDBM
TSTCAL
TSTMBX
TSTMAIL
4. To detach the 399 minidisk, Enter:
----> DET 399

5. To run the CHANGE exec, Enter:
----> CHANGEID CHGNODE DEMOXX A DEMOXX new_node

6. Review messages to make sure all disks were accessed and changed
SYSTEM NETID File Customization 79

Changing the HOSTS LOCAL File for TCP/IP

If you changed the node ID or the local TCP/IP address, complete the following
steps:
1. Logon to TCPMAINT:
----> l tcpmaint
2. Enter the password
3. To Xedit the HOSTS LOCAL file on the E-disk, Enter:
----> x hosts local e

4. Locate the line that has the current node ID, DEMOVM
5. Change the DEMOVM name to your selected node ID
Note: Make sure that your selected name is not already in the file. If there is
a duplicate, you will get strange results.
6. Correct the octet host address if it has changed
7. To save your changes, Enter:
----> file
8. To compile and copy everything to the correct location for correct TCP/IP
addressing, Enter:
----> chgnode
9. Logoff
10. Re-cycle TCP/IP
Updating the Web Server IP Address

All pointers for Web access use the IP address to eliminate conflict with name defi-
nitions. After you logon to the EWEBADM id, this Administration Service Machine
will dynamically update the HTML code with your newly defined IP address. Other
applications, such as EVIEW and Network Manager, are also updated as well.
Migrating From An Existing CPU To A New CPU

When you installed the system, you customized the SYSTEM NETID file on MAINT
190 to specify the correct CPU serial number. If you migrate the system from the
CPU on which you installed the system to another CPU, the SYSTEM NETID file must
be changed to specify the new CPU serial number.

VM/ESA 2.4.0 DEMOpkg System Customization

To accommodate your unique environment, changes may be necessary to the fol-
lowing key components:
SYSTEM CONFIG The various attributes of your system environment, including
the real I/O of a limited number of devices.
(fname) LOGO A number of files that define the logo.
Examine the files which have been provided with the DEMOpkg System and make
the necessary changes to reflect your own unique requirements.
VM/ESA System Enhancements

This section describes some of our internal tools.
CP Nucleus
The CP nucleus is now kept on MAINT CF1 or CF2. The CPDISK CF1 can be
selected as the primary load CPDISK.
The new module is called, CPLOAD MODULE. When a new CP nucleus is gener-
ated, the resulting module is placed on CF1. When this module has successfully
been tested, it should then be copied to CF2 for backup.
CP can now access minidisks without CMS being IPLed. You may customize what
is on those disks from CMS as shown in the following sections.
HCPSYS ASSEMBLE
HCPSYS ASSEMBLE is just a shell and should never be updated.
This function was replaced by the SYSTEM CONFIG file. The SYSTEM CONFIG file can
be found on the new CP owned minidisks: CF1 and CF2.
HCPBOX ASSEMBLE
HCPBOX ASSEMBLE is just a shell and should never be updated.
This function was replaced by a series of new files:
Table 21 (Page 1 of 2). Replacement Files for HCPBOX ASSEMBLE

File Name File Type File Func- File Description
tion
LOGO CONFIG Control CP uses to identify the other files.
LOCAL LOGO Logo Displayed on local terminals.
LDEV LOGO Logo Displayed on logical device terminals.
SNA LOGO Logo Displayed on SNA terminals.
MINIMUM LOGO Logo The very least displayed.
DEFAULT LOGO Logo When nothing else works.
PRINTSEP LOGO Logo Printed on separator pages.
VM/ESA 2.4.0 DEMOpkg System Customization 81

Table 21 (Page 2 of 2). Replacement Files for HCPBOX ASSEMBLE

File Name File Type File Func- File Description
tion
ONMESS SAMPLE Msg One line at top of logo.
INPTAREA SAMPLE Msg Input area at bottom of logo.
HCPRIO ASSEMBLE
HCPRIO ASSEMBLE is just a shell and should never be updated.
This function was replaced by the SYSTEM CONFIG file.
Customizing the HCPRIO File

To make changes to the HCPRIO file, complete the following steps:
1. Logon to MAINT
2. Enter the following command:
----> ctrxedit rio

Note: RIO not HCPRIO
This command makes the proper disk linkages and accesses, and displays the
SYSTEM CONFIG file for any changes needed using XEDIT.
3. To activate any changes, shutdown and IPL your system
Note: When you first get this system, we recommend you review this file and
make very few changes.
Customizing the SYSTEM CONFIG File

To make changes to the SYSTEM CONFIG file, complete the following steps:
1. Logon to MAINT
----> ctrxedit sys

Note: SYS not HCPSYS
SYSTEM CONFIG file for any changes needed using XEDIT.
3. To activate any changes, shutdown and IPL your system
Note: When you first get this system, we recommend you review this file and
make very few changes.

Customizing the System Logos

To make a change to the LOGO file, complete the following steps:
1. Logon to MAINT
----> ctrxedit box

Note: BOX not HCPBOX
files on MAINT CF1 using the FILELIST.
3. Cursor to the LOGO file you wish to modify and then Enter:
----> COLOR
XEDIT displays the file that you have chosen. Several PF keys have been
changed at this time to help you colorize your LOGO. The changed settings are
shown in the following table:
Table 22. PF Key Settings to Colorize System Logos

PF1 CTRTOG XEDIT (Toggles though all the colors, in order.)
PF4 CTRDELCR XEDIT (Delete the attribute and color byte. )
PF9 CTRRED XEDIT (Sets the color to RED. )
PF10 CTRWHITE XEDIT (Sets the color to WHITE. )
PF11 CTRBLUE XEDIT (Sets the color to BLUE. )
PF12 CTRGREEN XEDIT (Sets the color to GREEN. )
4. Place the cursor where you wish and the program will destroy the data at that
location and replace it with 2 bytes
The first byte is the attribute byte “1D” and the second is the color byte that you
have selected.
The only colors available are: RED, GREEN, BLUE, and WHITE. If an
attribute/color combination exists at that location, the color that you have
selected is overlayed on them. The MSGLINE and CURLINE colors are changed
to reflect the last color you selected. A message explaining what happened
and where the cursor was located is displayed on the MSGLINE. CTRDELCR is
the only exception to this rule. It removes the attribute and color bytes and
replaces them with a “BLANK.” The MSGLINE and CURLINE colors are changed
to PINK.
5. If you are satisfied with your changes, Enter:
----> FILE
VM/ESA 2.4.0 DEMOpkg System Customization 83

The COLOR exec continues with the BOXVIEW exec. BOXVIEW displays the logo in
color, which is the one you just finished updating. It shows the complete
screen with the ONLINE MESSAGE file at the top and the INPUT AREA file at the
bottom. These files are listed in the VM/ESA LOGO CONFIG system file.
6. When you are finished with the color display, press Enter to continue
BOXVIEW exits to the FILELIST display.
Accessing MAINT CF1 in Read/Write Mode

To make a change to any file on MAINTS CF1 disk, get the proper access by
Entering:
----> ctrxedit cf1
CTRXEDIT displays all of the files on MAINT CF1 in read/write mode.
Accessing MAINT CF2 in Read/Write Mode

To make a change to any file on MAINTS CF2 disk, get the proper access by
Entering:
----> ctrxedit cf2
CTRXEDIT displays all of the files on MAINT CF2 in read/write mode.

System Operations
System Operations
IPLing the VM/ESA 2.4.0 DEMOpkg System (Normally) . . . . . . . . . . . . 87
Retaining Existing Spool Files with a Cold/Warm Start . . . . . . . . . . . . . . 87
Changing the TOD Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Continuing with the IPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
IPLing the VM/ESA 2.4.0 DEMOpkg (Optionally) . . . . . . . . . . . . . . . . 91

VM/ESA Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
RACF Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Changing Logon Passwords (Non-RACF) . . . . . . . . . . . . . . . . . . . . 95

Requirements for Changing Logon Passwords . . . . . . . . . . . . . . . . . . . 95
Using the GROUP_PW Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
VM/ESA 2.4.0 DEMOpkg System Backup . . . . . . . . . . . . . . . . . . . . 99

Using the DASD Dump/Restore (DDR) Program . . . . . . . . . . . . . . . . . . 99
Named Saved System (NSS) and IMG File Backup/Restore . . . . . . . . 103

Backing Up the NSS and IMG Data Files . . . . . . . . . . . . . . . . . . . . . 103
Restoring the NSS and IMG Data Files . . . . . . . . . . . . . . . . . . . . . . 104
Generating a New NCP for the 3745 . . . . . . . . . . . . . . . . . . . . . . 105

Loading the New NCP to the 3745 . . . . . . . . . . . . . . . . . . . . . . . . . 105
Loading an OS/390 Job to the 3745 . . . . . . . . . . . . . . . . . . . . . . . . 105
Web Server Demo Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Enterprise/View Text Browser Demo Access . . . . . . . . . . . . . . . . . . . 107
System Operations 85
System Operations

System Operations
IPLing the VM/ESA 2.4.0 DEMOpkg System (Normally)

IPL the new system using the address of the 3390 actuator to which D240R1 was
restored.
You should receive the following message:

VM ENTERPRISE SYSTEMS ARCHITECTURE RELEASE 4 SERVICE LEVEL ;
SYSTEM NUCLEUS CREATED ON
mm/dd/yy at .hh:mmiss, LOADED FROM D24 R1
HCPZCO6218I Using parm disk 1 on volume D24 R1 (device cruu)
HCPZCO5618I Parm disk resides on cylinders 252 through 271.
HCPZCO5618I Parm disk resides on cylinders 252 through 271.
hh:mm:ss Start ((Warm|Force|COLD) (DRain))
((DIsable) (NODIRecr) (NOAUTOlog))
or (SHUTDOWN)
HH:MM:SS START (WARM|FORCE|COLD)
(DRAIN)(DISABLE) (NODIRECT))|(SHUTDOWN)
Retaining Existing Spool Files with a Cold/Warm Start

If you do not wish to retain existing spool files, Enter:
----> cold
If you do wish to retain existing spool files, press Enter .
Changing the TOD Clock

At this point, you will be given the opportunity to either:
Set the time of day and the date, if the TOD clock was not set since the
machine was powered up; or
Reset the time of day and the date, if either one or both is incorrect
Setting the Time and Date for the TOD Clock

If the TOD clock was not set since the machine was powered up, you will get the
following messages (respond as indicated):
SET DATE MM/DD/YY:
----> mm/dd/yy
where mm/dd/yy specifies the current date (month/day/year).
SET TIME HH:MM:SS:
----> hh:mm:ss
where hh:mm:ss specifies the current time (hour:minute:second).
TO ENABLE TOD, ENTER “S1” ON (OPRCTL) PANEL OF
SERVICE PROCESSOR
IPLing the VM/ESA 2.4.0 DEMOpkg System (Normally) 87

System Operations
Note: This is function Y on the hardware mode selection frame.

CHANGE TOD CLOCK (YES|NO):
----> no
Resetting the Time and Date for the TOD Clock

If the TOD clock has been set since the machine was powered up, you will get a
message asking if you would like to change the clock.
If the date and time is correct, you do not need to reset the clock:
----> no
Skip to “Continuing with the IPL.”
If the date and time is incorrect, reset the clock:
----> yes
----> (set clock)

Go back to “Setting the Time and Date for the TOD Clock” on page 87.
Continuing with the IPL

After changing the TOD clock, the system will continue with the IPL. The following
screen will appear:
The directory on volume D22 R1 at address ccuu has been

brought on-line.
HCPWRS25 7E Spool file on off-line volume D24 B1 will be deleted
HCPWRS25 7E Spool file on off-line volume D24 R1 will be deleted
HCPWRS2513I
HCPWRS2513I Spool files available nn
HCPWRS2513I
HCPWRS2513I Spool files on off-line volumes xxx
HCPWRS2513I Spool files with I/O errors NONE
HCPWRS2513I Spool files with control errors NONE
HCPWRS2513I Spool files to be discarded yyy
HCPWRS2513I
HCPWRS2513I Total files to be deleted zzz
HCPWRS2511A
HCPWRS2511A Spool files will be deleted because of COLD start.
HCPWRS2511A No files have been deleted yet.
HCPWRS2511A To continue COLD start and delete files, enter GO.
HCPWRS2511A To stop COLD start without deleting files, enter STOP.
To continue the COLD start and to delete files, Enter:
----> go
The preceding messages may or may not be displayed. However, the following
message should always be displayed:
HCPWRS2512I Spooling initialization is complete.

System Operations
The system console is automatically logged on as OPERATOR. The system will

complete the IPL.
Several user IDs will be AUTOLOGGED to perform various system functions. Local
terminals will be enabled, the printer buffers will be loaded, and the printer will be
started. The system will be available for use as soon as you receive the message
that AUTOLOG2 has logged off.
IPLing the VM/ESA 2.4.0 DEMOpkg System (Normally) 89

System Operations

System Operations
IPLing the VM/ESA 2.4.0 DEMOpkg (Optionally)
VM/ESA Loader
The stand-alone loader is invoked by adding a new parm to the IPL procedure. The
LOADPARM command can be added when needed at the service processor, or to
your IPL command when running the 2nd level.
The LOADPARM command appears as follows:
----> IPL ccuu1 LOADPARM ccuu2

where ccuu1 is the VM/ESA system residence pack and ccuu2 is the real address of
a console (for example, IPL E06 LOADPARM 463).
The following screen will appear:
STAND-ALONE PROGRAM LOADER: VM/ESA RELEASE 2.4
DEVICE NUMBER: CCUU1 MINIDISK OFFSET: EXTENT: 1
MODULE NAME: CPLOAD LOAD ORIGIN: 1
----------------------IPL PARAMETERS---------------------------
--------------------------COMMENTS-----------------------------
---------------------------------------------------------------
9= FILELIST 1 = LOAD 11= TOGGLE - EXTENT/OFFSET
This stand-alone program loader enables you to select the DASD address the
system will be IPLed from, the CPEXTENT minidisk from which to load the CPLOAD
module, and the name of the NUCLEUS module you wish to select.
The fields in the STAND-ALONE PROGRAM LOADER screen are defined as follows:
DEVICE NUMBER: CCUU1 Points to a physical DASD device (for example, 0E06).
EXTENT: 1 Declares to the loader program to look at MAINT CF1 to
find the module to load.
To select MAINT CF2, Enter:
----> 2
MODULE NAME: CPLOAD The nucleus name you have given the most current
NUCLEUS module.
Note: In our execs, we force this name to CPLOAD and the backup nucleus to
BKLOAD.
IPLing the VM/ESA 2.4.0 DEMOpkg (Optionally) 91

System Operations
Notice at the bottom of the screen the following PF keys:

PF9 shows you all of the files that you can select the IPL nucleus from, and the
minidisk you selected in the EXTENT field.
PF11 returns you to the initial screen updated with the selected module. When
the files are displayed, move the cursor to the IPL Deck that you wish,
press PF11 to select a module, and then exit (press PF3 ).
PF10 loads the NUCLEUS and continues with the more familier IPL steps of your
system. (See “IPLing the VM/ESA 2.4.0 DEMOpkg System (Normally)” on
page 87.)

System Operations
RACF Passwords
We enabled a standard feature of RACF/VM 1.10.0 called LOGONBY. You will be
able to log onto most or all system machines with the following command:
----> L (logon userid) BY (password userid)
For example, you can log onto the DIRMAINT machine by Entering:
1. Log onto DIRMAINT:
----> L DIRMAINT BY MAINT

2. Enter the password for MAINT:
----> ******
RACF Passwords 93
System Operations

System Operations
Changing Logon Passwords (Non-RACF)

To comply with IBM Corporate security guidelines (explained in IS&A Bulletin 104A),
all logon and certain minidisk read/write passwords must be changed on a regular
basis:
Logon passwords must be changed every 2 months or more frequently as indi-
cated by a sound business judgement.
The passwords for AUTOLOG1, DIRMAINT, MAINT, PVM, RSCS, VMUTIL, and any
other user ID frequently used by the system programmer should be changed
monthly.
Disk read/write passwords for the following minidisks should also be changed
every 6 months:
AUTOLOG1 191 in group password file on MAINT 191
DIRMAINT 191 contains DIRMAINT executable code and procedures
MAINT 191 may contain portions of the VM/ESA directory
ADMIN 191 may contain portions of the VM/ESA directory
Requirements for Changing Logon Passwords

The following rules should be followed when changing the logon and minidisk
read/write passwords:
The password should not be the same as the user ID (for example, DM01 for
DM01).
The password should not be a part of the user ID (for example, BATCH for
CMSBATCH).
The password should not identify the user (for example, IBMCE for OLTSEP or
EREP).
The password should be randomly selected.

The password should not be trivial, obvious, or predictable.
The password should be at least 6 numeric, 5 alphabetic or 4 alphanumeric
characters. Logon passwords cannot be longer than 8 characters.
Each password should be treated as IBM Confidential.
Using the GROUP_PW Exec

The GROUP_PW exec uses the GROUP PASSWORD and GROUP USERIDS files either to
set a password for each user ID in a group or to AUTOLOG user IDs. All of the user
IDs in each group are assigned the group password. In both of these files, records
that are blank or records that have the first characters either to be a “*” or “/*,” are
ignored.
The GROUP PASSWORD file must contain one record for each group to be defined.
Each record contains a group name followed by the password for that group.
The GROUP USERIDS file must contain one record for each user ID either to update
the password or to AUTOLOG the user ID. Each record contains a group name
followed by a user ID that is a member of that group. IDs that are to be
Changing Logon Passwords (Non-RACF) 95

System Operations
AUTOLOGged will also be followed by the word AUTOLOG, a delay time and type
(optional), and any AUTOLOG parms. See the header information in the file for
details.
Before using the GROUP_PW exec for the first time, read the following sections of
this chapter. These sections tell you how to group user IDs and assign passwords
to each group.
Verifying if Passwords Need to be Updated

To verify that the passwords need to be updated:
A single argument of REAL must be supplied.
If an argument of AUTO is supplied, then those IDs that are flagged with
AUTOLOG, will be AUTOLOGged. An argument of AUTOLOG may also be used.
If an argument of TEST is supplied, then the exec will run but will only display
the passwords that would have been used to update if REAL had been speci-
fied, and the exec had been run from an authorized ID. The IDs that would be
AUTOLOGged will also be displayed, along with any wait times and parms.
If an argument of LOOK is supplied followed by a single user ID, then the exec
will return the group and password for that user ID.
If an argument of LIST is supplied followed by a single group name, then the
exec will list all the user IDs in that group.
If LIST is specified with no group name, then all group names will be listed.
Defining the User ID Group Names

The VM/ESA 2.4.0 DEMOpkg System is shipped with each user ID assigned to 1 of
9 groups:
SYSPROG for system programmer user IDs, for example: MAINT.
CODEMNT for code maintenance user IDs, for example: TCPMAINT.
DEMOID for demonstration user IDs, for example: VMUSER01.
OPER for system operator user IDs, for example: OPERATOR and OP1.
ADMIN for system administrator user IDs, for example: ADMIN.
CE for CE user IDs, for example: EREP and OLTSEP.
BACKUP for backup user IDs.
SERVER for server virtual machines, for example: GCS and VTAM.
GUEST for guest virtual machines, for example: MVS.
Examine the GROUP USERIDS file on MAINT 191 to determine how the user IDs have
been grouped.
GROUP PASSWORD File

The GROUP PASSWORD file defines the passwords for each group of user IDs. Each
record must contain two items: a group name followed by the password for that
group. Group names may be any string of alphanumeric characters, with no
imbedded blanks. Group names must be unique. Names that are relevant to a
particular group, like SYSPROG or ADMIN, may be used.

System Operations
Group Name Group Password

SYSPROG ESASP
CODEMNT ESAMT
DEMOID ESADM
OPER ESAOP
ADMIN ESAAD
CE ESACE
BACKUP SYSAUTO (SHOULD NEVER CHANGE)
SERVER ESASV
GUEST ESAGT
GROUP USERIDS File

The GROUP USERIDS file defines group membership for the purpose of either
updating passwords or AUTOLOGging IDs. Each record must contain at least two
items: a group name followed by a user ID. For those IDs that are to be
AUTOLOGged, the third item on the record must be the word AUTOLOG. The word
AUTOLOG may be followed by a number and a type that specifies the amount of
time to wait after AUTOLOGging the ID before continuing (for ID that need time to
initialize before proceeding).
WAITTYPE may be SEC, MIN, or HRS. The default SEC is assumed, if not required,
because of following parms. The WAITTYPE may be followed by any additional
parms to be passed on the AUTOLOG command. If additional parms are specified,
then the wait time must be specified, even if a “0” and a WAITTYPE must be given.
The order of items in the GROUP USERIDS file is significant for AUTOLOG purposes.
The IDs flagged for AUTOLOG, will be AUTOLOGged in the order listed in this file.
For example:
Group Name Group User ID Command WAITTYPE

SERVER DIRMAINT AUTOLOG
SERVER PVM AUTOLOG 5 SEC
SERVER GCS AUTOLOG 5 SEC
SERVER VTAM AUTOLOG 1 MIN
SERVER RSCS AUTOLOG
ADMIN ADMIN
CODEMNT CSP330
Invoking the GROUP_PW Exec

To invoke the GROUP_PW exec, complete the following steps:
1. Logon to MAINT, Enter:
----> logon maint

ENTER PASSWORD
----> ctrsp
Changing Logon Passwords (Non-RACF) 97

System Operations
VM/ESA 2.4. DEMOpkg System - CMS
2. Press Enter
Ready;
Important!
The machine DIRMAINT should be running before executing the following
two procedures.
3. After you have modified your GROUP USERID file, change the passwords by
typing:
----> CTRGEN
4. To check for missing groups and others before actually changing the pass-
words, select option 6 (List missing USERs in GROUP USERID)
5. To change your passwords for your system, select option 7 (Change your
passwords)
These steps in previous systems took more than 1 hour to complete. It may
take 5 - 10 minutes. We have improved the run time by replacing the whole
USER DIRECT file using INITLZ rather than sending DIRMAINT change password
commands.
Tips on Using the GROUP_PW Exec

The concept of assigning passwords to groups of user IDs allows a lot of flexibility
in your IBM Center. For instance, if a set of user IDs is maintained for a specific
user or branch office, a unique group identifier can be assigned to that person or
office. This unique identifier can then be associated with the unique set of user IDs
maintained by that person or office. The person responsible for this set of user IDs
can assign whatever password they want to assign to the collection of user IDs.
This can be done in a branch office or user specific copy of GROUP USERIDS file.
When it is time to change VM/ESA 2.4.0 DEMOpkg System passwords, the system
programmer can solicit from each group the unique copies of GROUP USERIDS file
and incorporate them in the main copy of GROUP USERIDS file. Make sure that any
group names used are included in the GROUP PASSWORD file.
It would be advisable to comment the main copy of the GROUP USERIDS file with
information relevant to the source of each set of user IDs. For example, if branch
office DFD and branch office ABC supplied unique copies of the GROUP USERIDS file,
the system programmer might add BO DFD before one set of user IDs and BO
ABC before the other set of user IDs. Using this technique, the burden for assigning
all passwords is off the shoulders of the system programmer. The job of the
system programmer is merely running the GROUP_PW exec at an appropriate time
each month.

System Operations
VM/ESA 2.4.0 DEMOpkg System Backup

After you have regenerated CP or CMS, saved CMS, or have made any other signif-
icant change to your system, you should back it up so that you can recover in case
of a catastrophe. You should also carry out a procedure that calls for backing up
your VM/ESA DEMOpkg System on a weekly basis. If you are using 3480 tapes to
backup to, consider using the CC backup system outlined in the section “Center
Tools” on page 115.
Warning!!
Be aware that backing up your system while other users are actively logged on
may invalidate this as a completely reliable backup procedure. Only a stand-
alone backup with VM shutdown offers a complete, reliable backup capability.
Using the DASD Dump/Restore (DDR) Program

This section describes the procedure for backing up the new VM/ESA DEMOpkg
System. The procedure causes a stand-alone device support facility program to be
written as the first file on the stand-alone utilities tape. The device support utility
program can be IPLed and used without the need of an operating system. Thus,
DASD volumes can be initialized without access to VM.
The procedure also causes a stand-alone DASD Dump/Restore (DDR) program to

be written as the second file on the stand-alone utilities tape. The DDR program
can be IPLed and used without the need of an operating system. Thus, the entire
VM/ESA DEMOpkg System can be restored without access to VM. In case of a
serious system error, which renders VM inoperable, this can be quite beneficial.
The DDR program backs up the following DASD volumes that contain the minidisks:
D240R1 D240L1
D240R2 D240P1
D240B1 D240P2
D240B2 D240O1
D240I1 D240S1
All volumes with SPOOL space should be backed up at the same time; otherwise,
spool files may be lost. DASD volumes that contain minidisks belonging to the
same SFS filepools should also be backed up together or the SFS filepool will
become unusable.
To use the DASD Dump/Restore program, complete the following steps:

1. Logon to MAINT
2. Enter the commands and responses shown in the following sample session:
----> att cuu * 181

where cuu is the address of a tape drive.
3. Mount the reel of tape that contains the stand-alone dump/restore and
format/allocate programs
VM/ESA 2.4.0 DEMOpkg System Backup 99

System Operations
4. Dump these programs to the tape by Entering:
----> filedef input disk ipl ickdsf s

Ready;
----> filedef output tap1 nl (18track

Ready;
----> move input output

Ready;
----> filedef input disk ipl ddrxa s

Ready;
----> move input output

Ready;
----> tape rew 181

Ready;
The stand-alone format/allocate and dump/restore programs have been written

to the tape.
5. To ensure that the programs are usable, IPL both programs and use the stand-
alone Dump/Restore program to actually perform the system backup by
Entering:
----> ipl 181

ICK 5E DEFINE INPUT DEVICE, REPLY 'DDDD,CUU' OR 'CONSOLE'
ENTER INPUT/COMMAND:
----> #cp i 181

HCPVMI232E IPL UNIT ERROR; IRB 4 17 2 C18 D 18 8
HCPGIR45 W CP entered; disabled wait PSW E 232
----> #cp i 181

VM ENTERPRISE SYSTEMS ARCHITECTURE DASD DUMP/RESTORE PROGRAM
ENTER CARD READER ADDRESS OR CONTROL STATEMENTS
ENTER:
6. Mount the tape that contains the data from D240R1 by Entering:
----> sysprint cons

ENTER:
----> input 123 3380 d240r1

ENTER:
----> output 181 xxxx (compact

where xxxx is either 3420, 3430 or 3480 (add mode 6250 after the (compact
option, if using a 3420 or 3430).
ENTER:

System Operations
----> dump all

DUMPING D24 R1 ...
END OF DUMP ...
ENTER:
Note: It is possible that any of these actuators may require a second reel of
tape. If so, you will receive a message similar to:
END OF VOLUME BLOCK nnnnnn, MOUNT NEXT TAPE

NNNNNN NNNNNN
DEVICE 38 NOT READY, CP-OPERATOR NOTIFIED
When you mount the next reel, the DDR program will continue automatically.
7. Mount the tape that contains the data from D240R2 by Entering:
----> #cp link d240r2 1a0 1a0 rr

ENTER READ PASSWORD:
----> ccms
DASD 1A LINKED R/
----> input 1a0 3380 d240r2

ENTER:
----> dump all

DUMPING D24 R2 ...
END OF DUMP ...
ENTER:
----> #cp det 1a0

DASD 1A DETACHED
8. Repeat step 7 for D240B1, D240B2, D240I1, D240L1, D240P1, D240P2, D240O1,
and D240S1.
9. To IPL CMS, press PA1 and then Enter:
----> i cms

Command complete
Ready;
or logoff of MAINT by Entering:
----> #cp logoff
VM/ESA 2.4.0 DEMOpkg System Backup 101

System Operations

System Operations
Named Saved System (NSS) and IMG File Backup/Restore

Before you back up the system, follow the machine operations manual guidelines
before mounting the tape:
Do not attach the tape unit to MAINT
The tape must be suitable for a 3420 or 3480 tape unit
Backing Up the NSS and IMG Data Files

To back up all the named saved systems and IMG files on tape, complete the fol-
lowing steps:
Note: This procedure takes approximately 10 minutes.
1. Mount a scratch tape with ring on an available 3420 tape drive, or insert a car-
tridge with the tab protector set to off in an available 3480 tape unit
2. Attach a tape drive to your user ID as 181
3. To dump all NSS system data files to tape, Enter:
----> spxtape dump 181 nss all

4. Substitute the real device number of the tape drive for the value 181:
DUMPING 181
NSS NSS nnnA
.
.
.
SPXTAPE DUMP FUNCTION ON DRIVECOMPLETE
181
READY;
The messages from SPXTAPE tells you that the files are being dumped to tape.
The CMS Ready message may occur between the messages.
5. To dump all IMG system data files to tape, Enter:
----> spxtape dump 181 img all run

where run specifies that the SPXTAPE rewinds and unloads the tape after the
operation.
DUMPING 181
IMG IMG nnnA
.
.
.
SPXTAPE DUMP FUNCTION ON DRIVECOMPLETE
181
READY;
6. Store the tape for emergency use
If it is necessary, you can use this tape and the SPXTAPE command to restore all
NSS and IMG system data files. For more information about the SPXTAPE command,
see the VM/ESA System Operation, SC24-5758.
Named Saved System (NSS) and IMG File Backup/Restore 103

System Operations
Restoring the NSS and IMG Data Files

To restore the NSS and IMG data files, complete the following steps:
1. Logon to MAINT
2. Mount the backup tape on a tape drive
3. Attach a tape drive to your user ID as 181:
----> att rdevno * 181

4. Enter the command:
----> spxtape load 181 nss all rew
NSS NSS nnnn

LOADING 181 A NOW nnnn
.
.
.
NSS NSS nnnn
SPXTAPE LOAD FUNCTION ON DRIVECOMPLETE
181
----> spxtape load 181 img all run

IMG IMG nnnn
.
.
.
IMG IMG nnnn
SPTAPE LOAD FUNCTION ON DRIVECOMPLETE
181
5. To end the reload process, Enter:
----> spxtape end 181

System Operations
Generating a New NCP for the 3745

The GENPEPV6 exec is supplied with this DEMOpkg System to assist in generating
new PEP's for your 3745.
To generate a new NCP, complete the following steps:

1. Logon to MAINT
2. To generate and link-edit a new PEP into the proper LOADLIB, Enter:
----> genpepv6 cc37450

The exec assumes the cc3745 NCPMSTR files exists on the MAINT's 298 mini-
disk. This exec gets 70 cylinders of temporary space and writes the LISTING
files to it. If all steps do not execute properly, you must look at the files on
MAINT's G-disk to determine your error.
3. If there are no errors in the PEP generation, you can release and detach the
temporary disk by Entering:
----> rel g (det
Loading the New NCP to the 3745

After generating a new PEP, you will need to load it into your 3745 by completing
the following steps:
1. Logon to VTAMOPER
2. To inactivate your currently running NCP and have VTAM access the proper
disks, Enter:
----> v inact, id=cc37450, f
----> send vtam ncpacc

3. Load the new NCP by Entering:
----> v act, id=cc37450, load=yes
Loading an OS/390 Job to the 3745

The GENPEPV6 exec will also create an OS/390 job.
1. Send the job to your OS/390 guest where it will be executed
The job will generate the NCP load module on OS/390 also.
2. You will need to inactivate and then activate again the CC37450 from OS/390
with load=no
3. After reloading your 3745, you will need to restart your PVM and RSCS links.
Generating a New NCP for the 3745 105

System Operations

System Operations
Web Server Demo Access

Note
The Web Server demos provided use the latest features such as Java and
frames. To demonstrate the full capabilities of these demos, you need
Netscape 2.02 for OS/2, Netscape 4.0 for Windows 95, or any other fully quali-
fied browser.
The Web Server demos can be accessed through an easy to use menu-controlled
interface. To access the demos, complete the following steps:
1. Make sure the following service machines are logged on:
EWEB001
EWEBCAL
VMWEBSRV
VMROPR
OFFSERV
TSTDBM
TSTCAL
TSTMBX
TSTMAIL
Note: If either the node or IP address has changed from the shipped node of
DEMOXX and home address of 9.39.65.233, then refer to “VM/ESA 2.4.0
DEMOpkg System Customization” on page 81 for the required changes.
2. Access the DEMOnet VM/ESA home page at URL:
http://9.39.65.233 (or the new IP address)
The demos are self-explanatory.
Enterprise/View Text Browser Demo Access

To access Beyond Software's Enterprise/View Text Browser demo:
1. Logon to one of the following demo IDs:
OFV01
OFV02
OFV03
2. On the command line, Enter:
----> WWW
Web Server Demo Access 107

System Operations

User ID Administration
User ID Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Authorizing OfficeVision/VM Users . . . . . . . . . . . . . . . . . . . . . . . . . 111
Authorizing Users for SQL/DS . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Authorizing Users for Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . 112
User ID Administration 109


User ID Authorization
Authorizing OfficeVision/VM Users

The following section describes what needs to be done when you add a new
PROFS user to your system. The tasks you need to perform include adding users
to the UAD file, assigning users to sub-databases, formatting A-disks for users, and
supplying PROFILE execs to users.
Read Chapter 3 of the Managing the Professional Office System, SH21-0580 for
more information.
Adding Users to the UAD File

To add users to the UAD file, complete the following steps:
1. Logon to TSTDBM
2. To display the contents of the OFSUAD file and see which users are already
authorized, Enter:
----> UAD Console

3. Enter the following:
----> UAD INPUT userid ALL,01 NAME=name

Replace the name variable with the users name, for example:
UAD input BROWNR all, 1 NAME=Robbin S. Brown
4. To load the revised UAD file and tell the service machines to also reload the
new UAD file, Enter:
----> UADLOAD
Authorizing Users for SQL/DS

All users of a SQL/DS application server (database) should have minimum connect
authority and should be listed in the SQL/DS table called, SQLDBA.SYSUSERLIST.
Because this is a demonstration system, all general users should have resource
authority, a private dbspace with a name equal to the user ID, a QMF set for
prompted query, and a ARISNEWUS run to create their own copies of the SQL/DS
sample tables.
User ID Authorization 111

To authorize users for SQL/DS, complete the following steps:

From the SQL/DS DB ADMIN user ID (for example: CCDB1ADM):
1. Grant authority to the new user
2. Acquire a private SQL/DS dbspace for the new user
3. Create SQL/DS samples tables and routines for the new user
From the new VM user ID:
1. Access the SQL/DS production code by Entering:
----> vmlink dbccdb4

2. Enable NLS for SQL/DS and the SQL/DS RXSQL feature by Entering:
----> sqllang
3. Start QMF and verify that the default query is set to prompted by Entering:
----> vmlink dmqmf
Authorizing Users for Publishing

To authorize user IDs for ProcessMaster, complete the following steps:
1. Logon to PUBADMIN
2. After the CMS Ready; message, access PUBADMIN's 195 minidisk as B by
Entering:
----> acc 195 b

3. After the CMS Ready; message, start the PUBASERV utility by Entering:
----> pubaserv
The ProcessMaster Administrator Services screen will appear:
. =============== ProcessMaster Administrator Services ============

Command ===> a
F FILES - file services
A AUTH - add, change or purge users access to libraries

P PASSWORD - update library passwords
C CHANGE - change logon id for user
L LIST - list user access to libraries
4. To add a new user or change a user ID's access to PUBLIB1, Enter:
----> A

The Library Access Authority screen will appear:
A. ================== Library Access Authority ======== Page 1

Command ===>
Userid ===> vmuser11 (Press Query PF key to get library list for use
Select: A - add C - change P - purge
Select Library Name Access (R= Read, W= Write)
a publib1 w
5. Enter the user ID and the following values in the fields as shown:
Select: a
Library Name: publib1
Access: w
The following screen will appear indicating the user access has changed:
A. ================== Library Access Authority ======== Page 1

Command ===>
User access changed
Userid ===> VMUSER16 (Press Query PF key to get library list for use
Select: A - add C - change P - purge
Select Library Name Access (R= Read, W= Write)
a PUBLIB1 W library access added
6. Disconnect or logoff PUBADMIN

Note: You can also read about this procedure in the ProcessMaster VM Edition
Administrator Guide, SC34-5034.
User ID Authorization 113


Center Tools
Center Tools
CCBACKUP System Version 1.3 . . . . . . . . . . . . . . . . . . . . . . . . . 117
Basic CCBACKUP Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Problem Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
System Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Tape Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Using the QTAPE Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Using the VTAPE Exec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
CCCMD Control Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Using the CTRFMT DASD Formatting Tool . . . . . . . . . . . . . . . . . . 139

Formatting and Allocating Spool Packs . . . . . . . . . . . . . . . . . . . . . . 141
Using the CTRACNT Tool 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

First Time Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Changing CTRACNT Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
VTAMOPER User ID Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
FCONMON Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
VMLINK Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Center Tools 115

Center Tools

Center Tools
CCBACKUP System Version 1.3

The CCBACKUP system provides a menu-driven automated method for DDR
backups using 3480 or 3490 tape units that have the tape loader feature. The
system consists of a number of execs that provide scheduling, maintenance,
tracking, and control that produces an unattended backup system.
The system is controlled through a command processor (CCCMD) that runs in dis-
connected mode. This job must be active for the CCBACKUP system to operate.
The system utilizes CCCMD for access and scheduling of the job streams that are
autologged by CCCMD. The backup streams can be run on any system attached to
the tape units, provided that the backup user IDs and command processors have
been established. The system, as distributed, can be configured to run backup
jobs on any level system that is connected through RSCS.
Note: To use this system, you must customize it with your device addresses and
installation information. Follow the installation and configuration instructions.
Enhancements with Version 1.2

The major change provided with this version is to allow backups to be scheduled
and run on second level or remote CPUs connected through RSCS. The minidisks
CTRTAPE 411 through 414 have been eliminated. All working files are passed
between CCCMD and the VMBACK1 through VMBACK8 user IDs. The DDR log files
have also been changed to reside on VMBACKx user IDs until the next scheduled
backup and the monthly history has been eliminated. The DDR log files for any
failure will be transferred to the reader file of the next user ID to execute
CCBACKUP. This includes logs files from second level or remote systems.
Group records have been added to the master file. These group records contain
group names and group default run information. The master file maintenance exec
allows the group records to be updated and provides group updates to iterations
and backup frequencies.
Capability has been provided for exits prior to execution of a backup group and at
the completion of the group. The user ID and password for the desired pre- and
postexecution autolog are entered as part of the group information through master
file maintenance. These user IDs could be setup to shutdown databases, service
processors, and any other jobs that will provide a more stable backup. The
postexecution user ID could restart those jobs that were shutdown in the pre-
execution user ID.
Enhancements with Version 1.3

The channel address has been expanded to two positions for tape and DASD
attachments. This provides the ability to operate on larger CPUs with more than 16
channels.
Facilities have been added to allow backups (beg group) with improved data
recording (IDRC), if the feature has been installed on your 3480/3490 tape system.
All execs have been compiled with the REXX compiler for improved performance.
Source files are available in a FCOPY PACKLIB file located on the CTRTAPE 400 mini-
disk called CCBACKUP SOURCE.
CCBACKUP System Version 1.3 117

Center Tools
Basic CCBACKUP Operations
CCBACKUP Menu
To start the system, Enter:
----> CCBACKUP
========== DD&S CC BACKUP SYSTEM ==========

MENU ID: MAINT
==================================================
1. Backup Status
2. Manual Schedule
3. Group/Auto Schedule
4. Master Maintenance
5. View Backup Log
6. Print Labels
7. Configuration
Enter your selection number here: __ <===

==================================================
VER 1.3
PF3/12 End
Figure 46. CCBACKUP System
=========== DD&S VM BACKUP SYSTEM ==============

Update From Streams ID: MAINT
=======================================================
DEMOXA Stream 4 UNABLE TO LINK SYSRES AS 1A
DEMOVM Stream 2 END OF VOLUME ON DDR
CCMS937 Stream 1 DDR FILE NOT = Requested File
=======================================================
<Enter> To Proceed VER 1.3
PF12 EXIT
Figure 47. CCBACKUP Stream Update

Display

Center Tools
These screens are displayed in color by IOS3270.
The CCBACKUP menu is a dynamic menu that provides a list of tasks that are authorized
for the specific user. The menu contains all available functions. The Center adminis-
trator with MAINT access will assign the specific IDs that will be available to perform
basic or extended functions.
When the menu exec starts up, all update files and the log files for any failures are
transferred to that user IDs reader file. The update files will be class P and the log files
will be class L, which should not disturb the user's other reader files. A update exec is
executed to update the master file and master log files.
If a stream did not successfully execute, the reason for error will be noted as shown in
the “Stream Update Display” screen. You will need to write down the error information.
You may continue by pressing Enter . If the error was other than a attach or link
error, a DDR log file is created, and the log file will appear in your reader file to review.
The section on “Problem Determination” on page 125 should be used to aid in
resolving any errors.
If all scheduled jobs have not completed, only those that have completed will be
updated at this time. A review of the Backup Status task will identify the schedules not
completed. If all backup streams have not completed, you should not reschedule any
failures until all backup streams have processed.
The control directory information, including passwords, are passed to the menu program
at execution and passed along to each job selected from the menu. The control
program can detect any changes to the menu exec or trace mode and will not pass any
data when this occurs. If the exec's requiring write access can not gain that status for
any reason, an appropriate error message will display. If this does not seem to be a
normal situation, review the section “Problem Determination” on page 125 to establish
the corrective procedure and for a detailed listing of specific error messages.
Backup Status
The Backup Status task pro-
vides a display of the current
================= DD&S CC BACKUP SYSTEM =============
status and scheduling of all files BACKUP/STATUS ID: MAINT 17 Mar 199 16:42:46
============================================================
as shown in the screen on the ++++++++ LAST BACKUP ++++++++++++++ +++++ NEXT BACKUP ++++
GRP SQ DISK VOL SET DATE TIME BACKUP ID SET DATESTATUS
right. 1 1 E22RES 1 B 3/1 /9 18:43:52 DEMOVM /VMBACK1 C
1 1 E22RES 2 B 3/1 /9 19: 1:41 DEMOVM /VMBACK1 C
3/17/9
3/17/9
1 1 E22PP1 1 B 3/1 /9 19:18:4 DEMOVM /VMBACK1 C 3/17/9
The display shows the date, 2 1 E22PP2 2 B 3/1 /9 19: 1:41 DEMOVM /VMBACK1 C
2 1 E22PP3 1 B 3/1 /9 19:18:4 DEMOVM /VMBACK1 C
3/17/9
3/17/9
time, and file information for the 2 1 E22PP3 2 B 3/1 /9 19:43:59 DEMOVM /VMBACK1 C
2 1 E22PP4 1 B 3/1 /9 2 :13:35 DEMOVM /VMBACK1 C
3/17/9
3/17/9
2 1 E22PP4 2 B 3/1 /9 19:18: 7 DEMOVM /VMBACK2 C 3/17/9
last backup completed and the 2 1 E22RS2 1 B 3/1 /9 19:34: DEMOVM /VMBACK2 C 3/17/9
2 1 E22RS2 2 B 3/1 /9 2 :38:39 DEMOVM /VMBACK2 C 3/17/9
backup stream where the DDR 2 1 E22OP1 1 B 3/1 /9 19:59:51 DEMOVM /VMBACK2 C
2 1 E22OP1 2 B 3/1 /9 2 :33:41 DEMOVM /VMBACK2 C
3/17/9
3/17/9
was performed. 2 1 E22SPL 1 B 3/1 /9 21: 4: 5 DEMOVM /VMBACK2 C
2 1 E22SPL 2 B 3/1 /9 21:32:12 DEMOVM /VMBACK2 C
3/17/9
3/17/9
2 1 E22SRV 1 B 3/1 /9 2 :15:41 DEMOVM /VMBACK3 C 3/17/9
2 1 E22SRV 2 B 3/1 /9 2 :42:19 DEMOVM /VMBACK3 C 3/17/9
2 2 E22MAN 1 B 3/1 /9 21: 8:33 DEMOVM /VMBACK3 C 3/17/9
The NEXT BACKUP information is 2 2 E22MAN 2 B 3/1 /9 21:37:13 DEMOVM /VMBACK3 C 3/17/9
==================================================================
determined by the iterations PF3 Menu PF8 Forward
VER 1.3
PF12 EXIT
and frequency as setup in the

master file for each group.
Figure 48. CCBACKUP Status Display

Center Tools
OVERDUE will appear in the status column for any files that are past due based on the
calculated next backup date. Sch Nodeid will appear in the status column for those
files scheduled for backup where nodeid is the scheduled system netid.
This screen is displayed in color by IOS3270.
Auto/Manual
Schedule
If the Group/Auto Schedule task ================= DD&S CC BACKUP SYSTEM =====================
SCHEDULER ID: OP1 17 Apr 199 16:45:42
is chosen, which would be the ====================================================================
NODEID GROUP DUE DATE DAYS PAST
normal choice, the group menu DEMOVM
1 VM 292 BACKUPS
2 VMR69 BACKUPS
4/18/92
4/13/92 4 Automatic Schedule
will appear as shown in CCMS937 6 937 VMIS6
8 MVS9 1 BACKUPS
4/16/92
4/26/92
1 Automatic Schedule
=====================================================================
Figure 49. If any of the groups Enter NODEID where Selected Group is to RUN
PF3 Menu PF12 EXIT
VER 1.3
have a due date past the

current date, they will be
selected with an Automatic Figure 49. CCBACKUP Grp/Auto Schedule Display 1
Schedule notation as shown.
If more than one group is past due and enough tape drives are available, multiple
groups will be automatically scheduled, otherwise, the group that is the most past due
will be selected.
If you wish to chose another group or process multiple groups, you may do so by
changing the designated group selections by entering a nodeid for the group or by
blanking out the one that appears.
If you have chosen more

=====================================================================
groups than can fit on the VER 1.3
PF3 Menu PF2 Run Schedule PF12 EXIT
number of 3480 /3490 drives
available, you will receive an
error message. Figure 50. CCBACKUP Grp/Auto Schedule Display 2
Be careful not to schedule a backup to run on a nodeid that can not access the disk to
be backed up or a failure will occur. When you press Enter , the bottom of the
screen, as shown in Figure 50 will appear. By pressing PF2 the groups will be
scheduled. The streams, which represent a stacker unit, will be setup to not split up
multiple volumes of a file.

Center Tools
The screen, as shown on the

right, will be positioned and dis- ==================
SCHEDULER 1 of 5
DD&S
ID:
CC BACKUP SYSTEM ===================
OP1 17 Apr 199 16:46: 2
===================================================================
played with the first stream and ++++++++++ LAST BACKUP +++++++++++++ SCHEDULING INFO
GRP SQ FILE VOL SET DATE TIME NODE/ID STREAM/SET/NODE
with the set fields filled in. 1
1
1 E22RES 1
1 E22RES 2
B 3/1 /9 18:43:52 DEMOVM /VMBACK1
B 3/1 /9 19: 1:41 DEMOVM /VMBACK1
From this point on, the opera- 1
1
1 E22PP1 1
1 E22PP1 2
B 3/1 /9 19:18:4 DEMOVM /VMBACK1
B 3/1 /9 19:43:59 DEMOVM /VMBACK1
2 1 E22PP2 1 B 3/1 /9 18:43:52 DEMOVM /VMBACK1 1 A DEMOVM
tion of the scheduling exec will 2
2
1 E22PP2 1
1 E22PP2 2
B 3/1 /9 18:43:52 DEMOVM /VMBACK1 1 A DEMOVM
B 3/1 /9 19: 1:41 DEMOVM /VMBACK1 1 A DEMOVM
operate the same as if the 2
2
1 E22PP3 1
1 E22PP3 2
2 1 E22PP4 1 B 3/1 /9 2 :13:35 DEMOVM /VMBACK1 1 A DEMOVM
Manual Schedule task was 2 1 E22PP4 2 B 3/1 /9 19:18: 7 DEMOVM /VMBACK2 1 A DEMOVM
2 1 E22RS2 1 B 3/1 /9 19:34: DEMOVM /VMBACK2 2 A DEMOVM
chosen. 2
2
1 E22RS2 2
1 E22OP1 1
B 3/1 /9 2 :38:39 DEMOVM /VMBACK2 2 A DEMOVM
2 1 E22OP1 2 B 3/1 /9 2 :33:41 DEMOVM /VMBACK2 2 A DEMOVM
2 1 E22SPL 1 B 3/1 /9 21: 4: 5 DEMOVM /VMBACK2 2 A DEMOVM
When you have entered or 2 1 E22SPL 2 B 3/1 /9 21:32:12 DEMOVM /VMBACK2 2 A DEMOVM
===================================================================
AUTO SCHEDULE FOR GROUP 2, 4 COMPLETED MAKE CHANGES AND SET
changed any of the desired PF3 Menu <Enter> To Proceed PF12 EXIT
stream, set, and nodeid fields

of a page, press Enter to
continue. Figure 51. CCBACKUP Scheduler Display1
After pressing Enter , the bottom of the screen will change as shown in Figure 52.
You can page forward or backward and continue reviewing or updating a schedule.
Repeat the same procedure to page to another screen, even if nothing is changed or
updated on the current screen.
If you are manually updating the schedule or making changes from an automatic
schedule, make sure that multiple volumes of a file are not split across streams creating
a situation where contiguous data between volumes could be on different time frames.
When the schedule is complete

====================================================================
and no further changes are VER 1.3
PF3 Menu PF2 SET SCHEDULE PF7 Back PF8 Forward PF12 EXIT
required, set the schedule by
pressing PF2 .
Figure 52. CCBACKUP Scheduler Display 2
This is done when the SET SCHEDULE function appears, as in the screen shown in
Figure 52, after pressing Enter .
If at any time you wish to discard any scheduling that you have updated prior to the SET
SCHEDULE, you can press PF12 to exit the CCBACKUP session, or press PF3 to return
to the menu.
If there is a requirement that a backup stream be completed prior to another stream

starting, there is a dependency feature built into the system. This feature will operate
only within a nodeid. Because of the complexity that dependencies add, you must be
very careful not to create a dependency loop that can not be fulfilled. This task will do
some limited editing, but can not detect all conditions that could cause a loop.

Center Tools
Now you are beginning the final

stage of the scheduling =================
SCHEDULER
DD&S
ID:
CC BACKUP SYSTEM ====================
OP1 17 Apr 199 16:46:3
===================================================================
process. The displays, as
DEMOVM 348 Drive 35 Start: 4/17/9 18:
shown in Figure 53 on STREAM 1 Reserve Drive Immediately: N
Dependency (N=No or Stream) : N
page 122 on the right and on
the next page, will be displayed ===================================================================
for completion for each required <Enter> To Proceed
VER 1.3
PF12 CANCEL
stream in stream order. The
system will make some
assumptions and default with all Figure 53. CCBACKUP Scheduler Display 3
required fields as shown in
Display 2 screen. You can
change any of the fields at this
point.
The tape drive assignment is the next available drive number. If you are unsure of what
drives are available, enter a ? to produce an error message showing the available
drives.
The backup should begin with a start date, either current or next day, and with a future
start time only.
The tape drive selected will not

================= DD&S CC BACKUP SYSTEM ====================
be attached until the job stream SCHEDULER ID: OP1 17 Apr 199 16:46:3
===================================================================
starts execution. If you wish DEMOVM 348 Drive 35 Start: 4/17/9 18:
the drive to be reserved imme- STREAM 1 Reserve Drive Immediately: N
Dependency (N=No or Stream) : N
diately, enter a Y in the Reserve

Master File PRE/POST Autologs Scheduled
Drive Immediately field --this Autolog SHUTSERV Before Stream: 1
Autolog STRTSERV After Stream : 4
At 17:45
Completes
will cause the job stream to be ==================================================================
VER 1.3
autologged and the tape drive <Enter> To Proceed PF12 CANCEL
to be attached as soon as
CCCMD receives the schedule.
The job stream will not start Figure 54. CCBACKUP Scheduler Display 3 with
execution until the requested Pre/Post Schedule
start date and start time.
If the stream is not dependent on another stream completing, the Dependency field is N.
If a dependency is desired, enter the number of the stream that must complete prior to
this stream starting. If a dependency is entered, the stream will not start at the sched-
uled time until the dependency is satisfied.
If pre- and postautolog schedules have been entered through master maintenance, the
second screen shown above will display on the first stream for that group rather than
the first screen. The before and after stream numbers and the start time may be
changed. The date used will be the one you requested in the before stream. The
after stream will be the date and time that the stream completes. If for any reason the
after stream does not complete, the postautolog will not take place. To eliminate the
pre- and postautolog jobs, this task must be cancelled and master maintenance per-
formed.

Center Tools
When you press Enter , the

screen shown in Figure 55 on ==================== DD&S
SCHEDULER ID:
CC BACKUP SYSTEM =======================
OP1 17 Apr 199 16:46:4
======================================================================
page 123 on the right will
DEMOVM 348 Drive 35 Start: 4/17/9 18:
appear to give the loading STREAM 1
LOAD SCHEDULE
Reserve Drive Immediately : N
Dependency : N
schedule for the tape drive.
+--------------------+
The tapes are mounted in the | E22PP2 Vol 1 Set A |
+----+---------------+----+
TOP SLOT
stacker top to bottom just as | ES21P2 Vol 2 Set A |

+----+---------------+----+
| E22PP3 Vol 1 Set A |
displayed. Make certain that +----+---------------+----+
the tapes are mounted correctly +----+---------------+----+
before going on to the next +---+----------------+----+
| E21PP4 Vol 2 Set A | LOADED
+---------------------+
screen.
===================================================================
VER 1.3
<Enter> To Proceed PF12 CANCEL
Once you have proceeded to
the next screen, you can not go
back to make changes. If Figure 55. CCBACKUP Scheduler Display 4
changes are required. press
PF12 to cancel the schedule
and start over.
Once the last load schedule screen is displayed, press Enter The backup streams
will be updated with the schedule. Messages will be displayed recapping the schedule
for a final review while the update is taking place.
As part of the stream update, this task passes the schedule, including the starting date
and time, to the command processor (CCCMD) at the selected nodeid. When the
schedule is received at the command processor, it reports back and a message will be
displayed saying the schedule is set. Even if no schedule is required, all nodeids will
be updated. When the scheduled date/time is reached the corresponding VMBACK job
will be autologged by CCCMD.
If you wish to change a schedule prior to the start date/time, you may do so by going
into the Manual Schedule task and make whatever changes are required. The new
schedule will be loaded and used when you set the schedule. If you want to cancel a
schedule that has been set, you can follow the same procedure and blank out all
entries. This will update a null schedule.
View Backup Log

The View Backup Log task is
normally used to find a specific ============== DD&S CC BACKUP SYSTEM ====================
backup tape to restore data. VIEW/LOG ID: OP1 17 Apr 199 16:45: 7
================================================================
To find a specific file, enter the Select File To View: SYSRES__
file name to select, as shown in ================================================================

VER 1.3
Figure 56 on this page. You PF3 Menu PF12 EXIT
may Enter ALL to select all

files, or Enter any prefix, such
as CC, to select all files with Figure 56. CCBACKUP View/Log Display 1
those starting characters.

Center Tools
The data selected will be dis-

played, as shown in Figure 57 ================
VIEW/LOG 1 of 1
DD&S CC BACKUP SYSTEM =========================
ID: OP1 17 Apr 199 16:45: 7
======================================================================
on page 124 on this page, G ++++ STARTED ++++ ++++ FINISHED +++ BACKUP TAPE
DISK V P Seq SET DATE TIME DATE TIME EXEC ID DRIVE
with all the volumes in order by SYSRES 1 1 1
SYSRES 1 1 1
B 4/1 /9 18:24: 2 4/1 /9 18:43:52 DEMOVM/VMBACK1 36
A 4/ 4/9 19: :46 4/ 4/9 19:17:33 DEMOVM/VMBACK1 36
the most current backup to the SYSRES 1 1 1
SYSRES 1 1 1
D 3/28/9 2: :52 3/28/9 2:17: 9 DEMOVM/VMBACK6 355
C 3/2 /9 18:12:47 3/2 /9 18:29:47 DEMOVM/VMBACK1 36
oldest. ======================================================================
VER 1.3
PF3 Select PF12 EXIT
An equal number of entries will

be available to match the iter-
ations or sets on the master Figure 57. CCBACKUP View/Log Display 2
file. If the number of volumes
decreases or a disk is no
longer included, those log
entries will remain indefinitely.
These screens are displayed in color by IOS3270.

Center Tools
Problem Determination
A number of different situations may arise that will cause any or all of the backup
streams to not complete processing. This section will detail most of the conditions and
provide you with some insight to solving other problems that may occur.
If you find that there are still tapes in the stacker, make sure that the switch on the tape
loader is set on AUTO. If it is not, then set it, load the next tape, and the backup stream
will resume automatically. If the backup stream did not resume automatically, then
something else has occurred and you need to proceed with problem determination.
First, query the VMBACKx user IDs on all scheduled nodes to see if they are logged on.
If so, then Enter the following command to each one:
----> SM VMBACKx QUITQUIT

where x is the stream.
Recheck each user ID to make sure it is logged off. If not, then you will need to force
them off or have someone with force authority to do it for you. You may then execute
CCBACKUP to bring up the error messages.
CCBACKUP Errors
Table 23. CCBACKUP Error Messages
ERROR MESSAGE: EXPLANATION:
Update Program Did Not Some user ID has read access
Receive R/W Access to Master Files to CTRTAPE 400.
Streams Does Not Someone has edited the control
Match CCCMD Control Files file. Reprocess the
Configuration.
No Response From CCCMD... Something has happened to the
Try Later command processor CCCMD.
Query CCCMD and if it is in
disc mode then force it off.
Autolog CCCMD.
Access Not Possible The user or users shown in the
Now...“user” is Using Files error message have access to the files.

Center Tools
If an error has occurred during

the process of a job stream, an ===================
Update From Streams
DD&S VM BACKUP SYSTEM =====================
ID: MAINT
=====================================================================
error message will be logged.
If more than one error occurred, DEMOVM Stream 4 UNABLE TO LINK SYSRES AS 1A
the one listed will be the first DEMOVM Stream 2 END OF VOLUME ON DDR
CCMS937 Stream 1 DDR FILE NOT = Requested File

one encountered. The error
message will be displayed as =====================================================================
<Enter> To Proceed VER 1.3
shown in the screen to the PF12 EXIT
right. The description and cor-

rective action of each error that
can display is shown in “Stream Figure 58. CCBACKUP Stream Update Display
Update Error Reference” on
page 126.
If no errors have occurred, this display will not be shown.
Write down the node, stream and error information as shown on the “Stream Update
Display” screen--it will be displayed only once. If all streams have not completed, or if
an RSCS link is down, only those streams reporting back will be processed. You can
review the Backup Status display to see if other scheduled streams have not been
processed.
The console messages are spooled and analyzed for each DDR operation. The con-
tents of these are stored on the VMBACKx 191 disk, where x represents the job stream
number, on the scheduled node. If an error occurred with the DDR, then the spooled
log is transferred back to the first user ID to issue CCBACKUP. If the spooled log is lost
from your reader files for any reason, you can access them by use of GIMME VMBACKx
from a user ID on the scheduled node.
Review the WORKCONS LOG file where the last log is stored. This file is usually the one to
look at in case of a failure. The WORKCONS LOG is added to the LASTCONS LOG, which is
the entire log for the stream. These logs will remain on the 191 disk until the next
backup schedule is processed and will then be erased.
Stream Update Error Reference

Table 24 (Page 1 of 2). Stream Update Error Messages
GETTAPE ERR nnn ATTACHED TO user vvv The
R/Wtape drive assigned to the stream was
assigned to another user ID.
For some reason the command processor
GETTAPE ERR NOT ATTACHED FOR SOME REASON
was not able to vary on and attach the
assigned tape drive. Check to make sure
the channel enable switch is on or that
there is no physical connection problem.
GETTAPE No Response From CCCMD The command processor is either not
running or something has happened to it.
Force it if necessary and autolog CCCMD.

Center Tools
Table 24 (Page 2 of 2). Stream Update Error Messages

GETDASD ERR NO BUFFERS AVAILABLE For some reason the buffers, where the ori-
ginal status of a DASD is saved prior to
attaching to the backup job, have filled up
or have been overlayed. Shut down
CCCMD by MSG CCCMD QUITQUIT and
autolog CCCMD.
GETDASD ERR N/A nnn ATTACHED TO user The
vvvdevice address specified in the master
file was not available because it was
attached to a userid.
GETDASD ERR IN USE BY OTHER USERS The device address specified in the master
file is attached to system and the use count
is not zero.
GETDASD ERR DASD ATTACH FAILED The device address specified in the master
file is not physically available to be
attached.
UNABLE TO LINK diskname AS 1A The diskname specified in the master file
could not be found. It is not physically
available or there was not full pack overlay
setup on the DIRECT file.
END OF VOLUME ON DDR When analyzing the console messages,
after the completion of the DDR for the
current file, an end of volume message was
found. This means that the requested
extents could not fit on one tape and that
the files will need to be sized or another
volume added. Review console log in your
reader or in the WORKCONS LOG on the
VMBACKx 191 minidisk.
NO (END OF JOB) FOUND When analyzing the console messages after
the completion of the DDR for the current
file, no end of job message was found in
the proper sequence. Review console log
in your reader or in the WORKCONS LOG file on
the VMBACKx 191 minidisk.
NO (END OF DUMP) FOUND When analyzing the console messages after
the completion of the DDR for the current
file, no end of dump message was found in
the proper sequence. Review console log
in your reader or in the WORKCONS LOG file on
the VMBACKx 191 minidisk.
DDR FILE NOT = Requested File The DASD address specified in the master
file does not have the name that agrees
with the master file.
DDR EXTENTS NOT = Requested Extents The extents requested for this volume does
not match what was actually completed.
Review console log in your reader or in the
WORKCONS LOG file on the VMBACKx 191
minidisk.
An error occurred with DDR where the
DDR INPUT EXTENTS NOT = OUTPUT EXTENTS
output did not match the input.

Center Tools
System Maintenance
Master Maintenance
The Master Maintenance task
==================== DD&S CC BACKUP SYSTEM =====================
on the CCBACKUP menu provides MASTER/MAINTENANCE ID: MAINT 17 Apr 199 16:43:3
==================================================================
for the addition, deletion, or Group : _ =ALL Groups
change of master file records. Set Mode: _

(A)dd
(D)elete
Select the Group and Set Mode (C)hange
================================================================== =
of operation as shown in PF3 Menu
VER 1.
PF12 EXIT
3
Figure 59. The mode will show

on the second line of the
display. If (A)dd mode is Figure 59. Master/Maintenace Display 1
selected, the Figure 61 screen
will appear.
The second screen, Figure 60

======================== DD&S CC BACKUP SYSTEM =====================
will appear for either the MASTER/MAINTENANCE Mode: CHANGE 1 of 1
======================================================================
(C)hange or (D)elete mode. If G S
CONTROL
V I
BACKUP SPECIFICATIONS
.........DASD................S Jul
LAST BACKUP
an asterisk is entered in the P Q File L T Frq Type Adr FR/Ext TO/Ext T Date Time
1 1 1 E22RES 1 3 14 338 1A 885 B 89184 19: :
ID
VMBACK1
2 1 1 E22RES 2 3 14 338 1A 885 1769 B 89184 19:12:19 VMBACK1
Group field, all groups will be 3 1 2 E22PP1 1 3 14 338 1A 885 B 89184 19:31:15 VMBACK1
4 1 2 E22PP1 2 3 14 338 1A 885 1769 B 89184 19:47:28 VMBACK1
displayed but no group changes 5 1 3 E22PP2 1 3 14 338
6 1 3 E22PP2 2 3 14 338
1A
1A 885
885
1769
B 89184 2 :17: 5 VMBACK1
B 89184 2 :35:38 VMBACK1
will be allowed. When a valid __ <== Make Selection
======================================================================
group is entered, only that VER 1.3
PF3 Change/Mode PF7 Back PF8 Forward PF1 GROUP/CHANGE PF12 EXIT
group's records will be dis-
played.
Figure 60. Master/Maintenance Display 2
Figure 61 allows all fields to be
entered for the (A)dd mode,
including all fields under the
CONTROL heading.
If you wish to change or delete

================== DD&S CC BACKUP SYSTEM ========================
a record, enter the record MASTER/MAINTENANCE Mode: ADD 17 Apr 199 16:37:26
=====================================================================
number you wish to select in Group
CONTROL
_
front of the Make Selection Sequence
File
__
________
Volume _
arrow, as seen in the Figure 60
BACKUP SPECIFICATIONS
screen. Details will be shown Iterations(Number/Sets)
Frequency(Every x Days)
_
___
on Figure 61. To delete, press DASD Type
DASD Address
____
____
DASD Extents FR: __________ TO: __________
Enter , and you will be asked ====================================================================
VER 1.3
to press PF2 to confirm. PF3 Change/Mode PF12 EXIT
Figure 61. Master/Maintenance Display 3
You may alter any of the fields appearing on the screen under the BACKUP
SPECIFICATIONS heading. You may also change the file sequence number in the
CONTROL section.

Center Tools
Field Definitions
The description of each field in the MASTER/MAINTENANCE screen is as follows:
Group The number assigned to package the associated files.
Sequence The sequence the file is to appear in the group and order of backup.
File The file directory name.
Volume The tape volume of the file.
Iterations Number of rotating sets.
Frequency Number of days between backups.
DASD Type 3370, 3375, 3380 etc.
DASD Address (Explanation Follows)
DASD Extents From & To Extents or “ALL” that will fit on a tape.
Group/Change Mode
If you wish to make a group-wide change or change specific group information, press
PF1 on Figure 60 on page 128 and complete the instructions below.
Note: If a file needs to be moved from one group to another, it is necessary to delete
and add it as a new record to the new group.
When PF1 is pressed on

================ DD&S CC BACKUP SYSTEM ======================
Figure 60 on page 128, and a MASTER/MAINTENANCE Mode: GROUP/CHANGE 17 Apr 199 16:43:3
====================================================================
specific group has been Group : 1
selected, the screen shown in Group Name : VM 292 BACKUPS
Iterations(Number/Sets) : 3
Figure 62 will appear. Any of
Frequency(Every x Days) : 14
the fields shown may be Improved Data Recording : N
changed. If the Iterations and Default Run Node : DEMOVM
Frequency fields are changed, Pre Backup Autolog : NONE ________
all records in the group are Post Backup Autolog : NONE ________
====================================================================
VER 1.3
updated. The Group Name is PF2 Confirm Group Update PF3 Change/Mode PF12 EXIT
used throughout the system to

identify the group. The Default
Run Node is used for the auto Figure 62. Master/Maintenance Display 4
schedule of the group.
If a userid has been setup to do any database shutdown or any other pre-backup activ-
ities, enter the user ID to be autologged and its password. The same would be true for
any post backup process. Make sure the user ID and password reside on the target
backup node.
Note: Improved data recording and compact are mutually exclusive.
Ensure that the extents are sized accordingly so that the DDR can fit on a single tape.
The Backup program will verify that the extents dumped match what was requested. If
a second volume is required, the DDR will terminate with an error. The best method to
determine the size of each tape is to manually DDR the entire DASD file. Set the
extents smaller than what was dumped on a full tape in order to provide growth. To
determine the amount of tape used on a cartridge, use TAPEMAP. A full tape is approx-
imately 534 feet.

Center Tools
DASD Address
The DASD Address in Display 3 can be either 01A0, if a full pack overlay is used, or the
actual address. When an actual address is used, the file can not be in use at the time
of the backup. As an example, you would need to shutdown MVS prior to updating
those files. The full pack overlay will allow you to backup a file attached to the system.
Note: It must be an attached system.
If you added files and have specified 01A0, make sure that you have added the corre-
sponding full pack overlay to the DIRECT file through DIRMAINT. Because xxxRES
(where xxx is XAS, R68, and so on.) will always be in use when running backups, a full
pack overlay will be setup for them to use as an example.
Print Labels
The Print Labels task allows
================= DD&S CC BACKUP SYSTEM =======================
you to create labels for the LABEL/PRINT ID: MAINT 17 Apr 199 16:45:27
====================================================================
3480/3490 tapes from the data PRINTER OUTPUT WILL BE ROUTED TO LBL348
stored on the master file. The Enter Group to Print: _

Disk Name: _______
Set:
Vol:
_
output is either written to your = ALL (Group, Set, Disk or Vol)
A-disk or sent to a printer Enter Group Name Override: _______________

====================================================================
depending on the option PF3 Menu PF12 EXIT
VER 1.3
selected in the CCBACKUP

profile. Flexibility is provided
that allows you to print a label Figure 63. CCBACKUP Label/Print Display 1
for one file and one set of a
group, to printing an entire
group of files and all sets.
An example of the display is shown in Figure 63. If you desire to print labels for an
entire group, enter the number assigned to that group. Then enter the letter of the set
you wish to print or an * if you want all sets printed. If you want only a file, enter the
file name or an * to print all files. If you want all volumes enter an * or the specific
volume needed. The group name from the master file will be used or it may be over-
ridden.
When you press Enter , the labels are produced. The entries on the screen remain
and are not cleared. Make your next selection, continue the process until all desired
labels are created, and press PF3 to return to the menu.
The output will be either sent to a printer with the tag specified in the profile, or written
to a file CCBACKUP $LABEL$ A, if specified in the profile. The profile option set is the first
detail line, as shown above in Figure 63.

Center Tools
The label format created is for

an 18 line by 28 character CUSTOMER CENTER
SYSTEM BACKUP
YourNode
label, as shown in the Sample
SYSTEM BACKUPS
Label. The labels are pin feed SET A
Group 1
3 inches wide and 3 inches E22RES

Vol 1
338 DDR COMPACT
348 /38K
long perf to perf. It contains CCBACKUP VM/ESA 1.2.2

IBM INTERNAL USE ONLY
two parts, the tape label and
the end label.
E22RES SET SYSTEM BACKUP
Vol 1 A SYSTEM BACKUPS
If you setup an RSCS printer for
your label, it must be defined
as 18 lines per page.
Figure 64. Sample Label
Note: If file option is used, CCBACKUP $LABEL$ will be added to an existing file if one is
present. You should erase it after you have completed each use.
Configuration
The Configuration task will be run to initially install and customize your Center's
system. It may be run again at any time there is a requirement to change any of the
system parameters. It is entirely menu driven with a fill- in-the-blank style operation. In
most cases, there is a default that has been filled in initially and then what ever the
current setting there after.
This screen, as shown in

============= DEMOVM CC BACKUP SYSTEM ==========================
Figure 65 on page 132, deals CONFIGURATION ID: MAINT 17 Apr 199 17: 9:18
====================================================================
with most of the installation NETID
CPU Name
: DEMOVM
: GAMMA 4381 128 9
hardware aspects. The NETID 348 Drive Addrs: 35 - 353
Enter as nnnn-nnnn or nnnn,nnnn
is determined by a query of
Other Tape Addrs: 38 - 386, 388- 38F
your system. If it ever changes Enter as nnnn-nnnn or nnnn,nnnn
within your system, you must TAPE LABELS : FILE

Enter RSCS Printer Tag or "FILE"
====================================================================
rerun the configuration. The <Enter> To Proceed
VER 1.3
PF12 EXIT
backup job will not run if the
NETID does not match.
Figure 65. CCBACKUP Configuration Display 1

Center Tools
The CPU type and serial number are from a query of the CPU. You may assign a name
to the CPU that will be referenced in the system.
Enter the address ranges of your 3480/3490 tape drives; this includes other tape drives
you may have. The 3480/3490 drives are used to determine the available drives for
backup use. Both sets are used by the tape management system.
If you have a printer setup with an RSCS tag to print your tape labels, Enter the label,
otherwise Enter:
----> FILE
If FILE is specified the output will be written to disk and can be manually routed to a
printer. When Enter is pressed, the fields entered will be checked for errors and
displayed. If no errors are detected, the next screen will appear.
The data from the first screen

================= DEMOVM CC BACKUP SYSTEM =====================
will be displayed at the top, but CONFIGURATION ID: MAIN 17 Apr 199 17: 9:18
==================================================================
can not be changed. If a NETID
CPU Name
: DEMOVM
: GAMMA 4381 128 9
change is required, press PF3 348 Drive Addrs: 35 - 353
Other Tape Addrs: 38 - 386, 388- 38F
to return to the prior screen. TAPE LABELS : FILE FILE
Figure 66 provides an example. Job Streams : 4 8 Have been provided with Base System.
Mini Disk Passwords: ALL passwords For Each Group Must Be Same.
CTRTAPE 4 CCTR RD: RCCTR WR: WCCTR MR: MCCTR

The number of job streams CCCMD 191
CTRTAPE 4 1 WCTR RD: ALL WR: WCTR MR: WCTR
defaults to the number of tape =====================================================================
NOTE. Before MDPW s Are Changed See Reference Guide VER 1.3
drives available. The system <Enter> To Proceed PF3 Prev Screen PF12 EXIT
provides for operation of up to

eight streams. If more than
eight drives are available, no Figure 66. CCBACKUP Configuration Display 2
more than eight streams can be
used.
The minidisk passwords may be changed. If they are changed, make sure that the
DIRECT file is updated to reflect the new passwords. Ensure the DIRECT file is not
updated until this job has completed and before autolog of CCCMD, or the system will
not be able to operate. If this does happen then the passwords must be changed back
and this procedure started from the beginning.
The screen, as shown in

=============== DEMOVM CC BACKUP SYSTEM =======================
Figure 67 on page 133, pro- CONFIGURATION ID: MAINT 17 Sep 199 17:28:56
=====================================================================
vides for identification of (2)nd MASTER
Node Streams
Level and (R)emote nodes to DEMOVM 4
REMOTE/SECOND LEVEL
be included in the CCBACKUP Channel (R)emote VMBACKx
Node Streams Override (2)nd Level AUTOLOG PW
system. The node must corre- CCMS937 4 5 R
spond to the RSCS/Netid of the ====================================================================
VER 1.3
<Enter> To Proceed PF3 Prev Screen PF12 EXIT
system. An example of a
remote system could be a 9370
connected via RSCS and
attached into an interface of the
3480/3490 controller.

Center Tools
Enter the Node name and number of Streams (usually the same as the master node) in
the appropriate fields. If the channel address of the 3480/3490 tape unit is not the
same, enter the Channel Override. (An example would be to enter 5 if the 9370
address are 550-553 and the 4381 is 350-353. The CCBACKUP system will reference
the drives as 350-353 and override the backup schedule sent to the 9370.)
Enter an R for a node not contained within this CPU, or a 2 if the node is running
second level. Because the second level command processor is different from the first
level, a password for VMBACK1 through VMBACK8 must be provided. Whenever the
passwords change, the configuration must be rerun. Files are sent to CCCMD at the
second level node to update its passwords and linkage to the first level. No configura-
tion is required at the second level.
This screen, as shown in

============ DEMOVM CC BACKUP SYSTEM ==========================
Figure 68, provides for the CONFIGURATION ID: MAINT 17 Apr 199 17:18:12
===================================================================
update of userids that are Authorized Restricted Use:
MAINT
Authorized Basic Use:
MAINT
allowed to have basic or OPERATOR OPERATOR
OP1
OP2
restricted use of the system. OP3
OP4
Those listed under the ===================================================================
VER 1.3
restricted column have access <Enter> To Proceed PF3 Prev Screen PF12 EXIT
to the system maintenance and

installation tasks. The basic
users have access to the other
operational tasks.
When you have completed all =====================================================================

NOTE. You Must AUTOLOG CCCMD Upon Completion Of This Job. VER. 3
entries, press Enter to PF2 Confirm Update PF3 Prev Screen PF12 EXIT
proceed. At this point, the

bottom of the screen will
change as indicated in Figure 69. CCBACKUP Configuration Display 4A
Figure 69. You can proceed
by pressing PF2 to confirm
the update.
Before you confirm the update you may wish to go back screen by screen and review
your entries. When you confirm the update and the job ends, complete any DIRECT file
changes and autolog CCCMD.

Center Tools
System Installation
The command processor CCCMD, as distributed with all VM systems, is included with
GROUP_PW in AUTOLOG1. If you do not desire to run the tape management or
CCBACKUP systems, then you need to remove CCCMD from GROUP_PW.
The CCBACKUP system as distributed provides eight userids for the backup streams to
run in. They are VMBACK1 through VMBACK8. Full pack overlays are distributed with
the DIRECT file for each VM system to include all its pack names.
You are ready to customize your system. You should be logged on to MAINT. Make
sure that CCCMD is running in disc mode and Enter:
----> CCBACKUP
When you get the CCBACKUP menu, choose Configuration and follow the procedure
described in the section “Configuration” on page 131.
If you wish to create labels for your cartridge tapes, the system will generate labels that
are 18 lines by 28 characters. If you do not have labels that size, you may want to use
the FILE option and edit the labels to a format that will fit the size labels you have.
You are now ready to use the system. No other installation is required to operate the
tape management system.

Center Tools
Tape Management System

The tape management system has been provided to introduce a level of control for
tape usage when multiple systems are sharing the same groups of tape drives. It
also provides for access to tape drives from ids with no attach authority.
The tools available to access the system are:

QTAPE for query
VTAPE for tape access commands
The control program CCCMD must be running for these execs to operate.
Using the QTAPE Exec

This exec can be run from a CMS Ready; screen by Entering:
----> QTAPE
==========> DD&S T A P E M A N A G E M E N T S Y S T E M <=====

QTAPE OP3 On DELTA/DEMOVM 8 Oct 1999 17:27:1
========================================================================
CUU ALPHA BETA DELTA
4381 13355 4361 6 822 9721 128 9
338 DEMOPKG 338 BUILD VM/ESA-DEMOVM
38 |
MVS 38 | ------------- | ------------- |
381 |
FREE | FREE | FREE |
382 |
383 |
384 |
385 |
386 |
OP2 181 | ------------- | ------------- |
388 |
+++++++++++++ | +++++++++++++ | +++++++++++++ |
389 |
+++++++++++++ | +++++++++++++ | +++++++++++++ |
38A |
+++++++++++++ | +++++++++++++ | +++++++++++++ |
38B |
+++++++++++++ | +++++++++++++ | +++++++++++++ |
38C |
+++++++++++++ | +++++++++++++ | +++++++++++++ |
38D |
+++++++++++++ | +++++++++++++ | +++++++++++++ |
38E |
+++++++++++++ | +++++++++++++ | +++++++++++++ |
38F |
+++++++++++++ | +++++++++++++ | +++++++++++++ |
35 |
FREE | +++++++++++++ | +++++++++++++ |
351 |
FREE | +++++++++++++ | +++++++++++++ |
352 |
FREE | +++++++++++++ | +++++++++++++ |
353 |
FREE | +++++++++++++ | +++++++++++++ |
| | | |
| | | |
| | | |
=========================================================================
PF3 EXIT PF4 SPLIT PF5 First PF12 EXIT
QTAPE Screen Display
Note: This screen is displayed in color by IOS3270.
The exec will refresh itself every 60 seconds and will redisplay the screen. The
screen display length is a variable length determined by the terminal type and
number of lines that it can display. The number of screens required to display your
Tape Management System 135

Center Tools
installations tape drives is determined by the definition chosen in the installation

and customization of your system. If multiple screens are required to display all
tape drives, PF7 and PF8 functions will appear at the bottom of the display to allow
forward and reverse screen positioning. PF4 will provide the capability of splitting
3420 and 3480 drives on separate screens.
If you specify a parameter of ALL, then all other tape CCU's will be displayed after
the standard displays.
The second line of the example, as shown in the QTAPE screen display, will indicate
the user ID from which the command was issued and the system that is running the
ID.
The following describe the notations as shown in the screen:

Userid Shows Virtual CUU Assigned
FREE Available For Use
------------ Attached To User On Other CPU
++++++++++++ Not Available For Use
OFFLINE Not Available For Use
Using the VTAPE Exec

The VTAPE exec communicates with a control program CCCMD that runs on an ID
with full attach authority and can process attach or vary commands even though
your user ID that may not have that authority. It also provides a level of control to
assure that a tape can not be used that is assigned to another CPU without forcing
that condition.
This exec should be used for all attach, detach, and vary commands that involve
the use of tape units.
The VTAPE exec can be run from a CMS Ready; screen by Entering:
----> VTAPE

Center Tools
=======> DD&S T A P E M A N A G E M E N T S Y S T E M <========

VTAPE OP2 On DELTA/DEMOVM 6 Oct 1999 9:43:
========================================================================
Command : ATT
ATT Attach
DET Detach
VARY ON VARY ON
VARY OFF VARY OFF
Real tape address : 38
USERID : OP2
Virtual tape address : 181
Force the attach (Y/N) : N
CCCMD ATT 38 OP2 181 N

RC( ) TAPE 38 ATTACH TO OP2 181
Note: Please enter the information above. All are required fields.
========================================================================
PF3 EXIT <Enter> Proceed PF8 Forward PF12 EXIT
VTAPE Screen Display 1
The defaults used for the screen are attach, first available tape drive, executing
userid, and virtual CUU of 181. Any of the fields can be changed and will be exe-
cuted when the Enter key is pressed. A message will be displayed to either
indicate a successful completion or an error condition.
The real tape address must be a valid tape unit that is online to the system. For
3480/3490 tapes, the attach command will automatically vary them on or off with
the ATT or DET commands. If you are not sure of what is available, press PF8 to
display the VTAPE screen display 2 as shown on the following page.
The user ID can be either your ID or any valid ID; either logged on or in discon-
nected mode.
The virtual tape address can be any valid virtual address for a tape unit such as
181, 182, and others.
Notes:
1. The Force the attach field should only be used if you wish the same tape unit
to be attached to two systems at the same time. Care must be taken not to
unload a tape or cause a positioning problem for a user on another system.
2. The status line below the force line shows the command that was submitted to
the control program. It is followed by the returned status that will indicate the
command was successful or will give the associated error message. If any of
the parameters submitted are invalid, the message “Invalid Function or
Parameters” will be displayed.
3. This screen is displayed in color by IOS3270.
Tape Management System 137

Center Tools
To display the screen to show the current status of all tape drives, press PF8 :
=======> DD&S T A P E M A N A G E M E N T S Y S T E M <========

VTAPE OP2 On ALPHA 6 Oct 1999 9:43: 3
========================================================================
CUU ALPHA BETA DELTA
4381 13355 4361 6 822 4381 128 9
338 DEMOPKG 338 BUILD Not Running
38 |FREE | FREE | +++++++++++++ |

381 |FREE | FREE | +++++++++++++ |
382 |FREE | FREE | +++++++++++++ |
383 |FREE | FREE | +++++++++++++ |
384 |OP3 181 | OP2MNT 181 | +++++++++++++ |
385 |OP1 181 | ------------- | +++++++++++++ |
386 |OP4 181 | ------------- | +++++++++++++ |
388 |+++++++++++++ | +++++++++++++ | +++++++++++++ |
389 |+++++++++++++ | +++++++++++++ | +++++++++++++ |
38A |+++++++++++++ | +++++++++++++ | +++++++++++++ |
38B |+++++++++++++ | +++++++++++++ | +++++++++++++ |
38C |+++++++++++++ | +++++++++++++ | +++++++++++++ |
38D |+++++++++++++ | +++++++++++++ | +++++++++++++ |
38E |+++++++++++++ | +++++++++++++ | +++++++++++++ |
38F |+++++++++++++ | +++++++++++++ | +++++++++++++ |
35 |FREE | +++++++++++++ | +++++++++++++ |
351 |FREE | +++++++++++++ | +++++++++++++ |
352 |FREE | +++++++++++++ | +++++++++++++ |
353 |FREE | +++++++++++++ | +++++++++++++ |
| | | |
| | | |
| | | |
=========================================================================
PF3 EXIT PF5 First PF12 EXIT
VTAPE Screen Display 2
Note: This screen is displayed in color by IOS3270.
The second line of the example, as shown in the VTAPE screen display 2, will indi-
cate the user ID from which the command was issued and the system that is
running on that ID.
The following describe the notations as shown in the screen:

Userid Shows Virtual CUU Assigned
FREE Available For Use
------------ Attached To User On Other CPU
++++++++++++ Not Available For Use
OFF-LINE Not Available For Use
CCCMD Control Program

The CCCMD user ID runs in a disconnected mode and operates with the QTAPE
and VTAPE execs by means of messages sent back and forth utilizing the IUCV
feature. This same control program is used by the CCBACKUP system for not only
3480 tape commands but also directory access control and the autolog of backup
jobs scheduled by the CCBACKUP system.

Center Tools
Using the CTRFMT DASD Formatting Tool

The CTRFMT exec is provided to ICKDSF format a single pack or range of packs by
prompting the user without having to lookup the actual DSF commands.
This exec has the cylinder ranges for a 3380 Model E and K, a 3390 Model 2, and
a 9345 Model 2.
1. To start the exec, Enter:
----> CTRFMT
2. You will be asked to provide the type DASD and physical addresses as shown
in the following screens:
Note: The packs will be labeled with SCRcuu or SCccuu.
Enter Type Of DASD (338 E 338 K 339 or 9345)

338 k
Enter Beginning Address CCUU

338 k
Enter Beginning Address CCUU
e d
Enter Ending Address CCUU or Blank if Single Drive
FORMATING 338 MODEL K DASD
ADDR LABEL
E D SCRE D
Reply GO to format or QUIT to exit
CTRFMT Setup/Run
When you have entered all the required information, a summary will be dis-
played.
3. To proceed, Enter:
----> GO
The physical DASD address will be attached to this user ID during formatting.
The console will be spooled to this user ID.
Using the CTRFMT DASD Formatting Tool 139

Center Tools
The console messages will begin to appear:

DASD E D ATTACHED TO OP1 1
ICK 3 E DEFINE INPUT DEVICE: FN FT FM, "CONSOLE", OR "READER"
CONSOLE
ICK 31E DEFINE OUTPUT DEVICE: FN FT FM, "CONSOLE", OR "PRINTER"
CONSOLE
ENTER INPUT COMMAND:
CPVOL FMT MODE(ESA) UNIT( 1) VOLID(SCRE D) NOVFY RANGE( ,2654)
ICK 3D REPLY U TO ALTER VOLUME 1 CONTENTS, ELSE T
U
ICK 3 2 I CPVOL IS OPERATING IN VM/ESA MODE
ICK 7 I DEVICE INFORMATION FOR 1 IS CURRENTLY AS FOLLOWS:
PHYSICAL DEVICE = 338
STORAGE CONTROLLER = 388
STORAGE CONTROL DESCRIPTOR = 5
DEVICE DESCRIPTOR = 1E
ICK 3 9 I VOLUME SERIAL = SCREOD
ICK 3 22I FORMATTING THE DEVICE WITH FILLER RECORDS
ICK 3 11I CYLINDER RANGE TO BE FORMATTED IS - 2654
ICK 3 I CPVOL REPORT FOR 1 FOLLOWS:
FORMATTING OF CYLINDER STARTED AT: 14:14: 4

FORMATTING OF CYLINDER 2654 ENDED AT: 14:14:16
VOLUME SERIAL NUMBER IS NOW = SCRE D
CYLINDER ALLOCATION CURRENTLY IS AS FOLLOWS:

TYPE START END TOTAL
---- ----- --- -----
PERM 2654 2655
ICKDSF - CMS/XA DEVICE SUPPORT FACILITIES 13.
ICK 1I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS
14:14:16 2/ 3/92

END
END
ICK 2I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS
CTRFMT Console Messages

4. You can disconnect from this user ID by Entering:
----> #CP DISC

When the formatting has been completed, the exec will logoff the user ID.
5. Review the spooled console log, as shown in the CTRFMT console messages
screen, to be sure no errors were detected.

Center Tools
Formatting and Allocating Spool Packs

To format and allocate the spool packs, complete the following steps:
1. To start the CTRFMT EXEC, Enter:
----> CTRFMT SPOOL

2. You will be asked to provide the spool pack name, the type of DASD, and the
physical addresses as shown in the following screens:
Enter Spool Pack Name

es2spl

es2spl
338 e
Enter Spool Pack Address CCUU
SPOOL PACK FORMAT AND ALLOCATION ES2SPL on E D
Format 1769
Allocate
PERM
SPOL 1 1769
Reply GO to format or QUIT to exit
CTRFMT SPOOL Setup/Run

After entering all the required information, a summary will be displayed.
3. To proceed, Enter:
----> GO
The physical DASD address will be attached to this user ID during the format-
ting. The console will be spooled to this user ID.

Center Tools
The console messages will begin to appear:

CPVOL FMT MODE(ESA) UNIT( 1) VOLID(TSTSPL) NOVFY RANGE( , 1 )
ICK 3 2 I CPVOL WILL PROCESS 1 FOR VM/ESA MODE
ICK 3 9 I VOLUME SERIAL = TSTSPL
ICK 3 22I FORMATTING THE DEVICE WITH FILLER RECORDS
ICK 3 11I CYLINDER RANGE TO BE FORMATTED IS - 1
U
FORMATTING OF CYLINDER STARTED AT: 15: 5: 8

FORMATTING OF CYLINDER 1769 ENDED AT: 15: 5:17
VOLUME SERIAL NUMBER IS NOW = ES2SPL

---- ----- --- -----
PERM 1769 177

15: 5:17 1/2 /93

CPVOL ALLOC MODE(ESA) UNIT( 1) VFY (TSTSPL) TYPE((SPOL, 1, 1 ))
ICK 3 2 I CPVOL WILL PROCESS 1 FOR VM/ESA MODE
ICK 3 9 I VOLUME SERIAL = ES2SPL
ICK 3 24I DEVICE IS CURRENTLY FORMATTED WITH FILLER RECORDS
U

---- ----- --- -----
PERM 1
SPOL 1 1769 1769

15: 5:25 1/2 /93

END
ICK 2I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS
CTRFMT SPOOL Console Messages

4. To disconnect from this user ID, Enter:
----> #CP DISC

When the formatting and allocation has been completed, the exec will logoff the
user ID.

Center Tools
5. Review the spooled console log, as shown in the “CTRFMT Console

Messages” screen, to be sure no errors were detected
The spool pack will be ready for the next system IPL to be included as CP owned.

Center Tools

Center Tools
Using the CTRACNT Tool 1.0

The CTRACNT exec is provided to simplify the process of maintaining DISKACNT
files on an automatically scheduled basis. Account files can be sent to a user ID or
catcher machine for processing so the account records or the files can be purged.
CTRACNT updates the ACNTSERV options for automatic processing and it can be
run from any user ID.
1. To start the exec, Enter:
----> CTRACNT
CENTER ACCOUNTING RECORD MANAGEMENT
Send Files To: (DEMOPKG)MYUSERID

DAILY AT 1:
Administrator: (DEMOPKG)OP1
PF11 CHANGE OPTIONS PF3/12 EXIT
This exec uses NEATWIND for the screen processing. The options from the
previous run have been stored and will be shown.
2. If you wish to change the options, press PF11 and follow the change proce-
dure described later
When you finish updating the options, ACNTSERV will be autologged.
The ACNTSERV machine will use MPVM to logon to DISKACNT at the specified time
and process the account files.
First Time Initialization

For MPVM to setup the initial password, you must complete the following steps:
1. Logon to ACNTSERV by Entering:
----> LOGON ACNTSERV NOIPL
----> I CMS
2. When CP Read appears on the screen, Enter:
----> AC (NOPROF
3. When READY; appears on the screen, Enter:
----> MPVM * ACNTPWV (TARGET yournodeid
Using the CTRACNT Tool 1.0 145

Center Tools
4. When you see the MPVM LOGONID panel, Enter the initial password for DISKACNT
You will see the screens appear as MPVM logs on and returns. Do not press
any keys until a clear screen with a Ready appears.
5. To start the ACNTSERV machine's automatic processing, Enter:
----> PROFILE
Changing CTRACNT Options

To change the options, complete the following steps:
1. For automatic generation of reports, Enter a Y
If you wish to continue to execute your reports as required, Enter N
CHANGE OPTIONS
AUTOMATIC SCHEDULE
_ Y=Yes N=No
2. Enter the USERID and NODEID of the administrator, if different than the
userid/nodeid shown:
CHANGE OPTIONS
AUTOMATIC SCHEDULE
ADMINISTRATOR
USERID ________ NODEID ________
All completion and error notices will be sent to this userid.

3. To select the frequency, place an / over the in front of the desired frequency:
CHANGE OPTIONS
AUTOMATIC SCHEDULE
DAILY
WEEKLY
MONTHLY

Center Tools
4. Enter the appropriate parameter for the frequency selected:
CHANGE OPTIONS
AUTOMATIC SCHEDULE
_____ DAY OF WEEK (ie. FRI)

_____ TIME
Note: Each will require a time be entered in a 24 hour clock format as shown:
HH:MM
Weekly requires the appropriate day of the week abbreviation. Monthly
requires the day of the month to run.
5. To select the output option, Enter an / over the in front of desired option:
CHANGE OPTIONS
DISPOSITION OF OUTPUT
PURGE
SEND TO RECEIVER
The appropriate option screen will be displayed:
CHANGE OPTIONS
SEND TO RECEIVER
USERID ________ NODEID ________
Using the CTRACNT Tool 1.0 147

Center Tools

Center Tools
VTAMOPER User ID Tools

The VTAMOPER user ID is provided as a secondary console for VTAM and has the
necessary built in tools to allow you to do VTAM and RSCS commands and avoid
logging onto VTAM.
The V and D commands are setup to do the appropriate send to VTAM. RSCS
commands can be given by using VMSG instead of SMSG. If you have links to
other processors that need to be recovered from time to time, an exec can be
setup to issue all the required commands to recover a link. You will find examples
on the VTAMOPER 191 minidisk.
After an IPL, it is necessary to clear VTAM one time to allow acceptance of VTAM
commands. The first time you logon to the VTAMOPER user ID after an IPL, it will
use MPVM to logon to VTAM and clear it for messages. When the VTAM password
changes, a LOGONID Change Password screen will be displayed and it will ask you
for the new password.
VTAMOPER User ID Tools 149

Center Tools

Center Tools
FCONMON Tool
FCONMON is selected from the VMTOOLS selection of products. We use this tool
to help identify points of interest in tuning and problem determination. The tool has
an expiration date of December 31, 2000.
Documentation is available on FCONMON 191: FCONX LIST382 . Additionally,

there is online help while running the monitor feature. This documentation gives
the reader some ideas and limits to review and also helps to determine where to
look and what to look for in many areas of performance analysis.
For example: Is it CPU bottleneck? Is it I/O bottleneck? Is it DASD constrained?
FCONMON Tool 151

Center Tools

Center Tools
VMLINK Tool
VMLINK is used for linking and accessing minidisks and SFS directories.
For VMLINK online information, Enter:
----> VMLINK
and press PF1 to display the help screens.
For more information on VMLINK, take a look at the VMLINK NAMES file that is on
MAINT's 19E minidisk (accessed as the Y-disk).
The following are some examples of how VMLINK can be used, either within execs
or directly from the CMS command line:
To add code to a profile exec or another exec that you may wish to modify,
Enter the command:
----> EXEC VMLINK OV* SQL* (QUIET

The OV and SQL are nicknames in the VMLINK NAMES file. These are lists of
individual minidisks that will be accessed.
To release and detach the minidisks that were accessed in the previous
example, Enter the command:
----> EXEC VMLINK OV* SQL* <DET> (QUIET

To link and access the OfficeVision minidisks from an exec:
1. Exit OfficeVision
2. To release and detach the minidisks automatically, Enter:
----> EXEC VMLINK OV* (QUIET INVOKE OFFICE

To link and access the OfficeVision minidisks, Enter the following after the CMS
Ready message:
----> VMLINK OV* (QUIET A

This exec also sets the LASTING GLOBALV file to execute this command each
and every time you logon to this user ID.
To remove the AUTOLINK that was previously set, Enter the following after the
CMS Ready message:
----> VMLINK OV* (QUIET R
VMLINK Tool 153

Center Tools

Emergency Operations Procedures

Alternate Nucleus IPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Restoring from Backup Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Restoring a System Volume Example . . . . . . . . . . . . . . . . . . . . . . . 159
Specific Minidisk Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Environmental Record Editing and Printing Program (EREP) . . . . . . . 165

Processing EREP Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Emergency Operations Procedures 155


Alternate Nucleus IPL

If you are having a problem bringing up VM/ESA and suspect that it may be due to
changes you made when generating a new CP nucleus, you may be able to recover
without restoring packs by IPLing a backup alternate nucleus. See the section
“IPLing the VM/ESA 2.4.0 DEMOpkg (Optionally)” on page 91.
Alternate Nucleus IPL 157


Restoring from Backup Tapes

This section describes a procedure that uses the DDR program and provides for the
restoration of the new VM/ESA DEMOpkg System after a catastrophic event.
Note: If the DASD medium to be restored has never been labelled, you must run
the device support facility program before restoring the dump/restore tapes.
The procedure assumes that the stand-alone Dump/Restore (DDR) program has
been written as the second file on the stand-alone utilities tape. The program
restores the following DASD volumes:
D240R1 D240L1
D240R2 D240P1
D240B1 D240P2
D240B2 D240O1
D240I1 D240S1
If you do not need to restore all of these DASD volumes, use only a portion of the
procedure that applies.
Notes:
1. The two volumes with SPOOL space, D240R1 and D240B1 should be restored at
the same time, otherwise, spool files may be lost.
2. DASD volumes that contain minidisks belonging to the same SFS filepools
should also be restored together or the SFS filepool will become unusable.
Restoring a System Volume Example
Restoring D240R1
If you have IPLed from the standalone DDR program tape, mount the first backup
tape for D240R1 on the same drive and continue with the restore by Entering:
ENTER:
----> input cuu xxxx

where cuu is the address of the tape drive from which you IPLed and where xxxx is
a 3480 or 3490 tape drive.
ENTER:
----> output cuu 3390 d240r1

where cuu is the address of the 3390 actuator to which D240R1 is to be restored.
ENTER:
----> restore all

Note: The DDR program may ask you to confirm that the correct volume is
mounted (respond as necessary).
Restoring from Backup Tapes 159

RESTORING D24 R1
DATA DUMPED . . .
.
.
.
END OF RESTORE
Note: If you are requested to mount a second reel, do so and the DDR program
will continue automatically.

Specific Minidisk Restore

The previous chapter provides procedures for restoring an entire DASD volume. To
restore a specific minidisk from a backup tape, complete the following steps:
1. Logon to MAINT
2. To get a copy of the current directory, Enter:
----> dirm user w
Ready;
RDR FILE nnnn SENT FROM DIRMAINT PUN WAS

mmmm RECS yyyy CPY 1
A NOHOLD NOKEEP
----> receive nnnn user withpass a (rep

3. Produce a minidisk map of your system by Entering:
----> dirmap user withpass a
FILE USER MDISKMAP A has been created.

READY;
The USER MDISKMAP file will be created on MAINT 191 (A-disk).

4. To determine the physical extents of the minidisk to be restored, use the mini-
disk map
5. Determine the backup tape where the minidisk extents reside
6. Mount the tape and attach the drive to MAINT as 181
7. Restore the minidisk by Entering:
----> ddr
Enter:
----> sysprint cons

Enter:
----> input 181 xxxx

where xxxx is a 3480 or 3490 tape drive.
Enter:
----> output cuu xxxx

where xxxx is the device type (3390) of the DASD actuator or drive to which the
minidisk is to be restored, and where cuu is the virtual address of the DASD
actuator or drive as determined from Table 25 on page 163.
Specific Minidisk Restore 161

Note: The device type to which the minidisk is restored must be the same as
the device type from which the minidisk was backed up.

If the volume to which the minidisk is being restored does not have a full-pack
minidisk defined to MAINT (see Table 25), then link the full-pack minidisk of that
volume before doing the DDR. For example:
----> #cp link d240p2 1a0 1ao mw

ENTER MULT PASSWORD:
----> ccms
DASD 1A LINKED R/W
Enter:
----> restore extent1 to extent2

where extent1 is the first block or cylinder, and where extent2 is the last block
or cylinder of the minidisk being restored.
Restoring ...
End of restore
Enter
End of Job
R;
Table 25. Virtual Addresses for Minidisk Restore

Minidisk Being Address User ID Alternate Alternate
Restored to Volume Address User ID
D240R1 1A0 D240R1 123 MAINT
D240R2 1A0 D240R2
D240B1 1A0 D240B1
D240B2 1A0 D240B2
D240I1 1A0 D240I1
D240P1 1A0 D240P1
D240P2 1A0 D240P2
D240L1 1A0 D240L1
D240O1 1A0 D240O1
D240S1 1A0 D240S1
Specific Minidisk Restore 163


Environmental Record Editing and Printing Program (EREP)

The Environmental Record Editing and Printing Program assists the IBM service
representative to manage and maintain your data processing installation. It is a
diagnostic aid (an application program) that runs under all three of the IBM
System/370 operating systems. EREP reads errors and other environmental
records generated by hardware and software, edits the records, and produces
printed reports at your request. The reports show how things are with the entire
installation, an I/O subsystem, and with an individual device. The error and envi-
ronmental records are the basis for the reports.
On VM/ESA, error recording involves three steps:

1. CP must create and store EREP records.
2. A special virtual machine called the EREP virtual machine must transfer the
records from storage to disk.
3. Finally, you must process the records on disk in a way that helps your installa-
tion diagnose and fix hardware problems.
The EREP virtual machine retrieves an EREP record when:

The virtual machine is defined
It has started the RETRIEVE program
It has room on its A-disk for new EREP records
The EREP virtual machine is logged on when the system is IPLed and it automat-
ically starts retrieving EREP records. Over time, the EREP virtual machine's A-disk
fills up with EREP records. CP sends a message to the operator when the A-disk is
75% full, 90% full, and completely full. You may also logon to the EREP virtual
machine and check the disk yourself. When the disk is full, you must process
some of the old records and erase some files to make room for new ones.
Processing EREP Records

To process any EREP records, complete the following steps:
1. To logon to EREP, Enter:
----> logon erep

2. Enter EREP's password
3. At the Ready; prompt, Enter the following commands:
----> #cp external

HCPRET8 67A ENTER END OR SUMMARY
----> summary
HCPRET8 66I x EREP RECORDS PROCESSED
----> #cp external
Environmental Record Editing and Printing Program (EREP) 165

HCPRET8 67A ENTER END OR SUMMARY
----> end
Ready;
4. To process the EREP records so far accumulated, print out nine separate
reports (depending on the types of records) and erase the error records file,
Enter:
----> reports
PROCESSING EREP REPORTS.....PLEASE WAIT

PRJ FILE nnnn SENT TO RSCS
RDR AS xxxx
EREP TASK COMPLETE
Ready;
5. To start the EREP virtual machine retrieving error records again, Enter:
----> retrieve erep
COMMAND ACCEPTED
HCPCRC8 64I Recording data retrieval has been started,
recording LOGREC for userid EREP.
6. To disconnect the EREP virtual machine, Enter:
----> #cp disc

Note: If you have not started a system printer (for example, 4245) as class H, the
EREP print files will remain in EREP's print que until you do something with them. If
a system printer has been started class H, the files will automatically print.

Appendix
Appendix 167
Appendix A. DISKMAP of the VM/ESA 2.4.0 DEMOpkg
System
1USER WITHPASS MAP OF MINIDISKS 1 :39:44 21OCT99

+____ ________ ___ __ _________ ________ _______
VOLSER DEVTYPE OWNERID VADR MDE START END LEN FLAGS
+______ _______ _______ ____ ___ _____ ___ ___ _____
----------------------------------------------------------------------
DDTRES 339 -2 LABEL XXXX XX 1
TESTVSE 1C MR 1 1113 1113
TESTVSE 1C1 MR 1114 2225 1112
----------------------------------------------------------------------
D24 B1 339 -2 D24 B1 1A MR 2225 2226
MAINT 124 MR 2225 2226
$ALLOC$ A 2 R 1
P735FALT 191 MR 1 17 17
P735FALT 2C2 MR 18 33 16
ADMIN 191 MR 34 53 2
APING 191 MR 54 55 2
AUDITOR 191 MR 56 6 5
A327 191 MR 61 62 2
CCCMD 191 MR 63 64 2
CTRMAINT 191 MR 65 73 9
CTRTAPE 4 RR 74 78 5
CTRTAPE 4 1 RR 79 79 1
CTRTASK 191 MR 8 87 8
CTRTASK 22 MR 88 95 8
CTRTASK 221 MR 96 1 3 8
DCEADMIN 191 MR 1 4 1 5 2
DCECORE 191 MR 1 6 111 6
DCECORE 511 MR 112 138 27
DCECORE 512 MR 139 145 7
FCONMON 191 MR 146 155 1
156 163 8 GAP
FFST 191 MR 164 167 4
ISPVM 191 MR 168 169 2
ISPVM 192 MR 17 279 11
LFSSERV 191 MR 28 284 5
LFSSERV 2 1 MW 285 3 4 2
LFSSERV 2 2 MW 3 5 324 2
MAINT B2 MR 325 334 1
MAINT 37 MR 335 337 3
MAINT 371 MR 338 342 5
LFSADM 191 MR 343 347 5
ACNTSERV 191 MR 348 349 2
ACNTSERV 193 MR 35 351 2
352 354 3 GAP
MAINTSTK 191 MR 355 362 8
MAINTSTK 454 MR 363 412 5
NSLD 191 MR 413 416 4
PRETEST 431 MR 417 438 22
P648 38D 36F MR 439 443 5
P648 39D 191 MR 444 448 5
P648 39D 2C2 MR 449 453 5
P648 39D 2DF MR 454 46 7
P648 39D 29D MR 461 465 5
P648 39D 36F MR 466 487 22
P6841 E 4 1 MR 488 491 4
P6841 E 4 2 MR 492 493 2
Appendix A. DISKMAP of the VM/ESA 2.4.0 DEMOpkg System 169

P6841 E 4 3 MR 494 497 4
P6841 E 4 5 MR 498 5 2 5
P684158 4 1 MR 5 3 5 6 4
P688188A 39E MR 5 7 536 3
MAINT 6CF1 MR 537 558 22
VMSERVS 191 MR 559 561 3
VMSERVU 191 MR 562 564 3
VMSERVR 191 MR 565 566 2
VMSERVS 3 1 WR 567 571 5
VMSERVS 3 2 WR 572 576 5
VMSERVS 3 3 WR 577 581 5
VMSERVS 3 4 WR 582 6 6 25
VMSERVS 3 5 WR 6 7 69 84
VMSERVS 3 6 WR 691 774 84
VMSERVS 3 7 WR 775 858 84
VMSERVS 3 8 WR 859 942 84
VMSERVS 3 9 WR 943 1 26 84
VMSERVU 3 1 WR 1 27 1 35 9
VMSERVU 3 2 WR 1 36 1 49 14
VMSERVU 3 3 WR 1 5 1 63 14
VMSERVU 3 4 WR 1 64 1 66 3
VMSERVU 3 5 WR 1 67 1 72 6
VMSERVR 3 1 WR 1 73 1 74 2
VMSERVR 3 2 WR 1 75 1 75 1
VMSERVR 3 3 WR 1 76 1 76 1
VMSERVR 3 4 WR 1 77 1 78 2
VMSERVR 3 5 WR 1 79 1 79 1
VMSERVR 3 6 WR 1 8 1 81 2
VMSERVR 3 7 WR 1 82 1 83 2
P688216A 191 MR 1 84 1 88 5
P688216A 2A2 MR 1 89 1 93 5
P688216A 2A6 MR 1 94 1 98 5
P688216A 2B2 MR 1 99 1133 35
P688216A 2C2 MR 1134 1138 5
P688216A 2D2 MR 1139 1148 1
P688216A 29E MR 1149 1168 2
P688216A 39E MR 1169 1188 2
SCRIPT 191 MR 1189 1189 1
SLMADMIN 191 MR 119 1194 5
SLMSERV 191 MR 1195 1219 25
SYSMON 191 MR 122 1224 5
VMBACK1 191 MR 1225 1226 2
VMBACK2 191 MR 1227 1228 2
VMBACK3 191 MR 1229 123 2
VMBACK4 191 MR 1231 1232 2
VMBACK5 191 MR 1233 1234 2
VMBACK6 191 MR 1235 1236 2
VMBACK7 191 MR 1237 1238 2
VMBACK8 191 MR 1239 124 2
VMBACK9 191 MR 1241 1242 2
VMUSER 1 191 MR 1243 1246 4
VMUSER 2 191 MR 1247 125 4
VMUSER 3 191 MR 1251 1254 4
VMUSER 4 191 MR 1255 1258 4
VMUSER 5 191 MR 1259 1262 4
VMUSER 6 191 MR 1263 1266 4
VMUSER 7 191 MR 1267 127 4
VMUSER 8 191 MR 1271 1274 4
VMUSER 9 191 MR 1275 1278 4
VMUSER1 191 MR 1279 1282 4
VTAMOPER 191 MR 1283 1284 2
2VMVMG1 2B3 MR 1285 1286 2
2VMVMG1 2C2 MR 1287 1287 1
1288 13 13 GAP

$PAGE$ A 2 R 13 1 16 3
$SPOOL$ B 2 R 16 1 18 2
RACFVM 2 MR 18 1 182 2
RACFVM 3 2 MR 1821 1828 8
RACFVM 3 5 MR 1829 1896 68
RACFVM 49 MR 1897 1914 18
RACFVM 191 MR 1915 1923 9
RACFSMF 191 MR 1924 1933 1
RACFSMF 192 MR 1934 1943 1
RACFADM 191 MR 1944 1953 1
IBMUSER 191 MR 1954 1954 1
2VMVMY2 2C2 MR 1955 1955 1
2VMVMY2 4 MR 1956 1979 24
5654 1 A 193 MR 198 1983 4
5654 1 A 2C2 MR 1984 1993 1
5654 1 A 29A MR 1994 2 3 37
5654 1 A 4 1 MR 2 31 2 4 1
5654 25 29A MR 2 41 2 65 25
5654 29B 2C2 MR 2 66 2 67 2
FCONMON 2 MR 2 68 2 87 2
2 88 2225 138 GAP
----------------------------------------------------------------------
D24 B2 339 -2 D24 B2 1A MR 2225 2226
$ALLOC$ B 2 R 1
5767 2P 2B2 MR 1 85 85
5767 2P 2C2 MR 86 94 9
5767 2P 2D2 MR 95 144 5
5767 2P 2A6 MR 145 153 9
5767 2P 2A2 MR 154 162 9
5767 2P 29E MR 163 164 2
5767 2P 59 MR 165 182 18
5767 2P 5 5 MR 183 223 41
5767 2P 599 MR 224 254 31
5767 2P 191 MR 255 279 25
28 29 11 GAP
P648 38D 191 MR 291 295 5
P648 38D 2A2 MR 296 3 5
P648 38D 2A6 MR 3 1 3 5 5
P648 38D 2B2 MR 3 6 31 5
P648 38D 2C2 MR 311 312 2
P648 38D 2DF MR 313 317 5
P648 38D 2D2 MR 318 322 5
P648 38D 37F MR 323 327 5
P648 39D 2A2 MR 328 328 1
P648 39D 2A6 MR 329 329 1
P648 39D 2B2 MR 33 346 17
P648 39D 2D2 MR 347 363 17
P648 39D 37F MR 364 382 19
P654 33A 191 MR 383 397 15
P654 33A 2A2 MR 398 4 2 5
P654 33A 2A6 MR 4 3 4 7 5
P654 33A 2B2 MR 4 8 442 35
P654 33A 2C2 MR 443 447 5
P654 33A 2D2 MR 448 457 1
P654 33A 29E MR 458 481 24
P6841 E 191 MR 482 5 2 21
P6841 E 2A2 MR 5 3 511 9
P6841 E 2A6 MR 512 52 9
P6841 E 2B2 MR 521 533 13
P6841 E 2C2 MR 534 537 4
P6841 E 2D2 MR 538 556 19
P6841 E 29D MR 557 565 9
P6841 E 4 MR 566 576 11
P6841 E 4 4 MR 577 581 5

P684158 191 MR 582 585 4
P684158 2A2 MR 586 587 2
P684158 2A6 MR 588 589 2
P684158 2B2 MR 59 593 4
P684158 2C2 MR 594 597 4
P684158 2D2 MR 598 6 5 8
P684158 4 MR 6 6 6 9 4
P68416B 191 MR 61 637 28
P68416B 2A2 MR 638 639 2
P68416B 2A6 MR 64 641 2
P68416B 2B2 MR 642 711 7
P68416B 2C2 MR 712 713 2
714 73 17 GAP
P68416B 29E MR 731 8 7
P688188A 191 MR 8 1 815 15
P688188A 2A2 MR 816 82 5
P688188A 2A6 MR 821 825 5
P688188A 2B2 MR 826 86 35
P688188A 2C2 MR 861 865 5
P688188A 2D2 MR 866 875 1
P688188A 29E MR 876 9 5 3
P695 13D 1 1 MR 9 6 9 8 3
P695 13D 191 MR 9 9 918 1
P695 13D 2A2 MR 919 919 1
P695 13D 2A6 MR 92 92 1
P695 13D 2B2 MR 921 922 2
P695 13D 2C2 MR 923 923 1
P695 13D 2D2 MR 924 933 1
P695 13D 2 1 MR 934 936 3
P695 14D 1 MR 937 939 3
P695 14D 191 MR 94 949 1
P695 14D 2A2 MR 95 95 1
P695 14D 2A6 MR 951 951 1
P695 14D 2B2 MR 952 953 2
P695 14D 2C2 MR 954 954 1
P695 14D 2D2 MR 955 964 1
P695 14D 2 MR 965 967 3
P696234A 191 MR 968 972 5
P696234A 2A2 MR 973 973 1
P696234A 2A6 MR 974 974 1
P696234A 2B2 MR 975 979 5
P696234A 2C2 MR 98 983 4
P696234A 2D2 MR 984 993 1
P696234A 29E MR 994 998 5
2VMVMG1 191 MR 999 1 32 34
2VMVMG1 2A2 MR 1 33 1 33 1
2VMVMG1 2A6 MR 1 34 1 34 1
2VMVMG1 2B2 MR 1 35 1 8 46
2VMVMG1 2B4 MR 1 81 11 2 22
2VMVMG1 2D2 MR 11 3 1115 13
2VMVMG1 411 MR 1116 115 35
2VMVMG1 412 MR 1151 1158 8
2VMVMG1 413 MR 1159 1183 25
2VMVMY2 191 MR 1184 1192 9
2VMVMY2 2A2 MR 1193 1197 5
2VMVMY2 2A6 MR 1198 12 2 5
2VMVMY2 2B2 MR 12 3 1233 31
2VMVMY2 2B3 MR 1234 1252 19
2VMVMY2 2D2 MR 1253 1377 125
2VMVMY2 29E MR 1378 1414 37
2VMVMZ3 191 MR 1415 1424 1
2VMVMZ3 2A2 MR 1425 1426 2
2VMVMZ3 2A6 MR 1427 1428 2
2VMVMZ3 2B2 MR 1429 1445 17

2VMVMZ3 2C2 MR 1446 1447 2
2VMVMZ3 2D2 MR 1448 1464 17
2VMVMZ3 49E MR 1465 1481 17
5654 1 A 191 MR 1482 15 6 25
5654 1 A 2A2 MR 15 7 1516 1
5654 1 A 2A6 MR 1517 1526 1
5654 1 A 2B2 MR 1527 1596 7
5654 1 A 2C4 MR 1597 1598 2
1599 1638 4 GAP
5654 1 A 4 2 MR 1639 1648 1
5654 1 A 49A MR 1649 1685 37
5654 1 A 493 MR 1686 1689 4
5654 25 191 MR 169 1699 1
5654 25 2A2 MR 17 17 1 2
5654 25 2A6 MR 17 2 17 3 2
5654 25 2B2 MR 17 4 1728 25
5654 25 2C2 MR 1729 1738 1
5654 25 2D2 MR 1739 1748 1
5654 25 49A MR 1749 1773 25
5654 29B 191 MR 1774 1786 13
5654 29B 2A2 MR 1787 1787 1
5654 29B 2A6 MR 1788 1788 1
5654 29B 2B2 MR 1789 18 1 13
5654 29B 2D2 MR 18 2 1814 13
5654 29B 4 MR 1815 1827 13
5654 29B 4 1 MR 1828 184 13
5686 81A 191 MR 1841 1853 13
5686 81A 2A2 MR 1854 1855 2
5686 81A 2A6 MR 1856 1857 2
5686 81A 2B2 MR 1858 187 13
5686 81A 2C2 MR 1871 1873 3
5686 81A 2D2 MR 1874 1886 13
5686 81A 4 MR 1887 1899 13
MAINT D2 MR 19 1914 15
MAINT D6 MR 1915 1929 15
MAINT 377 MR 193 1938 9
MAINTSTK 45 MR 1939 1978 4
MAINTSTK 451 MR 1979 2 28 5
MAINTSTK 452 MR 2 29 2 52 24
MAINTSTK 453 MR 2 53 2 53 1
MAINTSTK 46 MR 2 54 2 57 4
MAINTSTK 461 MR 2 58 2 65 8
MAINTSTK 462 MR 2 66 2 69 4
MAINTSTK 463 MR 2 7 2 7 1
2 71 2 8 1 GAP
P68416B 2D2 MR 2 81 212 4
5654 1 A 2D2 MR 2121 217 5
2171 2225 55 GAP
----------------------------------------------------------------------
D24 I1 339 D24 I1 1A MR 1112 1113
$ALLOC$ C 2 R 1
CAPTMACH 191 MR 1 1 1
CAPTMACH 3 MR 2 3 2
CAPTMACH 4 MR 4 5 2
CAPTMACH 491 MR 6 6 1
P648A7 A 191 MR 7 26 2
P648A7 A 2A2 MR 27 29 3
P648A7 A 2A6 MR 3 32 3
P648A7 A 2B2 MR 33 65 33
P648A7 A 2C2 MR 66 69 4
P648A7 A 2D2 MR 7 78 9
P648A7 A 291 MR 79 93 15
P648A7 A 4 MR 94 113 2
P648A7 A 4 1 MR 114 133 2

P648A7 A 5 MR 134 152 19
P648A7 A 5 1 MR 153 171 19
5648A7 S 191 MR 172 2 1 3
5648A7 S 193 MR 2 2 271 7
5648A7 S 195 MR 272 3 6 35
5648A7 S 2A2 MR 3 7 321 15
5648A7 S 2A6 MR 322 336 15
5648A7 S 2B2 MR 337 4 1 65
5648A7 S 2C2 MR 4 2 411 1
5648A7 S 2D2 MR 412 466 55
5648A7 S 291 MR 467 546 8
5648A7 T 191 MR 547 55 4
5648A7 T 2A2 MR 551 551 1
5648A7 T 2A6 MR 552 552 1
5648A7 T 2B2 MR 553 554 2
5648A7 T 2C2 MR 555 555 1
5648A7 T 2D2 MR 556 559 4
5648A7 T 2 MR 56 561 2
SQLMACH 191 MR 562 581 2
SQLMACH 193 R 582 651 7
SQLMACH 195 RR 652 686 35
SQLMACH 196 MR 687 696 1
SQLMACH 197 MR 697 711 15
SQLMACH 198 MR 712 714 3
SQLMACH 199 MR 715 719 5
SQLMACH 291 MR 72 729 1
SQLMACH 292 MR 73 731 2
SQLMACH 294 MR 732 746 15
SQLMACH 393 MR 747 749 3
SQLMACH 2 MR 75 778 29
SQLMACH 2 1 MR 779 785 7
SQLMACH 2 2 MR 786 85 65
CCDB4MCH 23 R 851 865 15
CCDB4MCH 231 R 866 87 5
CCDB4MCH 232 R 871 875 5
CCDB4MCH 233 R 876 95 75
CCDB4MCH 234 R 951 955 5
CCDB4MCH 235 R 956 1 55 1
CCDB4MCH 191 MR 1 56 1 68 13
CCDB4MCH 195 RR 1 69 1 94 26
CCDB4ADM 191 MR 1 95 1 96 2
CCDB4ADM 291 MR 1 97 1 99 3
11 1112 13 GAP
----------------------------------------------------------------------
D24 L1 339 -2 D24 L1 1A MR 2225 2226
$ALLOC$ D 3 R 1
MAINT 348 MR 1 3 3
DB2ADM 191 MR 4 8 5
RMSMASTR 191 MR 9 9 1
GDQF22 191 MR 1 14 5
MAINT 1341 MR 15 35 21
MAINT 57 MR 36 52 17
MAINT 672 MR 53 55 3
P5654 7 2B2 MR 56 89 34
9 94 5 GAP
ANET 191 MR 95 96 2
CPMON 191 MR 97 1 1 5
CRITIQUE 191 MR 1 2 1 6 5
MSTRSRVO 191 MR 1 7 119 13
MSTRSRVO 19A MR 12 132 13
SPM 191 MR 133 134 2
SPM 1 191 MR 135 136 2
SQLMSTR 191 MR 137 145 9
SQLMSTR 291 MR 146 15 5

SQMMUM1 191 MR 151 155 5
SLMADMIN 2191 MR 156 16 5
TASM 191 MR 161 163 3
SQLMSTR 292 MR 164 168 5
169 17 2 GAP
SMSMASTR 191 MR 171 171 1
P684142K 191 MR 172 176 5
P684142K 29D MR 177 181 5
P684142K 2A2 MR 182 186 5
P684142K 2A6 MR 187 191 5
P684142K 2B2 MR 192 196 5
P684142K 36F MR 197 2 6 1
P684142K 37F MR 2 7 216 1
P684142K 2C2 MR 217 221 5
222 226 5 GAP
P684142K 4 1 MR 227 231 5
P684142K 2D2 MR 232 241 1
MAINT 354 MR 242 253 12
254 353 1 GAP
PLNLP 191 MR 354 358 5
LANPROGS 191 MR 359 363 5
CMEOSI 191 WR 364 372 9
CMEOSI 192 WR 373 375 3
CMEOSI 193 WR 376 378 3
SQLOPER 191 MR 379 383 5
MAINT 674 MR 384 386 3
MAINT 671 MR 387 389 3
MAINT 353 MR 39 39 1
RSCSXCHG 5BF MR 391 393 3
VM3812 192 MR 394 493 1
DFSMS 191 MR 494 525 32
SQMOPER1 191 MR 526 53 5
531 594 64 GAP
AVSVM2 191 MR 595 599 5
6 6 1 2 GAP
MAINT 37E MR 6 2 631 3
MAINT 36E MR 632 661 3
662 674 13 GAP
MAINT 573 MR 675 691 17
MAINT 673 MR 692 697 6
698 713 16 GAP
MAINT 67 MR 714 719 6
MAINT 368 MR 72 762 43
MAINT 4B1 MR 763 792 3
U5648 2 391 MR 793 824 32
MAINT 363 MR 825 9 9 85
91 959 5 GAP
NDCMAINT 191 MR 96 968 9
P5654 7 2A2 MR 969 97 2
EREPSERV 191 MR 971 972 2
P5654 7 2A6 MR 973 974 2
MAINT 365 MR 975 988 14
MAINT 366 MR 989 995 7
MAINT 35 MR 996 1 8 13
MAINT 43 MR 1 9 1 76 68
MAINT 351 MR 1 77 11 6 3
P5654 7 2D2 MR 11 7 1123 17
SQLMSTR 195 MR 1124 1138 15
1139 12 3 65 GAP
P5654 7 191 MR 12 4 12 8 5
P5654 7 2C2 MR 12 9 1213 5
MAINT 367 MR 1214 1217 4
MAINT 333 MR 1218 1222 5
MAINT 571 MR 1223 1231 9

1232 1256 25 GAP
NETVIEW 191 MR 1257 1261 5
CTRTASK 8888 MR 1262 1346 85
MAINT 33 MR 1347 144 94
MAINT 364 MR 1441 1495 55
MAINT 332 MR 1496 1512 17
MAINT 331 MR 1513 1526 14
P5654 7 613 MR 1527 1577 51
1578 1583 6 GAP
MAINT 574 MR 1584 1592 9
MAINT 572 MR 1593 16 1 9
16 2 1611 1 GAP
MAINT 352 MR 1612 1624 13
1625 1629 5 GAP
P5654 7 614 MR 163 168 51
1681 1695 15 GAP
ISPVM 195 MR 1696 17 2 7
17 3 17 5 3 GAP
NPMGRAPH 191 MR 17 6 171 5
NPM 398 MR 1711 1715 5
NPM 1A MR 1716 1753 38
NETVIEW 199 MR 1754 1768 15
NETVIEW 198 MR 1769 18 8 4
NVAS 198 MR 18 9 1823 15
MAINT 334 MR 1824 1965 142
1966 2225 26 GAP
----------------------------------------------------------------------
D24 NS 339 -2 D24 NS 1A MR 2225 2226
$ALLOC$ E 2 R 1
5648C 5A 191 MR 1 5 5
5648C 5A 2 MR 6 255 25
5648C 5A 2A2 MR 256 26 5
5648C 5A 2A6 MR 261 265 5
5648C 5A 2B2 MR 266 27 5
5648C 5A 2C2 MR 271 275 5
5648C 5A 2D2 MR 276 1 25 75
1 26 2225 12 GAP
----------------------------------------------------------------------
D24 O1 339 D24 O1 1A MR 1112 1113
$ALLOC$ C 1 R 1
OFFSERV 191 MR 1 3 3
OFFSERV 25 R 4 13 1
OFFSERV 26 R 14 23 1
OFFSERV 261 R 24 53 3
OFFSERV 4 5 R 54 73 2
OFFSERV 4 6 R 74 93 2
OFFSERV 31 R 94 343 25
CALLADM 191 MR 344 383 4
CALLUP 191 MR 384 393 1
CALLUP 192 MR 394 453 6
CALLUP 193 MR 454 483 3
P684 8F4 191 MR 484 498 15
P684 8F4 377 MR 499 5 8 1
P684 8F4 396 MR 5 9 518 1
P684 8F4 397 MR 519 521 3
P684 8F4 398 MR 522 556 35
SYSADMIN 191 MR 557 576 2
TSTAWAY 191 MR 632 636 5
TSTAWAY 291 MR 637 641 5
TSTAWAYR 191 MR 642 646 5
TSTAWAYR 291 MR 647 651 5
TSTCAL 191 MR 652 654 3

TSTDBM 161 MR 655 662 8
TSTDBM 191 MR 663 677 15
TSTDBM 5FD MR 678 687 1
TSTDBM 5FE MR 688 697 1
TSTDBM 5FF MR 698 7 7 1
TSTMAIL 151 MR 7 8 71 3
TSTMAIL 191 MR 711 717 7
TSTMBX 191 MR 718 732 15
TSTMBX 5FF MR 733 742 1
EWEBADM 394 MR 743 744 2
EWEBADM 395 MR 745 746 2
VMRMAINT 191 MR 747 75 4
VMRMAINT 4 1 MR 756 765 1
VMRMAINT 15E MR 776 777 2
VMRMAINT 161 MR 793 8 2 1
VMWEBSRV 1B MR 8 3 8 7 5
VMRMAINT 192 MR 8 8 832 25
VMRMAINT 4 2 MR 837 838 2
VMWEBSRV 192 MR 839 888 5
EWEBADM 291 MR 889 889 1
VMROPR 1D MR 89 896 7
VMROPR 191 MR 897 9 1 5
VMROPR 192 MR 9 2 9 6 5
EWEBADM 191 MR 9 7 9 7 1
EWEBADM 193 MR 9 8 912 5
EWEBADM 491 MR 913 922 1
EWEB 1 191 MR 923 924 2
OFV 1 191 MR 925 926 2
OFV 2 191 MR 927 928 2
OFV 3 191 MR 929 93 2
EWEBADM 292 MR 931 935 5
EWEBADM 195 MR 936 94 5
EWEBCAL 191 MR 941 942 2
EWEBLOG 191 MR 943 944 2
EWEBLOG 2 1 MR 945 949 5
EWEBADM 194 MR 99 1 69 8
1 7 1112 43 GAP
----------------------------------------------------------------------
D24 P1 339 -2 D24 P1 1A MR 2225 2226
$ALLOC$ D 1 R 1
BOOKMGR 192 MR 1 85 85
86 9 5 GAP
P688194C 2C2 MR 91 92 2
93 93 1 GAP
PPMAINT 192 MR 94 98 5
99 1 3 5 GAP
DFSMS 1D6 MR 1 4 123 2
DFSMS 1C4 MR 124 131 8
132 133 2 GAP
P688197A 2A6 MR 134 138 5
P688197A 2A2 MR 139 143 5
P688194C 2D2 MR 144 148 5
149 149 1 GAP
PLNLP 3 MR 15 158 9
PUBADMIN 395 MR 159 184 26
P688197A 29E MR 185 194 1

P688197A 39E MR 195 2 4 1
P688197A 191 MR 2 5 219 15
P688194C 2B2 MR 22 229 1
P688194C 2A6 MR 23 231 2
P688194C 29E MR 232 236 5
P688194C 491 MR 237 266 3
P688194C 39E MR 267 271 5
P688194C 191 MR 272 286 15
P688197A 2D2 MR 287 291 5
P688197A 2C2 MR 292 296 5
P688197A 2B2 MR 297 3 6 1
P688235A 191 MR 3 7 316 1
P688235A 39E MR 317 326 1
P688235A 2A2 MR 327 331 5
P688235A 29E MR 332 341 1
P688235A 2A6 MR 342 346 5
P688235A 2D2 MR 347 351 5
P688235A 2C2 MR 352 356 5
GRAPHPRT 191 MR 357 358 2
P688194C 2A2 MR 359 36 2
DMQMF 2 191 MR 361 365 5
U5648 2 191 MR 366 366 1
U5648 2 4A2 MR 367 368 2
GDDMPG 4 1 MR 369 378 1
P688235A 2B2 MR 379 388 1
MAINT 375 MR 389 439 51
TASM 192 MR 44 441 2
U5648 2 4A6 MR 442 443 2
PDM4234 191 MR 444 448 5
DFSMS 1B1 MR 449 525 77
ASTEST3 191 MR 526 54 15
541 547 7 GAP
DW37 361 MR 548 581 34
DW37 362 MR 582 632 51
633 635 3 GAP
DPF4 29 191 MR 636 644 9
DPFGRP4 191 MR 645 653 9
DPFGRP3 191 MR 654 662 9
DPF382 191 MR 663 671 9
DFSMS 19D MR 672 68 9
VM3812 191 MR 681 685 5
DEMOSYS 191 MR 686 69 5
PUBADMIN 5F1 MR 691 7 2 12
7 3 7 3 1 GAP
PSFMAINT 192 MR 7 4 754 51
PSFMAINT 191 MR 755 839 85
PSFMAINT 291 MR 84 856 17
PSFMAINT 292 MR 857 873 17
PRTMGR 191 MR 874 895 22
BOOKMGR 191 MR 896 9 3 8
BOOKMGR 291 MR 9 4 916 13
BOOKMGR 3 MR 917 929 13
PUBLIB 191 MR 93 934 5
PUBLIB 193 MR 935 943 9
CRITIQUE 192 MR 944 948 5
PUBADMIN 191 MR 949 957 9
PUBADMIN 192 MR 958 1 21 64
PUBADMIN 195 MR 1 22 1131 11
PUBADMIN 295 MR 1132 1156 25
PSFMAINT 194 MR 1157 1496 34
ASTEST2 191 MR 1497 1511 15
DFSMS 1B5 MR 1512 1588 77
ASTEST1 191 MR 1589 16 3 15
PUBADMIN 5 1 MR 16 4 1624 21

PUBADMIN 495 MR 1625 1645 21
PUBADMIN 4 1 MR 1646 1666 21
PUBADMIN 4 MR 1667 1751 85
P648 63H 191 MR 1752 1841 9
P648 63H 2A2 MR 1842 1857 16
P648 63H 2A6 MR 1858 1873 16
P648 63H 2B2 MR 1874 1923 5
P648 63H 2C2 MR 1924 1928 5
P648 63H 2D2 MR 1929 1983 55
P648 63H 4 MR 1984 2 73 9
P648 63H 4 1 MR 2 74 2163 9
DFSMS 1A2 MR 2164 2171 8
DFSMS 1A4 MR 2172 2179 8
DFSMS 1A6 MR 218 2187 8
DFSMS 1C2 MR 2188 2195 8
2196 2225 3 GAP
----------------------------------------------------------------------
D24 P2 339 -2 D24 P2 1A MR 2225 2226
$ALLOC$ D 2 R 1
PDM3835 191 MR 1 5 5
PDM4224 191 MR 6 1 5
11 29 19 GAP
IHVOPER 191 MR 3 32 3
33 35 3 GAP
PPSERV 191 MR 36 38 3
FTPMAINT 191 MR 39 39 1
FTPMAINT 2 6 MR 4 4 1
FTPMAINT 2 8 MR 41 41 1
DMECF 2 191 MR 42 46 5
47 48 2 GAP
FTPQH 191 MR 49 49 1
PPSERV 3 1 R 5 54 5
PDM423 191 MR 55 59 5
DMECF 1 191 MR 6 64 5
74 1 2 29 GAP
CONFR 1 191 MR 1 3 1 4 2
1 5 1 9 5 GAP
FTPCM 191 MR 11 11 1
PPSERV 3 2 R 111 119 9
FTPDS1 191 MR 12 12 1
FTPDS2 191 MR 121 121 1
FTPFS1 191 MR 122 122 1
FTPFS2 191 MR 123 123 1
PPSERV 3 4 R 124 128 5
P654 33A 39E MR 129 152 24
PDM4 28 191 MR 162 17 9
IHVOPER 193 MR 171 183 13
U5648 2 495 MR 184 2 17
LANDISK 191 MR 2 1 2 1 1
LANDSPRT 191 MR 2 2 2 6 5
SM37 191 MR 2 7 211 5
226 238 13 GAP
U5648 2 491 MR 239 255 17
PDM3816 191 MR 256 264 9
265 272 8 GAP
LANPRINT 191 MR 273 277 5
LANUSER 191 MR 278 282 5
PPSERV 3 3 R 283 291 9
LANDISK 2 MR 292 3 9
PPSERV 31 R 3 1 3 9 9

PDM382 191 MR 31 318 9
PDM3825 191 MR 319 327 9
PDM3827 191 MR 328 336 9
337 344 8 GAP
SM37 211 MR 345 353 9
BATCH 199 MR 354 354 1
SM37 21 MR 355 384 3
385 387 3 GAP
DMQMF 1 191 MR 388 392 5
FTPMAINT 291 MR 393 4 9 17
41 414 5 GAP
SM37 212 MR 415 423 9
APL2V22 291 MR 424 438 15
BASICSV 191 MR 439 455 17
PSFMAINT 193 MR 456 472 17
473 473 1 GAP
SM37 213 MR 474 499 26
U5648 2 4E2 MR 5 516 17
VMASDEMO 191 MR 517 521 5
VMASDEMO 91 MR 522 551 3
U5648 2 4D2 MR 552 568 17
BATCH 191 MR 569 57 2
BATCH 193 MR 571 579 9
BATCH 194 MR 58 581 2
BATCH 195 MR 582 582 1
BATCH1 191 MR 583 586 4
BATCH2 191 MR 587 59 4
SFCM 4 MR 591 61 2
611 622 12 GAP
PDMOPER 191 MR 623 631 9
PPSERV 3 5 R 632 674 43
PPSERV 3 6 R 675 759 85
PPSERV 3 7 R 76 844 85
PPSERV 3 8 R 845 929 85
FTPMAINT 2 2 MR 952 985 34
GDQF22 291 MR 1166 1275 11
1276 1279 4 GAP
PPSERV 3 9 R 128 1449 17
PPSERV 311 R 145 1534 85
FTPMAINT 2 4 MR 1535 1566 32
FTPMAINT 212 MR 1567 1592 26
FTPCM 192 MR 1593 16 2 1
FTPQH 192 MR 16 3 1612 1
VM3812 193 MR 1613 1697 85
APL2SV 191 MR 1698 1723 26
APL2V22 292 MR 1724 1758 35
APL2V22 191 MR 1759 1818 6
LANDISK 192 MR 1819 19 3 85
SFCM 191 MR 19 4 1988 85
P654 9E 191 MR 1989 2 43 55
P654 9E 2A2 MR 2 44 2 51 8
P654 9E 2A6 MR 2 52 2 67 16
P654 9E 2B2 MR 2 68 2 97 3
P654 9E 2C2 MR 2 98 21 2 5
P654 9E 2D2 MR 21 3 2137 35
P654 9E 4 MR 2138 2161 24
P654 9E 4 1 MR 2162 2186 25
2187 2225 39 GAP
----------------------------------------------------------------------
D24 R1 339 -2 D24 R1 1A MR 2225 2226
MAINT 123 RR 2225 2226

SYSDUMP1 123 RR 2225 2226
$ALLOC$ A 1 R 1
$DIRECT$ A 4 R 1 17 17
MAINT 1393 MR 18 18 1
MAINT 1394 MR 19 19 1
MAINT 15B4 MR 2 2 1
$SYSCKP$ A 6 R 21 24 4
$SYSWRM$ A 7 R 25 28 4
$T-DISK$ B 1 R 29 78 5
$SPOOL$ B 1 R 79 193 115
$PAGE$ A 1 R 194 277 84
MAINT CF1 MR 278 294 17
MAINT CF2 MR 295 311 17
MAINT 19 MR 312 418 1 7
MAINT 2C2 MR 419 423 5
MAINT 2D2 MR 424 528 1 5
MAINT 194 MR 529 628 1
MAINT 193 MR 629 761 133
MAINT 19D MR 762 881 12
MAINT 19E MR 882 1 81 2
P748XE4M 11F MR 1 82 1 85 4
P748XE4M 29D MR 1 86 1 94 9
MAINT 191 MR 1 95 1149 55
MAINT 2 1 MR 115 1171 22
MAINT 5E5 MR 1172 118 9
MAINT 319 MR 1181 1189 9
MAINT 376 MR 119 1194 5
MAINT 2A2 MR 1195 12 6
MAINT 2A4 MR 12 1 12 6 6
MAINT 2A6 MR 12 7 1212 6
MAINT 42C4 MR 1213 1217 5
MAINT 2C4 MR 1218 1222 5
MAINT 2A 4 MR 1223 1239 17
124 1292 53 GAP
OPERATNS 191 MR 1293 13 7 15
OPERSYMP 191 MR 13 8 1312 5
OPERATOR 191 MR 1313 1317 5
CMSBATCH 195 MR 1318 1319 2
EREP 191 MR 132 1321 2
AUTOLOG1 191 MR 1322 1322 1
DISKACNT 191 MR 1323 1323 1
OP1 191 MR 1324 1324 1
LGLOPR 191 MR 1325 1325 1
P684 96K 4 1 MR 1326 1334 9
P684 96K 4 6 MR 1335 1342 8
P684 96K 4 3 MR 1343 1345 3
XCHANGE 5BF MR 1346 1348 3
AUTOLOG2 191 MR 1349 1349 1
MAINT 325 MR 135 1399 5
MAINT 31A MR 14 1449 5
MAINT 24 MR 145 1454 5
P684 96K 191 MR 1455 1463 9
P684 96K 5 2 MR 1464 1471 8
GCS 191 MR 1472 1475 4
GCSXA 191 MR 1476 1479 4
TCPMAINT 591 MR 148 15 8 29
TCPMAINT 592 MR 15 9 1564 56
TCPMAINT 198 MR 1565 1573 9
TCPMAINT 191 MR 1574 158 7
P735FALT 491 MR 1581 16 9 29
P735FALT 492 MR 161 1665 56
TCPIP 191 MR 1666 167 5
BOOTPD 191 MR 1671 1672 2
TFTPD 191 MR 1673 1674 2

DHCPD 191 MR 1675 1676 2
FTPSERVE 191 MR 1677 1685 9
SMTP 191 MR 1686 171 25
NAMESRV 191 MR 1711 1712 2
REXECD 191 MR 1713 1714 2
X25IPI 191 MR 1715 1716 2
PORTMAP 191 MR 1717 1718 2
NDBPMGR 191 MR 1719 1719 1
NDBSRV 1 191 MR 172 172 1
SNMPQE 191 MR 1721 1722 2
SNMPD 191 MR 1723 1724 2
NCS 191 MR 1725 1726 2
NCS 195 MR 1727 1728 2
NCSLLBD 191 MR 1729 173 2
NCSGLBD 191 MR 1731 1732 2
ROUTED 191 MR 1733 1734 2
LPSERVE 191 MR 1735 1736 2
SNALNKA 191 MR 1737 1739 3
VMNFS 191 MR 174 1748 9
VMKERB 191 MR 1749 1754 6
ADMSERV 191 MR 1755 1759 5
RSCSDNS 191 MR 176 176 1
UFTD 191 MR 1761 1762 2
TSAFVM 191 MR 1763 1764 2
AVSVM 191 MR 1765 1767 3
P684 96K 2B3 MR 1768 1787 2
2VMVMV2 1 MR 1788 18 2 15
2VMVMV2 3 MR 18 3 1825 23
2VMVMV2 7F MR 1826 183 5
OSASF 2 MR 1831 1845 15
OSASF 4 MR 1846 1868 23
OSASF 191 MR 1869 1878 1
OSAMAINT 191 MR 1879 1888 1
OSAMAINT 7F MR 1889 1893 5
OSADMIN1 191 MR 1894 19 3 1
OSADMIN2 191 MR 19 4 1913 1
OSADMIN3 191 MR 1914 1923 1
P748XE4M 491 MR 1924 1938 15
RACFVM 3 MR 1939 1958 2
RACFVM 3 1 MR 1959 1966 8
RACMAINT 191 MR 1967 1975 9
MAINT 51D RR 1976 2 5 3
2 6 2 11 6 GAP
P748XE4M 492 MR 2 12 2 2 9
DIRMAINT 2DB MR 2 21 2 3 1
DIRMAINT 2DF MR 2 31 2 37 7
DIRMAINT 2AA MR 2 38 2 46 9
DIRMAINT 1DB MR 2 47 2 56 1
2 57 2 63 7 GAP
DIRMAINT 155 MR 2 64 2 7 7
DIRMAINT 1DE MR 2 71 2 79 9
DIRMAINT 1FA MR 2 8 2 88 9
DIRMAINT 15D MR 2 89 2 89 1
DIRMAINT 1AA MR 2 9 2 98 9
DATAMOVE 2AA MR 2 99 21 7 9
DATAMOVE 1FA MR 21 8 2116 9
DATAMOVE 1AA MR 2117 2125 9
DATAMOVE 155 MR 2126 2134 9
DATAMOV2 155 W 2135 2143 9
DATAMOV2 1AA W 2144 2152 9
DATAMOV2 1FA W 2153 2161 9
DATAMOV2 2AA W 2162 217 9
DATAMOV3 155 W 2171 2179 9
DATAMOV3 1AA W 218 2188 9

DATAMOV3 1FA W 2189 2197 9
DATAMOV3 2AA W 2198 22 6 9
P748XE4M 41F MR 22 7 221 4
DIRMAINT 1DF MR 2211 222 1
5767 2P 8881 MR 2221 2225 5
----------------------------------------------------------------------
D24 R2 339 -2 D24 R2 1A MR 2225 2226
$ALLOC$ B 1 R 1
MAINT 3A2 MR 1 6 6
MAINT 3A4 MR 7 12 6
MAINT 3A6 MR 13 18 6
MAINT 3B2 MR 19 149 131
MAINT 3C2 MR 15 154 5
MAINT 3C4 MR 155 163 9
MAINT 3D2 MR 164 371 2 8
MAINT 49 MR 372 478 1 7
MAINT 493 MR 479 611 133
MAINT 5A2 MR 612 617 6
MAINT 5A4 MR 618 623 6
MAINT 5A6 MR 624 629 6
MAINT 5B2 MR 63 638 9
MAINT 5C2 MR 639 643 5
MAINT 5C4 MR 644 648 5
MAINT 5D2 MR 649 678 3
MAINT 5E6 MR 679 687 9
P684 42H 191 MR 688 696 9
P684 42H 2A2 MR 697 698 2
P684 42H 2A6 MR 699 7 2
P684 42H 2B2 MR 7 1 7 8 8
P684 42H 2C2 MR 7 9 71 2
P684 42H 2D2 MR 711 719 9
P684 42H 29D MR 72 721 2
P684 42H 29E MR 722 73 9
P684 96K 2A2 MR 731 732 2
P684 96K 2A6 MR 733 734 2
P684 96K 2B2 MR 735 747 13
748 748 1 GAP
P684 96K 2D2 MR 749 786 38
P684 96K 29D MR 787 794 8
P684 96K 4 MR 795 8 7 13
P684 96K 4 2 MR 8 8 81 3
P688198H 191 MR 811 848 38
P688198H 2A2 MR 849 851 3
P688198H 2A6 MR 852 854 3
P688198H 2B2 MR 855 921 67
P688198H 2C2 MR 922 926 5
927 1 28 1 2 GAP
P748XE4M 2C2 MR 1 29 1 29 1
P684 96K 2C2 MR 1 3 1 39 1
1 4 1 41 2 GAP
P748XE4M 191 MR 1 42 1 5 9
P748XE4M 29E MR 1 51 1 51 1
P748XE4M 2A2 MR 1 52 1 55 4
P748XE4M 2A6 MR 1 56 1 59 4
P748XE4M 2B1 MR 1 6 1 67 8
P748XE4M 2B2 MR 1 68 1 8 13
P748XE4M 2D2 MR 1 81 114 6
MAINT 4 MR 1141 1215 75
MAINT 4 9 MR 1216 1399 184
MAINT 6A2 MR 14 14 2 3
MAINT 6A4 MR 14 3 14 5 3
MAINT 6A6 MR 14 6 14 8 3
MAINT 6B2 MR 14 9 1417 9
MAINT 6C2 MR 1418 142 3

MAINT 6C4 MR 1421 1423 3
MAINT 6D2 MR 1424 1432 9
MAINT 7A2 MR 1433 1435 3
MAINT 7A4 MR 1436 1438 3
MAINT 7A6 MR 1439 1441 3
MAINT 7B2 MR 1442 145 9
MAINT 7C2 MR 1451 1453 3
MAINT 7C4 MR 1454 1456 3
MAINT 7D2 MR 1457 1465 9
P735FALT 2A2 MR 1466 149 25
P735FALT 2A6 MR 1491 1515 25
P735FALT 2B2 MR 1516 1577 62
P735FALT 2B3 MR 1578 1579 2
P735FALT 2C4 MR 158 1584 5
P735FALT 395 MR 1585 1586 2
2VMVMV2 191 MR 1587 1596 1
2VMVMV2 2A2 MR 1597 16 6 1
2VMVMV2 2A6 MR 16 7 1616 1
2VMVMV2 2B2 MR 1617 1631 15
2VMVMV2 2C2 MR 1632 1635 4
2VMVMV2 2D2 MR 1636 1715 8
5654A 9A 191 MR 1716 1716 1
5654A 9A 2A2 MR 1717 1718 2
5654A 9A 2A6 MR 1719 172 2
5654A 9A 2B2 MR 1721 1745 25
5654A 9A 2D2 MR 1746 1835 9
5654A 9A 4E2 MR 1836 188 45
5654A 9A 491 MR 1881 1925 45
P688198H 2D2 MR 1926 1985 6
P688198H 29E MR 1986 2 45 6
2 46 2225 18 GAP
----------------------------------------------------------------------
D24 SP 339 -2 D24 SP 1A MR 2225 2226
$ALLOC$ A 3 R 1
1 2225 2225 GAP
----------------------------------------------------------------------
D24 S1 339 D24 S1 1A MR 1112 1113
$ALLOC$ E 1 R 1
MAINT 4 5 MR 1 1 2 1 2
P684 96K 5 5 MR 1 3 11 8
MAINT 4 1 MR 111 212 1 2
P684 96K 5 1 MR 213 22 8
MAINT 393 MR 221 3 8
MAINT 394 MR 3 1 484 184
MAINT 5B4 MR 485 5 8 24
P735FALT 2D2 MR 5 9 598 9
DFSMS 1B2 MR 599 628 3
629 1112 484 GAP
----------------------------------------------------------------------
ECAM 1 339 $SUBSYS$ 48FF MW 1
1 1112 1112 GAP
----------------------------------------------------------------------
ECAM 2 339 $SUBSYS$ 48FE MW 1
1 1112 1112 GAP
----------------------------------------------------------------------
IF4 96 339 -2 LABEL XXXX XX 1
MAINT 4 96 RR 1 2225 2225
----------------------------------------------------------------------
RVTUP2 339 -2 LABEL XXXX XX 1
1 475 475 GAP
ADAS51 A 2C2 MR 476 479 4
ASMON51 191 MR 48 489 1
ADAS51 A 293 MR 49 499 1
ADAS51 A 191 MR 5 519 2

ADAS51 A 2A2 MR 52 522 3
ADAS51 A 2A6 MR 523 525 3
526 569 44 GAP
ADAS51 A 294 MR 57 669 1
ADAS51 A 2B2 MR 67 814 145
ADAS51 A 396 MR 815 849 35
ADAS51 A 296 MR 85 889 4
ADAS51 A 392 MR 89 929 4
ADAS51 A 391 MR 93 1 24 95
1 25 1 69 45 GAP
ADAS51 A 292 MR 1 7 1129 6
ADAS51 A 291 MR 113 1224 95
ADAS51 A 2D2 MR 1225 1264 4
1265 2225 961 GAP
----------------------------------------------------------------------
RVXUI1 339 -2 LABEL XXXX XX 1
1 1446 1446 GAP
APE211 191 MR 1447 1456 1
1457 2225 769 GAP
----------------------------------------------------------------------
T22 P2 339 LABEL XXXX XX 1
1 12 12 GAP
APE211 4 1 MR 13 29 17
3 1112 1 83 GAP
----------------------------------------------------------------------

Appendix B. Standard Device Addresses for the IBM Center
The statements are now on MAINT CF1 in the SYSTEM CONFIG file:
/ /
/ SAMPLE SYSTEM CONFIG FILE /
/ /
/ /
/ Rules of the config file: /
/ /
/ 1) REXX style comments are permitted /
/ /
/ 2) Configuration commands can be continued to next line via a /
/ trailing comma on the previous line /
/ /
/ 3) IMBED statements can be used to imbed other files that /
/ reside on the PARMDISK into the configuration file /
/ /
/ 4) The IMBED record is of the format: IMBED fn ft /
/ /
/ 5) Tolerance record can be used to signal whether CP should /
/ tolerate errors in some sections of the CONFIG file or not; /
/ default is to have tolerance on (that is to tolerate errors) /
/ /
/ 6) Format of tolerance is: TOLERATE_CONFIG_ERRors ON | OFF“ /
/ /
/ 7) A prefix of "systemid:" on the front of any statement limits /
/ the scope of the statement to apply to a specific node or /
/ a collection of nodes defined on a previous EQUATE statement. /
/ /
/ /
/ /
/ /
/ /
/ Content of this file overrides anything specified in HCPSYS/HCPRIO /
/ /
/ /
/ /
/ Checkpoint and Warmstart Information /
/ /
System_Residence,
Checkpoint Volid D24 R1 From CYL 21 For 4 ,
Warmstart Volid D24 R1 From CYL 25 For 4
/ /
/ Timezone Definitions /
/ /
System_Dateformat Fulldate
Timezone_Definition CDT West 5. .

Timezone_Definition CST West 6. .
Timezone_boundary on 1998- 4- 5 at 2: : to CDT

Timezone_boundary on 1998-1 -25 at 2: : to CST
Timezone_boundary on 1999- 4- 4 at 2: : to CDT

Timezone_boundary on 1999-1 -31 at 2: : to CST
Timezone_boundary on 2 - 4- 2 at 2: : to CDT
Timezone_boundary on 2 -1 -29 at 2: : to CST
Appendix B. Standard Device Addresses for the IBM Center 187

Timezone_boundary on 2 1- 4- 1 at 2: : to CDT
Timezone_boundary on 2 1-1 -28 at 2: : to CST
/ /
/ CP_Owned Volume Statements /
/ /
CP_Owned Slot 1 D24 R1

CP_Owned Slot 2 D24 B1
CP_Owned Slot 3 RESERVED
/ /
/ Sample CP_Owned Volume Statements /
/ These statements are not active at the present time. They are /
/ examples, and can be activated by removing the comment delimeters /
/ /
/ CP_Owned Slot 1 DRUM 1 /
/ CP_Owned Slot 17 PAG 1 /
/ CP_Owned Slot 24 SPL 1 /
/ /
/ System_Identifier Information /
/ /
System_Identifier_Default DEMOXX
/ /
/ User_Volume_List /
/ These statements are not active at the present time. They are /
/ examples, and can be activated by removing the comment delimeters /
/ /
/ User_Volume_List USRP 1 /

/ Syatem Packs for VM/ESA 2.4. /
User_Volume_List D24 R2
User_Volume_List D24 B2
User_Volume_List D24 I1
User_Volume_List D24 O1
User_Volume_List D24 NS
User_Volume_List D24 L1
User_Volume_List D24 S1
User_Volume_List D24 P1
User_Volume_List D24 P2
User_Volume_List D24 SP
/ System Packs used for RAMAC DASD /
User_Volume_List ECAM 1
User_Volume_List ECAM 2
User_Volume_List IF4 96
/ /
/ Set Privilege Classes /
/ /
Priv_Classes ,
Operator A ,
IOCP_Read CE ,
IOCP_Write C ,
HW_Service F ,
User_Default G
/ /
/ System Userids /
/ /
System_Userids ,
Operator OPERATOR disconnect ,
Account DISKACNT ,
Dump OPERATNS ,
Erep EREP
/ /
/ Features Statement /
/ /
Features ,
Enable , / Enable the following features /
Set_Privclass , / Disallow SET PRIVCLASS command /
Clear_TDisk , / Don't clear TDisks at IPL time /
Disable , / Disable the following features /
LogMsg_From_File , / No LOGMSG from SYSTEM LOGMSG /
Auto_Warm_IPL , / Prompt at IPL always /
Retrieve , / Retrieve options /
Default 8 , / Default.... default is 7 /
Maximum 64 , / Maximum.... default is 7 /
MaxUsers noLimit , / No limit on number of users /
Passwords_on_Cmds , / What commands allow passwords? /
Autolog yes , / ... AUTOLOG does /
Link no , / ... LINK does /
Logon no / ... and LOGON does, too /

/ /
/ The following RDEV statements are examples. They are NOT /
/ currently active. They have been commented out. /
/ /
/ Rdevice 12 Type Reader, /

/ Class 6 /
/ Rdevice 13 Type Punch, /
/ Classes 6 , /
/ Form PUNCH /
/ Rdevice 4 - 4F Type Bsc_Adapter /
/ Rdevice 5 - 5F Type Bsc_Adapter /
/ Rdevice AF Type Impact_Printer /
/ Rdevice AF3 Type Impact_Printer, /
/ Classes ACT /
/ Rdevice 191 Type 38 , /
/ Model 3 /
Rdevice 41- 48 Type Bsc_Adapter

Rdevice 6D- 6F Type Bsc_Adapter
Rdevice 2F Type Impact_Printer,

Universal_Charset Yes,
AFP No,
Classes H
Rdevice 1E Type Impact_Printer,

Universal_Charset Yes,
Classes H
Rdevice 44 - 45F Type 3279 Mod 3

Rdevice 46 - 469 Type 3279 Mod 3
Rdevice 51 - 517 Type CTCA
Rdevice 5C - 5DF Type CTCA
Rdevice 5E - 5FF Type CTCA
Rdevice A2 - A3F Type CTCA
Rdevice A4 - A5F Type CTCA
Rdevice 38 - 38F Type 342 ,

Model 8,
Dual_Density Yes
Rdevice B - B F Type AFP

Rdevice 18C -18DF Type UNSUPPORTED Devclass PRINTER
/ /
/ Status of Devices /
/ /
Devices ,
Online_at_IPL -FFFF,
Sensed -FFFF
/ /
/ Console Definitions /
/ /
Operator_Consoles 444 A44 463 46 462 44B E21

Emergency_Message_Consoles 444 A44 463 46 462 44B E21

/ /
/ Special characters for system set here /
/ /
Character_Defaults ,
Char_Delete '@' , / System default ... @ /
Escape '"' , / System default ... " /
Line_Delete '¢' , / Default is cent sign /
Line_End '#' , / System default ... # /
Tab '“' / System default ... “ /
/ /
/ System Forms /
/ /
Form_Default ,
Console STANDARD, / Find out if these are the defaults /
Printer STANDARD,
Punch STANDARD,
Reader STANDARD
/ /
/ Initial Parmdisk Access /
/ /
CP_Access MAINT CF1 A

CP_Access MAINT CF2 B
/ /
/ Logo_Config /
/ /
Logo_Config LOGO CONFIG

/ /
/ PRODUCT ENABLE/DISABLE INFORMATION /
/ /
PRODUCT PRODID 5684 96K STATE ENABLED DESCRIPTION ' / / . : : .$BASEDDR R

SCS Networking Version 3 Release 2 Modification '
PRODUCT PRODID 5735FALT STATE ENABLED DESCRIPTION ' / / . : : .$BASEDDR T

CP/IP LEVEL 32 - TCP/IP FEATURE (BASE)'
PRODUCT PRODID 5735NFST STATE ENABLED DESCRIPTION ' / / . : : .$BASEDDR T

CP/IP LEVEL 32 - TCP/IP NFS FEATURE (BASE)'
PRODUCT PRODID 5654A 9A STATE ENABLED DESCRIPTION ' 8/3 /99.15: 8: .MAINT AD
STAR Distributed Storage Manager for VM 3.1.2'

Appendix C. DB2/VM Database Machines
The next four terms are used in the following discussion of multiple production mini-
disks:
Primary Database Machine is a database machine that owns a production
minidisk. For example, the DB2MACH machine,
which was defined during installation, is a
primary database machine. Other primary data-
base machines on this system are CCDB1MCH,
and CCDB4MCH.
Secondary Database Machine is a database machine that does not own a
production minidisk. The VM directory entries
for theses machines do not contain an MDISK
statement for the production minidisk. Instead,
they contain a LINK statement.
Primary Production Minidisk is the production minidisk that is owned by the
DB2MACH database machine. It is the original
production minidisk in your installation (Cus-
tomer Centers should not use, change or refer-
ence this minidisk).
Secondary Production Minidisk contains a copy of the DB2/VM supplied files on
the original production minidisk. A secondary
production minidisk is owned by a primary data-
base machine other than the DB2MACH
machine. (The DB2MACH machine is a primary
database machine that owns the primary pro-
duction minidisk).
The SQLMACH and CCDB4MCH machines are primary database machines because
they each own a production minidisk defined by an MDISK control statement. The
CCDB1MCH and CCDB4MCH machines also have a VM directory LINK entry for the
SQLMACH machine's service minidisk. The service minidisk contains all IBM-sup-
plied files, including those that are necessary for a production minidisk. The sec-
ondary production minidisk is initialized by copying all appropriate IBM-supplied files
from the service minidisk to it. DB2/VM supplies an exec called ARISPDFC that
was used to copy the files for secondary production minidisk on the primary data-
base machine CCDB4MCH.
The DB2/VM supplied files must be the same on all production minidisk at your
installation. If you apply service to one production minidisk, you must apply the
service to all production minidisk.
Appendix C. DB2/VM Database Machines 193

_____________
| SQLMACH | ____________________________ ____________ _______________
| Virtual |------| 195 Production Disk R/W | | CCDB4MCH | | DB2/VM |
| Machine |___ | for DBN= NEW33 | | Virtual | <========== IUCV ========> | User Machine|
|__v________| | |__________________________| | Machine | or | |
| |_____ _____________________________ |__________| APPC/VM |_______v_____|
| |----| 198 RxSQL Production R/W | RxSQL | | | | | | __________________
| | |___________________________| feature | | | | | |---| 191 Work Disk |
| | _____________________________ | | | | | |________________|
| |----| 199 RxSQL Service R W | M | | | | |
| |___________________________| D | | | | ________________________ | L
| I | | | L------| 191 Work Disk | | I
| S | | | |______________________| | N
| ________________________ SQL/DS Distribution disk K | | | | K
L------| 193 Service Disk | <== Linked to by all other | | | ________________________ |
|_____v________________| Primary Data Base machines | | L--------| 195 Production Disk |-----|
| | | |______________________| ____________
<ARISPDFC> | | | | SQLMACH |
_______________________| | | ________________________ MDISK Owner=> | Virtual |
| Read/Only Link | L----------| 193 Service Disk |---------------->| Machine |
| ____________ | Link=> |______________________| ARISPDFC |__________|
| | CCDB4MCH | |
|______| DBM | | _______________________________________________________
| |_____v____| ____________________________ L------------| | DBN= CCDB1 | Size | Stor | % | Mdisk |
| |________| 195 Production Disk R/W | L------------| CUU | description | cyl | Pool | use | Label |
| | For DBN = CCDB4 | | --- | --------------- | ---- | ---- | --- | ------- |
| |__________________________| | 2 | Directory Disk | 1 | -- | - | BDISK |
V | 2 1 | Log Disk 1 | 5 | -- | - | LOGDSK1 |
to | 2 2 | Data Disk 1 | 4 | 1 | 73% | DDSK1 |
local | 2 3 | Data Disk 2 | 5 | 2 | % | DDSK2 |
DBM's | 2 4 | Data Disk 3 | 1 | 3 | 2% | DDSK3 |
| 2 5 | Data Disk 4 | 3 | 1 | % | DDSK4 |
| 2 6 | Data Disk 5 | 2 | 3 | % | DDSK5 |
|_____|_________________|______|______|_____|_________|
Storage pool 1 has 2 dbextents and is 41% used
Storage pool 3 has 2 dbextents and is % used
A view of base DB2/VM Application Servers and

Machines
A view of the DB2/VM Database Machine

CCDB4MCH with DB2/VM Application Server
CCDB4.

Appendix D. Tips and Techniques
Creating the Stand-Alone Tape

The CMS file IPL ICKDSF on your product disk is the stand-alone version of the
ICKDSF. The stand-alone ICKDSF can be executed by punching the IPL ICKDSF to
a virtual card reader and IPLing the file from the virtual reader. The stand-alone
ICKDSF can also be copied to a tape with which you may also IPL.
The following is a sample exec you can use to copy the stand-alone program code
to an unlabeled tape:
THIS EXEC COPIES THE STAND-ALONE DEVICE SUPPORT FACILITIES
FROM CMS FILE 'ICKSADSF COREIMAG' TO AN IPL-ABLE TAPE.
THE TAPE MUST BE ATTACHED AS VIRTUAL ADDRESS '181'.
CP REWIND 181
&IF &RETCODE NE &GOTO -NOTAPE
FILEDEF INMOVE DISK IPL ICKDSF S (LRECL 8 RECFM F
FILEDEF OUTMOVE TAP1 (LRECL 8 RECFM F BLOCK 8
MOVEFILE
&IF &RETCODE NE &GOTO -BADMOVE
&BEGTYPE
STAND-ALONE ICKDSF SUCCESSFULLY GENERATED
&END
&EXIT
-BADMOVE
&TYPE ERROR LOADING CMS FILE TO TAPE
&EXIT 1
-NOTAPE
&TYPE TAPE 181 NOT ATTACHED OR NOT READY
&EXIT 2
Listing a Source
To list your source, complete the following steps:
1. To logon to MAINT, Enter:
----> l maint
2. Enter your password for MAINT
3. To access the minidisks/directories for the component you are interested in (for
example: CP, CMS, GCS), Enter:
Note: You must have restored D240R2 and attached it to the system.
----> VMFSETUP ESA CP
----> CTRXEDIT HCPxxx
----> TOP
----> PUT * HCPxxx assemble a

where xxx is sys for HCPSYS, rio for HCPRIO, or box for HCPBOX.
Appendix D. Tips and Techniques 195

Saving a Trip to the Master Console
If you need to re-IPL the real system, you can do it without a trip back to the master
console by logging on from a local non-SNA device. The SHUTDOWN command
now enables additional parameters, which can be used to control the re-IPL of the
system, including specifying the address you want the master console to come up
on.
To re-IPL the real system, complete the following steps:

1. To find out if your current virtual console is a local device and what its address
is, Enter:
----> q v con
You will see something like the following:
CONS 9 ON GRAF 473 TERM START
9 CL T NOCONT NOHOLD COPY 1 READY FORM STANDARD
9 TO MAINT RDR DIST SYSPROG FLASHC DEST OFF
9 FLASH CHAR MDFY FCB
9 3215 NOEOF OPEN 1216 NOKEEP NOMSG NONAME
9 SUBCHANNEL =
If the response shows that you are on a GRAF device, then you may use this
procedure. Make a note of the address shown. If the response shows that you
are on a LDEV device or a SNA network ID, then you may not use this proce-
dure.
2. Using the address obtained from the query, start the shutdown procedure spec-
ifying your address to come up as the master console by Entering:
----> shutdown reipl iplparms cons=473

After the usual delay, your console comes up as the master console with the
OPERATOR user ID logged on. The DEMOpkg System is distributed with “Fea-
tures Enable Auto_Warm_IPL” in the SYSTEM CONFIG file, so you will not be
prompted for type of start and TOD setting.
3. To change any of the conditions of the re-IPL, you can specify to be prompted
for such input by Entering:
----> shutdown reipl iplparms cons=473 prompt

4. To finish the IPL process, reply manually to each of the prompts

Finding Maintenance User IDs
The FINDUSER exec is provided by Demonstration Delivery & Support to help find
the product number and maintenance user IDs of installed products on the VM/ESA
2.4.0 DEMOpkg System.
For example:
To find user IDs for VTAM, Enter:
----> finduser vtam
USERID Product ID Description

-----------------------------------------------------
5654 1 A 5654 1 VTAM
To find user IDs for VM, Enter:
----> finduser vm
USERID Product ID Description

-----------------------------------------------------
. 5654 3 VM/ESA
ISPVM 5684 43 ISPF
P5654 7 Automated Network Operations/VM
P6841 E 56841 E Passthru Virtual Machine (PVM)
P684142A 5699142 LANRES/VM
P68416A 5684168 GDDM
2VMVMG1 568411215 OpenEdition DCE
2VMVMY1 5654 3 GUI
2VMVMZ1 568411214 OpenEdition Shell and Utilities
Using the USERID Directory

The following are some helpful hints and tips for using any USERID directory.
Note: These commands and execs are not part of DirMaint. They are additional
extensions to the VMTOOLS package, QDIR.
To display any user ID or profile in full screen mode, Enter:
----> qdir userid d

To display the minidisks of any user ID in full-screen mode, Enter one of the
following:
----> qdir userid (m li
----> qdir userid (m

To get a user ID and then place it on the 191 or A-Disk, Enter:
----> qdirw userid
Appendix D. Tips and Techniques 197

To display the password, machine size, classes and more, Enter:
----> qdirp userid

To display an index of the complete directory, Enter:
----> fdirm
From the directory listing, Xedit can be invoked to show the directory entries.
The directory can then be filed on your A-Disk.
Performance Considerations
One suggestion for the possible performance enhancement to the VM/ESA
DEMOpkg System would be to logoff any server virtual machine associated with a
product or demonstration that is not currently needed. The following are suggested
candidates:
If TCP/IP is not being used:
FTPSERVE RSLAVE3
PORTMAP SMTP
REXECD SNALNKA
RSLAVE1 TCPIP
RSLAVE2 VMNSF
If DFSMS is not being used:

DGTMASTR
SMSMASTR
If CVIEW is not being used:

CVIEW
If GFIS is not being used:

GEODBMCH
All of these server virtual machines, along with many others, are autologged on
when the system is IPLed. To shutdown any one of them, simply logon to either
MAINT, ADMIN, or OP1 and force them off. For example, to force off the TCPIP
virtual machine, Enter:
----> force tcpip
If one of these IDs has been logged off, but you want to use it, logon to MAINT,
ADMIN, or OP1 and autolog it by Entering:
----> xautolog tcpip

Appendix E. Logging On VMUSERnn
Fifteen general purpose VM user IDs are provided to users that do not have a spe-
cific demonstration VM user ID. The user IDs are VMUSER01 thru VMUSER10. As
shipped, the user IDs display a VMLINK Category Selection menu that enables you
to select the products to be used. DEMODOC may also be selected to print demon-
stration or system documentation. You can also perform an “AutoLink” to selected
products the next time the user ID is evoked. The user IDs are authorized to use
OfficeVision and SQL.
The USER user IDs will be provided on the next release of VM/ESA.
Executing the Product Code

To execute the product code, complete the following steps:
1. Select a category from the VMLINK Category Selection menu by choosing the
appropriate number
For example, if number 12 for OFFICE is selected, the next menu will permit
you to choose any of the OFFICE category products.
2. To link to the product, move the cursor to the appropriate line and press PF5
3. To leave the VMLINK Category Selection menu, press PF3 twice
You are now ready to invoke the product!
Customizing the User ID for a Specific Demonstration

To customize the user ID, complete the following steps:
1. Select a category from the VMLINK Category Selection menu by choosing the
appropriate number
For example, if number 12 for OFFICE is selected, the next menu will permit
you to choose any of the OFFICE category products.
2. To autolink to the product, move the cursor to the appropriate line and then
press PF9
3. To leave the VMLINK Category Selection menus, press PF3 twice
You are now ready to invoke the product!
Appendix E. Logging On VMUSERnn 199

VMLINK Menus
1. Logon to DEMOpkg by Entering your userid and password:
----> USERnn
----> PPPPPPPP
where nn is a value from 01 to 10.
Once a day the DEMOpkg logo will be displayed by the DISPLOGO exec, after
which the following panel is displayed:
DEMOpkg: -VMLINK- Category Selection Menu
Number Category Description

1) DEMODOC VM/ESA 2.4. DEMOpkg System Documentation.
2) BOOK BookManager Build and Read.
3) COMM Communications products.
4) DATABASE Database management products.
5) DECISION Decision Support products.
6) DEMO Product demo access using VMLINK.
7) DEMOPRT Disks related to DD & S documentation.
8) LANGUAGES Available interpreters and compilers.
9) OFFICE OfficeVision and related products.
1 ) PERFORM VM Performance Facilities.
11) PRINT PSF/VM and AFP Family products.
12) PRODBOOK Program Product manuals.
13) PUBLISH VM Publishing and Publishing products.
14) SYSTEM Disks related to system support.
15) UTILITY Miscellaneous useful stuff.
Enter the number of a specific category. ______

Or press enter with no number to see all VMLINK entries
F12=Cancel
This panel allows the user to reduce the number of screens displayed before
accessing or invoking a product, and shows the different categories for the pro-
ducts. Some products may be in more than one category.

2. Select option 6 (DEMO Product demo access using VMLINK):

Enter the number of a specific category. __6___

F12=Cancel
3. Press Enter
The VMLINK selection screen will appear:
VMUSER 3 VMLINK A V 26 Trunc=26 Size=2 Line=1 Col=1 Alt=

Cmd Nickname Vdev Fm Ext Lm Category Description
GDDMPG = = / DEMO GDDM/VM Ver 3.1.1 Presentation
DMQMF = = / DEMO Invoke Query Management Facility
DMLAA = = / DEMO Invoke LangAcc NLE(set VSTOR=2 M
DMDXT = = / DEMO Invoke DXT Product Disk V.2.5.
DMAPE DIR O / DEMO Invoke APE
DMSQM = = / DEMO Invoke SQL Master/VM
DMSQLU = = / DEMO Invoke SQL Master/VM w/alt vmid
DMDBE = = / DEMO Invoke DBEDIT Product Disk
DMCSPAD = = / DEMO Invoke CSP/AD with Sample MSL's
DMCSPAD2 = = / DEMO Invoke CSP/AD
DMCSPAE = = / DEMO Invoke CSP/AE Utilities
DMADC = = / DEMO Invoke AD/Cycle WorkBench/VM Dmo
DMADCWB2 = = / DEMO Invoke AD/Cycle WorkBench/VM Dmo
DMQMF311 = = / DEMO Invoke Query Management Facility
DML123M = = / DEMO Demo Accss to LOTUS 123/M Rel2.1
DMASV4 = = / DEMO invoke VMAS Ver.4.1.
DMAS = = / DEMO invoke VMAS Ver.4.1.
DMAST = = / DEMO invoke VMAS Ver.4.1.
DMICE = = / DEMO invoke vmas ice
VMLINK Disk selection for category DECISION
====>
1=Help 2=Filelist 3=Return 4=SortName 5=Select 6=Alt View

7=Backward 8=Forward 9=AutoLink 1 =Detach 11=Remove/A 12=Category
This screen reflects the new options for nicknames, in alphabetical order, and a
full description line displayed on the right.
Appendix E. Logging On VMUSERnn 201

4. Use your cursor to select a nickname and press a PF key to implement the
action
Help for VMLINK is available by pressing PF1 .
Once you have finished running your application or using VMLINK, this screen
will be redisplayed:

Enter the number of a specific category. ______

F12=Cancel
5. You can complete another action or exit to CMS

Exit is accomplished by pressing PF12 or PF3 .
The following message is displayed as you leave CTRMENU:
Quitting CTRMENU at your request.

Ready; T= .94/1. 8 13:55:14
Running DEMOPKG

Appendix F. Summary of DirMaint Syntax Commands
HELP ADVHCMD
DIRM FOR mach Get

DIRM FOR mach REPlace
DIRM FOR mach SETpw xxxxxxxx
DIRM SEND fn ft
DIRM FILE fn ft
AMD AMD
DIRM FOR mach AMD vaddr 339 AUTOV size volid mode BLK 4K LAB xxxxxx PW read write mwri
CMD 2K
1K
DIRM FOR mach MMD FROM user vaddr TO user2 vaddr
DIRM FOR mach DMD vaddr - -

Clean KEEP
Noclean
DIRM STAT Datamove All

Locked Both
Nolog
Workunit All
nnnnnnnn
Fail
DIRM Query Datamove

Unassigned
DVHLevel
Workunit nnnnnnnn
DIRM WORKUNIT nnnnnnnn Cancel

Retry
DELETE
Wakeup
All DELETE
DIRM ENable
DIRM ON Immed
(Fix up an userid directory entry)

=====> neatuser fname
Appendix F. Summary of DirMaint Syntax Commands 203

Appendix G. Shared File System (SFS)
SFS Command Summary
GRANT authority for a DIRC space:

GRANT AUThority dirid to user (dirw
Who are the users in a SFS space?

Q ENROLL USEr
Q ENROLL ADMinistration
Q AUTHerization dirname
Enroll a user into a SFS space:

ENRoll USEr spacename (BLOcks number
ENRoll PUBlic spacename
ENRoll ADMinistrator userid spacename
Add more space to a SFS userid:

FILESERV MINIDISK serverid
Give a user more space of a SFS space:

MODIfy USEr +blocks FOR spacename
Erase a DIR:
ERASE dirname
Create a DIR:
CREate DIRectory dirname
Create a DIRC:
CREate DIRectory dirname (DIRControl
Review Space Information:

Query FILEPOOL STOrage
Query FILEPOOL MINidisk
Query LIMITS ALL
Query FILEPOOL REPort
Set the default filepool:

SET FILEPOOL spacename:
Current filepool information:

Query FILEPOOL CURrent
Query FILEPOOL PRImary
Appendix G. Shared File System (SFS) 205

Adding Space to an Existing SFS
To add space:
1. Review the servers minidisks to identify the next minidisk address to add:
----> qdir vmservs d

2. Add a minidisk to an existing and running SFS server:
----> dirm for vmservs amd 306 3390 autov 100 d230b1 wr lab sys306
pw rdata wdata
306 is the next mdisk number in order.
3. Link to the servers 191 mdisk:
a. Enter: link vmservs 191 1 rr
b. Enter password
c. Enter: acc 1 c
4. Review the poolid POOLDEF file:
a. Enter: x vmsys pooldef c
b. Enter: acc 193 z
5. Create a control file on the administrators A-disk:
a. Enter: x vmsysadd dsk0528 a
i DDNAME=MDK 3 VDEV=3 6 GROUP=2
(MDK 3 came from x vmsys pooldef file.)
(3 6 came from the minidisk you added.)
Note the next MDKnnnnnn sequence number.
b. Enter: filepool minidisk vmservs vmsysadd dsk0528 a vmsys
c. Enter: 1
d. Enter: wdata
Password is from the DIRM AMD command.
6. Issue the FILEPOOL MINIDISK command:
----> q filepool mini

Appendix H. QDIR PACKAGE
The following are helpful tips in dealing with any userid directory. These execs
were provided by extensions to VMTOOLS and the tools package of QDIR:
Display any userid or profile in full screen mode:
----> qdir userid d

Display the minidisks of any userid in full screen mode:
----> qdir userid (m li

or
----> qdir userid (m

Get the userid and place it on the 191 or A mdisk:
----> qdirw userid

Display on the password, machine size, classes, and more:
----> qdirp userid

Display an index of the complete directory:
----> fdirm
Invoke XEDIT to show the directory entries and then file the directory on your
A-disk.
Appendix H. QDIR PACKAGE 207

Appendix I. VM/ESA DEMOpkg Support
We strive to provide a quality DEMOpkg System for our customers. We provide
fast, friendly support. If you experience any problems or have questions, review our
FAQs or contact the DEMOpkg help desk.
VM/ESA DEMOpkg FAQs

Access the FAQs database to view common problems and answers:
1. Access the DEMOcentral Web site: http://w3.demopkg.ibm.com
2. Select DEMOpkg
3. Select Support
4. Select FAQ
DEMOpkg Help Desk

Before contacting DEMOpkg Support, please review our FAQs. When calling or
sending an e-mail about a particular service request, have following information
ready:
Name
Phone Number
E-mail Address
Application or Demo
Brief Description of the Problem
Report problems to DEMOpkg Support:

Select Feedback from our DEMOpkg Support web page
Call T/L 542-3966 or outside (972) 280-3966
Remote Demonstrations
Demonstration Delivery & Support provides several DEMOnet host systems, gate-
ways and servers for doing remote demonstrations. For more information, visit our
DEMOnet Web site, or call the DEMOnet help desk at tie line 542-3966 or outside
(972) 280-3966.
Appendix I. VM/ESA DEMOpkg Support 209

IBM
Printed in U.S.A.

Demonstration Delivery & Support Vm/Esa 2.4.0 Demopkg System Reference Guide Release 4Q99

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Demonstration Delivery & Support Vm/Esa 2.4.0 Demopkg System Reference Guide Release 4Q99

Uploaded by

Copyright:

Available Formats

Demonstration Delivery & Support

VM/ESA 2.4.0 DEMOpkg System Reference Guide

2 VM/ESA 2.4.0 Reference Guide

Document Number VM4Q99R

IBM Software Group

1507 LBJ Freeway

ii VM/ESA 2.4.0 Reference Guide

Introduction to VM/ESA 2.4.0 DEMOpkg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

VM/ESA 2.4.0 DEMOpkg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

VM/ESA CMOS Product List by Market Segment . . . . . . . . . . . . . . . . . 5

VM/ESA P/R390 Product List by Market Segment . . . . . . . . . . . . . . . 11

System Component Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Accessing Common Minidisks . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

DirMaint Version 1.5.0 Customization . . . . . . . . . . . . . . . . . . . . . . . 19

DirMaint Directory Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . 25

SYSTEM NETID File Customization . . . . . . . . . . . . . . . . . . . . . . . . 77

VM/ESA 2.4.0 DEMOpkg System Customization . . . . . . . . . . . . . . . . 81

iv VM/ESA 2.4.0 Reference Guide

IPLing the VM/ESA 2.4.0 DEMOpkg System (Normally) . . . . . . . . . . . . 87

IPLing the VM/ESA 2.4.0 DEMOpkg (Optionally) . . . . . . . . . . . . . . . . 91

Changing Logon Passwords (Non-RACF) . . . . . . . . . . . . . . . . . . . . 95

VM/ESA 2.4.0 DEMOpkg System Backup . . . . . . . . . . . . . . . . . . . . 99

Named Saved System (NSS) and IMG File Backup/Restore . . . . . . . . 103

Generating a New NCP for the 3745 . . . . . . . . . . . . . . . . . . . . . . 105

Web Server Demo Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

User ID Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

User ID Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Center Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

CCBACKUP System Version 1.3 . . . . . . . . . . . . . . . . . . . . . . . . . 117

Tape Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Using the CTRFMT DASD Formatting Tool . . . . . . . . . . . . . . . . . . 139

Using the CTRACNT Tool 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

VTAMOPER User ID Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

FCONMON Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

VMLINK Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Emergency Operations Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Alternate Nucleus IPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Restoring from Backup Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Specific Minidisk Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Environmental Record Editing and Printing Program (EREP) . . . . . . . 165

vi VM/ESA 2.4.0 Reference Guide

Appendix A. DISKMAP of the VM/ESA 2.4.0 DEMOpkg System . . . . . 169

Appendix B. Standard Device Addresses for the IBM Center . . . . . . . 187

Appendix C. DB2/VM Database Machines . . . . . . . . . . . . . . . . . . . 193

Appendix D. Tips and Techniques . . . . . . . . . . . . . . . . . . . . . . . 195

Appendix E. Logging On VMUSERnn . . . . . . . . . . . . . . . . . . . . . 199

Appendix F. Summary of DirMaint Syntax Commands . . . . . . . . . . . 203

Appendix G. Shared File System (SFS) . . . . . . . . . . . . . . . . . . . . 205

Appendix H. QDIR PACKAGE . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Appendix I. VM/ESA DEMOpkg Support . . . . . . . . . . . . . . . . . . . . 209

viii VM/ESA 2.4.0 Reference Guide

51. CCBACKUP Scheduler Display1 . . . . . . . . . . . . . . . . . . . . . . 121

x VM/ESA 2.4.0 Reference Guide

xii VM/ESA 2.4.0 Reference Guide

Who Should Use This Book

xiv VM/ESA 2.4.0 Reference Guide

xvi VM/ESA 2.4.0 Reference Guide

Introduction to VM/ESA 2.4.0 DEMOpkg

VM/ESA CMOS Product List by Market Segment . . . . . . . . . . . . . . . . . 5

VM/ESA P/R390 Product List by Market Segment . . . . . . . . . . . . . . . 11

Introduction to VM/ESA 2.4.0 DEMOpkg 1

2 VM/ESA 2.4.0 Reference Guide

VM/ESA 2.4.0 DEMOpkg