You're right. I wonder why the OP would only want to recall ML2 data. Unless he was meaning bring all ML2 down to ML1.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 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(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), 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 Silvio Camplani > Sent: Monday, August 20, 2012 4:00 PM > To: [email protected] > Subject: Re: HSM - space for full recall > > The list command should have "select(ml2)" to exclude ML1 > > LIST dsname MCDS ODS(HLQ.DFHSM.LISTING) select(ml2) > > Regards, > > Silvio Camplani > zSeries Sr. Analyst, Systems Support > Bombardier > > On Mon, Aug 20, 2012, at 04:49 PM, Silvio Camplani wrote: > > 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
