No wonder, thank you. I'll try that. ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Lizette Koehler [[email protected]] Sent: Monday, August 20, 2012 6:00 PM To: [email protected] Subject: Re: HSM - space for full recall
You are probably running out of space. Use the command with the ODS(your_name_here) and preallocate it really large (a couple 1000 cylinders to start) Lizette -----Original Message----- >From: Uriel Carrasquilla <[email protected]> >Sent: Aug 20, 2012 2:52 PM >To: [email protected] >Subject: Re: HSM - space for full recall > >For some reason I am not getting the summary at the end of the listing. >I'll submit the console command. > >________________________________________ >From: IBM Mainframe Discussion List [[email protected]] on behalf of >Lizette Koehler [[email protected]] >Sent: Monday, August 20, 2012 5:38 PM >To: [email protected] >Subject: Re: HSM - space for full recall > >Uriel, > >After reading the posts, all you need to do is this > >LIST DATASETNAME MCDS ODS(your_dataset_name_here) SELECT(ML2) > >The end of the report will summarize your usage. > >You can do this through the console with a F dfhsm,LIST.... >Or HLIST command in TSO Option 6. > >So long as you have the ODS(...) parm it will not tie up your tso session. > >Lizette > >-----Original Message----- >>From: Uriel Carrasquilla <[email protected]> >>Sent: Aug 20, 2012 2:34 PM >>To: [email protected] >>Subject: Re: HSM - space for full recall >> >>We have all the HSM ML2 on VTL and the VTL guy is telling me that I am using >>70 TBytes. >>I believe I am using 40 TBytes. >>So far this is what I coded in REXX: >>Address TSO >>"hsend wait list datasetname('"file"') mcds ods('"list"') select(ml2)" >> >>But I must specify one "file" at a time. >>is there a method to specify a high-level instead of the full dataset name? >> >>________________________________________ >>From: IBM Mainframe Discussion List [[email protected]] on behalf of >>McKown, John [[email protected]] >>Sent: Monday, August 20, 2012 5:15 PM >>To: [email protected] >>Subject: Re: HSM - space for full recall >> >>Silvio indicated ML2 only can be gotten with a SELECT(ML2). I just don't >>understand why anyone would want to only restore __all__ ML2 and not restore >>ML1. Unless the OP meant how much space would it take on ML1 to recall all >>the ML2 data to ML1. Which I don't even know how to do, other than HRECALL >>and then HMIGRATE it. But, personally, I would do that one data set at a time >>to minimize HSM overhead and the amount of primary DASD required. >> >>I can separate them because I can tell the difference between an ML2 volser >>and an ML1 volser in the listing. This is because ML2 is tape, which are all >>numeric. And ML1 is DASD, all of which at my installation begin with HSM. >> >>-- >>John McKown >>Systems Engineer IV >>IT >> >>Administrative Services Group >> >>HealthMarkets® >> >>9151 Boulevard 26 • N. Richland Hills • TX 76010 >>(817) 255-3225 phone • >>[email protected] • www.HealthMarkets.com >> >>Confidentiality Notice: This e-mail message may contain confidential or >>proprietary information. If you are not the intended recipient, please >>contact the sender by reply e-mail and destroy all copies of the original >>message. HealthMarkets® is the brand name for products underwritten and >>issued by the insurance subsidiaries of HealthMarkets, Inc. –The Chesapeake >>Life Insurance Company®, Mid-West National Life Insurance Company of >>TennesseeSM and The MEGA Life and Health Insurance Company.SM >> >> >>> -----Original Message----- >>> From: IBM Mainframe Discussion List [mailto:[email protected]] >>> On Behalf Of Lizette Koehler >>> Sent: Monday, August 20, 2012 4:11 PM >>> To: [email protected] >>> Subject: Re: HSM - space for full recall >>> >>> john, >>> >>> I think the OP requested ML2 only, won't the MCDS entries be for both >>> ML1 and ML2? Is there a way to separate it? >>> >>> Lizette >>> >>> >>> -----Original Message----- >>> >From: "McKown, John" <[email protected]> >>> >Sent: Aug 20, 2012 1:52 PM >>> >To: [email protected] >>> >Subject: Re: HSM - space for full recall >>> > >>> >Neat. I'm using the data for a different analysis and never looked at >>> the very bottom. >>> > >>> >-- >>> >John McKown >>> >Systems Engineer IV >>> >IT >>> > >>> >Administrative Services Group >>> > >>> >HealthMarkets(r) >>> >> >>> >> -----Original Message----- >>> >> From: IBM Mainframe Discussion List [mailto:IBM- >>> [email protected]] >>> >> On Behalf Of Silvio Camplani >>> >> Sent: Monday, August 20, 2012 3:50 PM >>> >> To: [email protected] >>> >> Subject: Re: HSM - space for full recall >>> >> >>> >> The end of the report produced by the commands below will have the >>> >> totals: >>> >> >>> >> MIGRATED TRACKS BYTES >>> >> DATA SETS MIGRATED MIGRATED >>> >> >>> >> 000009778 000001829K 076546048K >>> >> >>> >> >>> >> Regards, >>> >> >>> >> Silvio Camplani >>> >> zSeries Sr. Analyst, Systems Support >>> >> Bombardier >>> >> >>> >> On Mon, Aug 20, 2012, at 04:40 PM, McKown, John wrote: >>> >> > If you enter a TSO command such as: >>> >> > >>> >> > HSEND LIST DATASETNAME MCDS ODS(HLQ.DFHSM.MCDS.LISTING) >>> >> > >>> >> > It will create (or append to) the dataset HLQ.DFHSM.MCDS.LISTING. >>> An >>> >> > example of this output is: >>> >> > >>> >> > 1- DFSMSHSM CONTROL DATASET - MIGRATED DATASET-- LISTING ----- AT >>> >> > 08:20:54 ON 12/08/20 FOR SYSTEM=LIH1 >>> >> > >>> >> > DATASET NAME MIGRATED LAST REF >>> >> MIGRATED >>> >> > TRKS QTY TIMES DS SDSP QTY LAST MIG >>> >> > ON VOLUME DATE >>> >> DATE >>> >> > ALLOC 2K BLKS MIG >>> ORG >>> >> DS >>> >> > 16K BLKS VOLUME >>> >> > >>> >> > AAHPN.DJDE.RPTS 290666 02/02/21 >>> >> 02/03/08 >>> >> > 0000001 ******* 001 PS NO 000001 *NONE* >>> >> > ACHMG.ASSUM.ROP.REPORT.G0023V00 288877 04/08/14 >>> >> 08/12/01 >>> >> > 0000001 ******* 001 PS NO 000001 *NONE* >>> >> > >>> >> > This will show you each DSN which is migrated and the "TRKS ALLOC" >>> >> for >>> >> > each. You can these values up using the utility of your choice. If >>> >> you >>> >> > have DB2, you could possibly write a utility to insert each DSN >>> into >>> >> a >>> >> > table, then use SQL to do various summations for you. Or use SAS. >>> Or >>> >> > ?????. Given my own preferences, I would download this to my Linux >>> >> > desktop and process it with Perl. But I'm known to be weird. >>> >> > >>> >> > -- >>> >> > John McKown >>> >> > Systems Engineer IV >>> >> > IT >>> >> > sage: INFO IBM-MAIN >>> >> >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >> >> >>---------------------------------------------------------------------- >>For IBM-MAIN subscribe / signoff / archive access instructions, >>send email to [email protected] with the message: INFO IBM-MAIN >>---------------------------------------------------------------------- >>For IBM-MAIN subscribe / signoff / archive access instructions, >>send email to [email protected] with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
