Hi everyone,
I may be all wet, but this is my best resource for help on this issue until
I get back on support with z/OS 1.13.
I am running z/OS 1.11 (unsupported). Back in January, I applied all
maintenance to bring it up to RSU1301.
For years, I have had a MGMTCLAS of ATMBKUPS with conditional partial release
and a DATACLAS of TMBKUPLG:
Space Avgrec . . . . . . : M
Avg Value . . . . : 1
Primary . . . . . : 3500
Secondary . . . . : 2500
Data Set Name Type . . . . . : EXTENDED
If Extended . . . . . . . . : PREFERRED
Extended Addressability . . : YES
Record Access Bias . . . . : SYSTEM
Space Constraint Relief . . . : YES
Reduce Space Up To (%) . . : 5
Dynamic Volume Count . . . : 12
Compaction . . . . . . . . . : TCOM
I know that the multi-volume striping will not do the partial release at close,
but I thought that HSM migration/recall was resulting in the release of unused
space in these datasets.
Last week, I had several failures to allocate these datasets and noticed that
even after recall, these datasets remain at 65616 tracks usually about 5% used.
Have I been fooling myself that this large (never run out while actually
writing the SMF data) and release at migration ever worked? I suspect IBM will
not be real helpful until I can reproduce on z/OS 1.13 which will be later this
year.
Dave Gibney
Information Technology Services
Washington State University
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
