|
View previous topic :: View next topic
|
| Author |
Message |
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| Code: |
MVC CCHHR,DSxPTRDS
OBTAIN CAMLST
...
CAMLST CAMLST SEEK,CCHHR,VOL,DSCBAREA
VOL DC CL6'XXXXXX'
DC 0D'0'
DSCBAREA DC XL140'0' |
OBTAIN with CAMLST SEEK is described in DFSMSdfp Advanced Services in the same area as OBTAIN with CAMLST SEARCH. I've never used the multiple DSCB feature of OBTAIN, though I know about it. After reading about your problems with it, I'm reluctant to try! |
|
| Back to top |
|
 |
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| David Robinson wrote: |
Good point Steve, of course, nothing is ever that straightforward!
I think also that the reverse can occur, that it to say if a dataset grows to a second extend because the primary space allocation was insufficient, but that secondary extent happens to be on a contiguous portion of disk to the first extent, then it will subsequently be reported as one extent, not two. |
Well, no, check this -
| Code: |
---NO--RELTRK--START CCHH--END CCHH--TRACKS
1 00000 0012000D 0012000D 1
2 00001 001E000E 001E000E 1
3 00002 001F000E 001F000E 1
4 00003 00220000 00220000 1
5 00004 00220008 00220008 1
6 00005 002F000E 002F000E 1
7 00006 00590002 00590002 1
8 00007 0082000E 0082000E 1
9 00008 0088000E 0088000E 1
10 00009 0109000B 0109000B 1
11 0000A 0109000C 0109000C 1
12 0000B 0109000D 0109000D 1
13 0000C 0109000E 0109000E 1
14 0000D 010F0000 010F0000 1
15 0000E 010F0001 010F0001 1
16 0000F 010F0002 010F0002 1 |
The data set was created by copying SMF data to it, with the intent it would get a B37. |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
| David Robinson wrote: |
Good point Steve, of course, nothing is ever that straightforward!
I think also that the reverse can occur, that it to say if a dataset grows to a second extend because the primary space allocation was insufficient, but that secondary extent happens to be on a contiguous portion of disk to the first extent, then it will subsequently be reported as one extent, not two. |
You're right...for SMS managed VSAM datasets 'Extent Consolidation' takes effect so that extents are merged into one if a subsequent extent can be taken next to the previous one. There's some restrictions for RLS datasets, catalogs and VVDS's, page space etc.
pic.dhe.ibm.com/infocenter/zos/v1r13/index.jsp?topic=%2Fcom.ibm.zos.r13.idad400%2Fspalloc.htm
You also have Dataclas Space Constraint Relief these days that will alter extent sizes to fit available space.
Curious why you're trying to write a utility for this when there are so many already out there. Naviquest (ISMF batch), FDREPORT and DMS to name a few. Even the REXX LISTDSI and SYSDSN functions might help. |
|
| Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| Pete Wilson wrote: |
| ... Curious why you're trying to write a utility for this when there are so many already out there. Naviquest (ISMF batch), FDREPORT and DMS to name a few. Even the REXX LISTDSI and SYSDSN functions might help. |
Pete - It's worth learning how to do this. Maybe -- unlikely -- he'll figure out a better way, either in terms of doing the mechanics better or in terms of displaying the information. |
|
| Back to top |
|
|
|
|
