Actually, I just did a DFDSS logicial copy, and looks like there are smarts
built-in….My cloning process first copies all non-ZFS data, and then copies all
ZFS data after that. Looks like all the VSAM files landed in EAS space by
default even though EATTR isn’t specified on the datasets, and that there is
plenty TMS available afterwards….
File Manager Display VTOC Data Set List
Row 00061 of 00821
Command ===>
Scroll CSR
Unit * DSN '**'
DevType * VOLSTATE ALL SMS SG *
Volumes 1 Data sets 780 VSAM 10 non-VSAM 770
(CMS) 1 Data sets 34 VSAM 34 non-VSAM 0
VOLSER RST03A Trks used 327567 Free 655233 Utilized 33%
(CMS) Cyls used 36876 Free 1079610 Utilized 3%
Data Set Name Seq Volume Begin CYL-HD
End CYL-HD Tracks Dsorg Recfm Lrecl Blksize Created
** RST03A * *
* * * *
CEE.SCEESPC 1 RST03A 685 4
686 15 PO U 0 32760 2021.298
CEE.SCEESPCO 1 RST03A 686 4
686 7 PO FB 80 27920 2021.298
CEE.SIBMAM24 1 RST03A 686 11
687 8 PO U 0 32760 2021.298
CEE.SIBMCALL 1 RST03A 687 4
687 3 PO U 0 32760 2021.298
CEE.SIBMCAL2 1 RST03A 687 7
687 3 PO U 0 32760 2021.298
CEE.SIBMMATH 1 RST03A 687 10
688 14 PO U 0 32760 2021.298
CEE.SIBMTASK 1 RST03A 688 9
688 4 PO U 0 32760 2021.298
OMVSU.RST03A.FNT.DATA 1 RST03A 65520 0
65540 315 VS U 0 4096 2024.143
OMVSU.RST03A.GDPS460.ZFS.DATA 1 RST03A 65541 0
66044 7560 VS U 0 4096 2024.143
OMVSU.RST03A.JAVAV11.DATA 1 RST03A 66045 0
68039 29925 VS U 0 4096 2024.143
OMVSU.RST03A.JAVAV17.DATA 1 RST03A 68040 0
69740 25515 VS U 0 4096 2024.143
OMVSU.RST03A.JAVA31V8.DATA 1 RST03A 69741 0
70622 13230 VS U 0 4096 2024.143
OMVSU.RST03A.JAVA64V8.DATA 1 RST03A 70623 0
71672 15750 VS U 0 4096 2024.143
OMVSU.RST03A.NETVHFS.DATA 1 RST03A 71673 0
71798 1890 VS U 0 4096 2024.143
VTOC Summary Information
Volume . : RST03A
Command ===>
Unit . . : 3390 Free Space
VTOC Data Total Tracks Cyls
Tracks . : 659 Size . . : 16,849,383 1,123,291
%Used . . : 3 Largest . : 16,194,150 1,079,610
Free DSCBS: 32,075 Free
Extents . : 6
Volume Data Track Managed Tracks Cyls
Tracks . : 17,730,090 Size . . : 655,233 43,681
%Used . : 4 Largest . : 655,227 43,681
Trks/Cyls: 15 Free
Extents . : 5
Dave Jousma
Vice President | Director, Technology Engineering
From: IBM Mainframe Discussion List <[email protected]> on behalf of
Jousma, David <[email protected]>
Date: Wednesday, May 22, 2024 at 12:44 PM
To: [email protected] <[email protected]>
Subject: EAV sysres?
So, for various reasons, mostly for ease of management, we have maintained a
single volume sysres. Today they are non-sms mod-54’s. But alas, based on our
product mix, I am close to exceeding the capacity of a -54. I am looking to
move to EAV
So, for various reasons, mostly for ease of management, we have maintained a
single volume sysres. Today they are non-sms mod-54’s. But alas, based on our
product mix, I am close to exceeding the capacity of a -54. I am looking to
move to EAV volumes, which z/OS supports, and my storage team wants to give me
their standard thin provisioned 1TB volumes to use. I want to “force” all my
ZFS datasets into Cylinder managed space. I know I can do that by
reallocating them with EATTR(OPT), but that’s not convenient. I don’t see a
way that DFDSS can do that on COPY or DUMP/RESTORE. I don’t believe IDCAMS
ALTER will do it either?
Looking for some nifty way to make this happen. Thanks in advance for any
feedback!
Dave Jousma
Vice President | Director, Technology Engineering
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
