Hi, Wondered if anyone's seen this before?
When I display ML1 volumes with a LIST ML1 I get the following (x6) 1st 2 have SDSP=YES, last 4 look like this.. VOL=AAABBB DEVTYP=3390 VOLTYPE=LEV 1 MIGDS=00000 MIGTRKS=000000 MIGDATE-TIME=00/00/00 00:00 FRAG=.776 HI-THRESH=075 LO-THRESH=*** SDSP=NO SPACE-MGMT=*** AGE=*** AUTO-HOST MIG=** BACK=** DUMP=NO Does this mean the MCDS thinks it has no datasets on this volume? If so, then the MCDS doesn't appear to see ANY ML1 migration datasets as all 6 volumes have MIGDS=0000 MIGTRKS=000000 When I look through the VTOC's I see between 200 - 450 HSM.HMIG.xxx datasets on each volume. Assuming vol AAABBB has 240 HSM.HMIG dsn's listed on the VTOC, When I list that volume with a LIST DSN MCDS SEL(VOL(AAABBB)) i get 240 dsn's like the one below (DSN names changed for dataprot laws) DSN=PROD.DATASET.AAAXRC.O03.MON.HISTORY.D06171.T0713 MIGVOL=AAABBB DSO=PS SDSP=NO LAST REF=06/06/21 MIG=06/07/06 TRKS=0000180 2K BLKS= 0000975 TIMES MIG= 001 16K BLKS=****** LAST MIGVOL=****** My question is this, how come the LIST ML1 shows the volume having no MIGDS yet a LIST DSN for that volume shows 240? Our Secondary Space Management suddenly stopped running a few weeks ago and when I looked at the LIST ML1 output i thought I'd figured out why. The LIST DSN command appears to shoot this in down in flames. Any ideas anyone? Regards, Joe Jeffries ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
