Dave: I get the daily digest so this might already have been pointed out...
We don't HSM here (we're an Innovation shop) but is the "HSM migration/recall"
process you talk about the same as "Space Management cycle" from the manual? I
would suspect that HSM preserves the actual dataset size(s) during
migration/recall unless you specify otherwise ie. via parms. For FDRABR, it's
DATA={ALL | USED}.
z/OS V1R12.0 DFSMSdfp Storage Administration:
Conditional. If a nonzero secondary space allocation has been specified for the
data set, release unused space at Space Management cycle time. This option only
applies to physical sequential and partitioned data sets. If specified for an
extended format VSAM data set, this option is processed as if Yes were
specified.
--------> signature = 6 lines follows <--------
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585 fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
"How *do* you plan for something like that?" Guardian Bob, Reboot
"For every action, there is an equal and opposite criticism."
"Systems Programming: Guilty, until proven innocent" John Norgauer 2004
-----Original Message-----
From: Gibney, Dave [mailto:[email protected]]
Sent: July 8, 2013 15:29
Subject: PS-E not releasing with HSM Migrate/Recall
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:
[snip]
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.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
