Environment: ZOS 1.12 The question: What does HSM look at to evaluate the DATASETSIZE value? We have coded the following in our startup parms for hsm (AN EXAMPLE) ADDVOL ABC123 UNIT(3390) MIGRATION(ML1 NODRAIN NOOVERFLOW) THRESHOLD(80) ADDVOL OVR123 UNIT(3390) MIGRATION(ML1 NODRAIN OVERFLOW) THRESHOLD(90) SETSYS ML1OVERFLOW(DATASETSIZE(301302))
Cut and Paste of description of DATASETSIZE: If the calculated size of a data set being backed up or migrated is equal to or greater than dssize, DFSMShsm prefers the OVERFLOW ML1 volume with the least amount of free space that still has enough remaining space for the data set. In our testing, we generated data sets sufficiently larger then 301302kb in size, yet, during a MIGRATE, the data set was still migrated to the NOOVERFLOW volume. The ultimate goal is to define EAV's as OVERFLOW volumes for large migrated dsns. Does anyone have any suggestions or ideas what I might be doing wrong? Sincerely; Ken Kripke [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
