The dsn is 1 cylinder. As suggested by others using AGE(0) would result in the migration all of the dsns from that volume (correct me if I am wrong). If I use the DAYS(X) parm instead of the AGE(0) would that be okay? HSEND FREEVOL MVOL(HSM501) DAYS(3) TARGETLEVEL(Ml2)
--- On Fri, 11/13/09, Mike Spencer <auspen...@bellsouth.net> wrote: From: Mike Spencer <auspen...@bellsouth.net> Subject: Re: DFHSM QUESTION - ARC1237I To: IBM-MAIN@bama.ua.edu Received: Friday, November 13, 2009, 7:11 AM A few things to check: How big is the data set that received the ARC1237I message? If this is a really big data set, and rarely used, then it should be migrated straight to ML2 tape using your Management Class definitions. Maybe it should have been written to tape to begin with. That is a decision you will need to determine based on size and frequency of the access by your end users of the file's data. You might want to consider using MOD-9, MOD-27 or MOD-54 for your ML1 volumes. Being that you received the out of space condition, a SDSP should not be considered, unless the majority of your ML1 files are very small and causing some serious fragmentation. What is the relationship between Primary Space Management and Secondary Space Management? If you are frequently running out of space on ML1; then there may be other issues with your Space Management cycles. Are there data set backup copies in your ML1 pool, are there problem data sets in your ML1 pool that are not migrating to ML2? Using a product such as MAINVIEW SRM can provide automated responses to migrate data from your ML1 volumes, or primary volumes based on thresholds you have set. The solutions can be set to migrate based upon size of the data, how many days unreferenced, type of the data, particular volumes or device types, anything you can imagine can be used as a trigger. MAINVIEW SRM will also monitor all DFHSM activity in real time to resolve any problems DFHSM encounters. Mike Spencer "willie bunter" <williebun...@yahoo.com> wrote in message news: <40324.30746...@web33903.mail.mud.yahoo.com>... Good Day All Readers, I received the following error message when I attempted to archive a dsn at the ML1 level: ARC1001I PRODD.AUDIT.D071104W.ZW090.SYSRES3 MIGRATE FAILED, RC=0037, REAS=0000 ARC1237I NO SPACE FOR MIGRATION COPY In the past I executed SECONDARY SPACE management to fix the problem. Is there something that I could do besides adding another ML1 volume with SMALLDS? Thanks. __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
