ABCs of z/OS System Programming Volume 3 - IBM Redbooks

More documents

Recommendations

Info

International Technical Support Organization ABCs of z/OS System Programming Volume 3 March 2010 SG24-6983-03
Page 1: ibm.com/redbooks Front cover ABCs o
Page 5 and 6: Contents Notices . . . . . . . . .
Page 7 and 8: 4.30 Virtual storage access method
Page 9 and 10: 6.2 The basic catalog structure (BC
Page 11 and 12: Notices This information was develo
Page 13 and 14: Preface The ABCs of z/OS® System P
Page 15 and 16: ► Send your comments in an e-mail
Page 17 and 18: Chapter 1. DFSMS introduction 1 Thi
Page 19 and 20: 1.2 Data facility storage managemen
Page 21 and 22: 1.3 DFSMSdfp component DFSMSdfp pro
Page 23 and 24: 1.4 DFSMSdss component DFSMSdss pro
Page 25 and 26: 1.5 DFSMSrmm component DFSMSdmm pro
Page 27 and 28: 1.6 DFSMShsm component DFSMShsm pro
Page 29 and 30: 1.7 DFSMStvs component Provide tran
Page 31 and 32: Chapter 2. Data set basics 2 A data
Page 33 and 34: 2.1 Data sets on storage devices DA
Page 35 and 36: 2.2 Data set name rules HARRY.FILE.
Page 37 and 38: Large format data sets Large format
Page 39 and 40: 2.5 Non-VSAM data sets DIRECTORY DS
Page 41 and 42: 2.6 Extended-format data sets and o
Page 43 and 44: 2.7 Data set striping Striping is a
Page 45 and 46: 2.8 Data set striping with z/OS V1R
Page 47 and 48: 2.9 Large format data sets Figure 2
Page 49 and 50: 2.10 Large format data sets and TSO
Page 51 and 52: 2.11 IGDSMSxx parmlib member suppor
Page 53 and 54:
Using CLIST OPENFILE INPUT/GETFILE
Page 55 and 56:
2.13 Data set specifications for no
Page 57 and 58:
System-determined block size The sy
Page 59 and 60:
The sequence for locating an existi
Page 61 and 62:
2.16 Volume table of contents (VTOC
Page 63 and 64:
Table 2-1 DSCBs that can be found i
Page 65 and 66:
Creating the VTOC and VTOC index To
Page 67 and 68:
is not specified, the default VTOC
Page 69 and 70:
Chapter 3. Extended access volumes
Page 71 and 72:
3.2 Large volumes before z/OS V1R10
Page 73 and 74:
3.3 zArchitecture data scalability
Page 75 and 76:
► As each application I/O is requ
Page 77 and 78:
is the actual unit address of a giv
Page 79 and 80:
not prepared to allow multiples I/O
Page 81 and 82:
3.7 HyperPAV implementation Applica
Page 83 and 84:
3.8 Device type 3390 and 3390 Model
Page 85 and 86:
3.9 Extended access volumes (EAV) I
Page 87 and 88:
3.10 Data sets eligible for EAV vol
Page 89 and 90:
3.11 EAV volumes and multicylinder
Page 91 and 92:
3.12 Dynamic volume expansion (DVE)
Page 93 and 94:
3.14 Command-line interface (DSCLI)
Page 95 and 96:
3.16 Select volume to increase capa
Page 97 and 98:
3.18 Select capacity increase for v
Page 99 and 100:
3.20 VTOC index with EAV volumes Wi
Page 101 and 102:
3.21 Device Support FACILITY (ICKDS
Page 103 and 104:
3.22 Update VTOC after volume expan
Page 105 and 106:
3.23 Automatic VTOC index rebuild -
Page 107 and 108:
3.24 Automatic VTOC rebuild with DE
Page 109 and 110:
3.25 EAV and IGDSMSxx parmlib membe
Page 111 and 112:
3.26 IGDSMSxx member BreakPointValu
Page 113 and 114:
3.27 New EATTR attribute in z/OS V1
Page 115 and 116:
3.28 EATTR parameter The EATTR para
Page 117 and 118:
3.29 EATTR JCL DD statement example
Page 119 and 120:
Note: Being listed in the tracker r
Page 121 and 122:
Tracker exclusion list The exclusio
Page 123 and 124:
Chapter 4. Storage management softw
Page 125 and 126:
Table 4-1 System utility programs S
Page 127 and 128:
Note: Load module partitioned data
Page 129 and 130:
► Copy and reblock load modules
Page 131 and 132:
COPY control statement In the contr
Page 133 and 134:
4.6 IEBGENER utility //COPY JOB ...
Page 135 and 136:
4.7 IEBGENER: Adding members to a P
Page 137 and 138:
4.9 IEHLIST utility //VTOCLIST JOB
Page 139 and 140:
4.11 IEHINITT utility Initializing
Page 141 and 142:
4.12 IEFBR14 utility //DATASETS JOB
Page 143 and 144:
Access methods are identified prima
Page 145 and 146:
4.14 Access method services (IDCAMS
Page 147 and 148:
4.15 IDCAMS functional commands ALT
Page 149 and 150:
4.16 AMS modal commands IF-THEN-ELS
Page 151 and 152:
4.17 DFSMS Data Collection Facility
Page 153 and 154:
4.18 Generation data group (GDG) Us
Page 155 and 156:
4.19 Defining a generation data gro
Page 157 and 158:
4.20 Absolute generation and versio
Page 159 and 160:
4.22 Partitioned organized (PO) dat
Page 161 and 162:
► A PDS has no mechanism to preve
Page 163 and 164:
Advantages of PDSEs PDSE advantages
Page 165 and 166:
SMSPDSE1 is created if the followin
Page 167 and 168:
volume SMS002. The original PDSs ar
Page 169 and 170:
and batch loader. The binder conver
Page 171 and 172:
Extended format data sets A special
Page 173 and 174:
BSAM support For BSAM in z/OS V1R9,
Page 175 and 176:
ecord data sets, as follows: Fixed-
Page 177 and 178:
Control interval (CI) VSAM stores r
Page 179 and 180:
- Several record definition fields
Page 181 and 182:
Sequence set The sequence set is th
Page 183 and 184:
4.35 VSAM: Processing a KSDS cluste
Page 185 and 186:
4.36 VSAM entry sequenced data set
Page 187 and 188:
4.38 VSAM relative record data set
Page 189 and 190:
4.40 VSAM linear data set (LDS) C O
Page 191 and 192:
4.42 VSAM: Mapping a linear data se
Page 193 and 194:
4.44 VSAM: Buffering modes User ACB
Page 195 and 196:
4.45 VSAM: System-managed buffering
Page 197 and 198:
4.46 VSAM buffering enhancements wi
Page 199 and 200:
Direct Weighted (DW) The majority i
Page 201 and 202:
SMBVSP is only a parameter for SMB
Page 203 and 204:
4.49 Data set separation SMS-manage
Page 205 and 206:
(PCU or volume). REQUIRED may be ab
Page 207 and 208:
DFSORT functions DFSORT adds the ab
Page 209 and 210:
Sun NFS version 2 protocols, the Su
Page 211 and 212:
► Fine-tune an SMS configuration
Page 213 and 214:
Backing up and restoring volumes an
Page 215 and 216:
4.56 DFSMSdss: Logical processing T
Page 217 and 218:
4.57 DFSMSdss: Physical processing
Page 219 and 220:
4.58 DFSMSdss stand-alone services
Page 221 and 222:
4.60 DFSMShsm: Availability managem
Page 223 and 224:
4.61 DFSMShsm: Space management SMS
Page 225 and 226:
4.62 DFSMShsm: Storage device hiera
Page 227 and 228:
4.63 ML1 enhancements with z/OS V1R
Page 229 and 230:
4.64 DFSMShsm z/OS V1R11 enhancemen
Page 231 and 232:
4.65 ML1 and ML2 volumes DFSMShsm w
Page 233 and 234:
4.66 Data set allocation format and
Page 235 and 236:
4.67 DFSMShsm volume types Daily Ba
Page 237 and 238:
4.68 DFSMShsm: Automatic space mana
Page 239 and 240:
4.69 DFSMShsm data set attributes A
Page 241 and 242:
4.70 RETAINDAYS keyword DFSMShsm us
Page 243 and 244:
4.71 RETAINDAYS keyword 99999 - If
Page 245 and 246:
4.72 DFSMShsm: Recall processing HS
Page 247 and 248:
4.73 Removable media manager (DFSMS
Page 249 and 250:
4.74 Libraries and locations IBM 34
Page 251 and 252:
the tape configuration database. Th
Page 253 and 254:
4.76 Managing libraries and storage
Page 255 and 256:
Chapter 5. System-managed storage 5
Page 257 and 258:
5.2 DFSMS and DFSMS environment Fig
Page 259 and 260:
amount of space required for the da
Page 261 and 262:
5.4 Service level objectives What p
Page 263 and 264:
5.5 Implementing SMS policies ACS R
Page 265 and 266:
5.6 Monitoring SMS policies Monitor
Page 267 and 268:
5.8 Using data classes TSO Allocate
Page 269 and 270:
5.9 Using storage classes 9393 RVA
Page 271 and 272:
5.10 Using management classes Expir
Page 273 and 274:
5.11 Management class functions All
Page 275 and 276:
► The VIO storage group uses syst
Page 277 and 278:
aggregate versions to retain, and h
Page 279 and 280:
For a detailed description of the A
Page 281 and 282:
SMS complex (SMSplex) A collection
Page 283 and 284:
► Modify an SCDS ► Define a new
Page 285 and 286:
5.18 Steps to activate a minimal SM
Page 287 and 288:
5.19 Allocating SMS control data se
Page 289 and 290:
5.20 Defining the SMS base configur
Page 291 and 292:
Defining a non-existent volume lets
Page 293 and 294:
Translating the ACS routines The tr
Page 295 and 296:
If the COMMDS points to another COM
Page 297 and 298:
2. Activating an SMS configuration
Page 299 and 300:
VARY SMS This command changes stora
Page 301 and 302:
5.26 Managing data with a minimal S
Page 303 and 304:
5.27 Device-independence space allo
Page 305 and 306:
5.28 Developing naming conventions
Page 307 and 308:
5.29 Setting the low-level qualifie
Page 309 and 310:
5.31 Planning and defining data cla
Page 311 and 312:
5.33 Use data class ACS routine to
Page 313 and 314:
5.35 Allocating a data set //NEWDAT
Page 315 and 316:
5.36 Creating a VSAM cluster //VSAM
Page 317 and 318:
5.37 Retention period and expiratio
Page 319 and 320:
5.39 Selecting data sets to allocat
Page 321 and 322:
5.41 System-managed data types Temp
Page 323 and 324:
5.42 Data types that cannot be syst
Page 325 and 326:
5.43 Interactive Storage Management
Page 327 and 328:
NaviQuest provides: - A familiar IS
Page 329 and 330:
► Recall data sets that have been
Page 331 and 332:
5.47 ISMF: Profile option Panel Hel
Page 333 and 334:
Panel List Dataset Utilities Scroll
Page 335 and 336:
5.50 ISMF: Volume Option Figure 5-5
Page 337 and 338:
5.52 ISMF: Data Class option Figure
Page 339 and 340:
5.54 ISMF: List option Panel List D
Page 341 and 342:
Chapter 6. Catalogs 6 A catalog is
Page 343 and 344:
Basic catalog structure (BCS) The b
Page 345 and 346:
One control interval can contain mu
Page 347 and 348:
► Non-VSAM volume record (NVR) -
Page 349 and 350:
Important: To minimize update activ
Page 351 and 352:
6.5 Using aliases // DD DSN=PAY.D1
Page 353 and 354:
6.6 Catalog search order IDCAMS 'CA
Page 355 and 356:
6.7 Defining a catalog and its alia
Page 357 and 358:
Catalog aliases are defined only in
Page 359 and 360:
6.9 Sharing catalogs across systems
Page 361 and 362:
6.10 Listing a catalog Use IDCAMS L
Page 363 and 364:
6.11 Defining and deleting data set
Page 365 and 366:
Delete generation data groups In th
Page 367 and 368:
6.12 DELETE command enhancement wit
Page 369 and 370:
6.13 Backup procedures Backing up a
Page 371 and 372:
6.14 Recovery procedures MASTER MAS
Page 373 and 374:
6.15 Checking the integrity on an I
Page 375 and 376:
6.16 Protecting catalogs DEFINE REC
Page 377 and 378:
6.17 Merging catalogs UCAT1 REPRO M
Page 379 and 380:
6.18 Splitting a catalog UCAT1 Figu
Page 381 and 382:
6.19 Catalog performance Factors th
Page 383 and 384:
6.20 F CATALOG,REPORT,PERFORMANCE c
Page 385 and 386:
6.21 Catalog address space (CAS) Us
Page 387 and 388:
6.22 Working with the catalog addre
Page 389 and 390:
6.23 Fixing temporary catalog probl
Page 391 and 392:
6.24 Enhanced catalog sharing MVS 1
Page 393 and 394:
Chapter 7. DFSMS Transactional VSAM
Page 395 and 396:
integrity. If the data set is open
Page 397 and 398:
LSR - local shared resources For LS
Page 399 and 400:
7.4 CICS function shipping before V
Page 401 and 402:
7.6 VSAM RLS overview VSAM RLS enab
Page 403 and 404:
7.7 Data set sharing under VSAM RLS
Page 405 and 406:
4. System 2 needs CI1 and CI4; CI1
Page 407 and 408:
committed or backed out. The reques
Page 409 and 410:
For LOG(ALL) you need to define a l
Page 411 and 412:
7.12 The batch window problem Batch
Page 413 and 414:
7.14 Coupling Facility structures f
Page 415 and 416:
D XCF,STR,STRNAME=IGWLOCK00 IXC360I
Page 417 and 418:
► RLS_MaxCfFeatureLevel({A|Z}) Th
Page 419 and 420:
► Place the SHCDSs on volumes wit
Page 421 and 422:
7.17 Update SMS configuration SMSBa
Page 423 and 424:
Command ===> SCDS Name . . . . . :
Page 425 and 426:
LABEL JOB ... //STEP1 EXEX PGM=IDCA
Page 427 and 428:
► RLS client Any address space th
Page 429 and 430:
VARY SMS command Use the VARY SMS c
Page 431 and 432:
7.21 Backup and recovery of CICS VS
Page 433 and 434:
7.22 Interpreting RLSDATA in an IDC
Page 435 and 436:
7.23 DFSMStvs introduction DFSMStvs
Page 437 and 438:
7.24 Overview of DFSMStvs DFSMStvs
Page 439 and 440:
7.25 DFSMStvs use of z/OS RRMS z/OS
Page 441 and 442:
7.26 Atomic updates Before After Be
Page 443 and 444:
7.28 DFSMStvs logging CICSA System
Page 445 and 446:
7.29 Accessing a data set with DFSM
Page 447 and 448:
- Cannot get a record before a sync
Page 449 and 450:
7.32 Prepare for logging Update CFR
Page 451 and 452:
Define log streams Each DFSMStvs in
Page 453 and 454:
► AKP(nnn[,nnn]...) - This specif
Page 455 and 456:
7.35 Interacting with DFSMStvs Inte
Page 457 and 458:
information about shunted URs and U
Page 459 and 460:
- Does not act as a recoverable res
Page 461 and 462:
Chapter 8. Storage management hardw
Page 463 and 464:
operating system point of view, dev
Page 465 and 466:
edundancy, which wastes space and c
Page 467 and 468:
The ESS was the first of the Seasca
Page 469 and 470:
8.4 Enterprise Storage Server (ESS)
Page 471 and 472:
8.5 ESS universal access Storage co
Page 473 and 474:
8.7 ESS host adapters Host adapter
Page 475 and 476:
► Greater unrepeated fiber link d
Page 477 and 478:
Eight-pack conversions The ESS eigh
Page 479 and 480:
adapter pair supports up to 96 disk
Page 481 and 482:
Spatial reuse Spatial reuse allows
Page 483 and 484:
A hot DDM spare pool consisting of
Page 485 and 486:
8.14 ESS copy services DATA MOVER C
Page 487 and 488:
► Application disaster recovery s
Page 489 and 490:
ack-end traffic. The ESS Model 800
Page 491 and 492:
Max hosts 1024 Max storage/disks 22
Page 493 and 494:
8.17 IBM TotalStorage DS8000 75.25
Page 495 and 496:
8.18 DS8000 hardware overview 2-Way
Page 497 and 498:
8.19 Storage systems LPARs Host Ada
Page 499 and 500:
8.20 IBM TotalStorage Resiliency Fa
Page 501 and 502:
8.21 TotalStorage Expert product hi
Page 503 and 504:
8.22 Introduction to tape processin
Page 505 and 506:
8.23 SL and NL format IBM Standard
Page 507 and 508:
8.24 Tape capacity - tape mount man
Page 509 and 510:
8.25 TotalStorage Enterprise Tape D
Page 511 and 512:
8.26 IBM TotalStorage Enterprise Au
Page 513 and 514:
8.27 Introduction to Virtual Tape S
Page 515 and 516:
8.28 IBM TotalStorage Peer-to-Peer
Page 517 and 518:
8.29 Storage area network (SAN) Fig
Page 519 and 520:
Related publications The publicatio
Page 521 and 522:
ABCs of z/OS System Programming Vol
Page 524:
ABCs of z/OS System Programming Vol
show all

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?