It looks like he may have many bad records on his BCDS that have not been
deleted in over 3 years. Which probably explains the size of the BCDS
dataset. I think the AGE=2993 may be the point when EXPIREBV may have had
problems.
When I had a similar issue, I got very conservative and worked with IBM to
resolve these issues so I would not break the BCDS. But when I did get a
good listing, the EXPIREBV ran for many hours. But it eventually cleaned up
the mess.
I would recommend he contact IBM and open an ETR to get assistance with
correcting the BCDS, as it may have "broken" records.
Then I would suggest that a review of the SMS classes to ensure that
EXPIREBV gets rid of the correct backups.
I agree that this looks like a task is needed to do this cleanup. And
involving IBM to correct the BCDS a valid direction to take.
Lizette
>>> David O'Brien Wrote
A. Expirebv has two modes: Display and Execute. If this is the first time
you've run the command, I would strongly urge you to run Display first and
make sure that the backups being deleted are the ones you want deleted in
accordance with your SMS Management class policies.
B.Isyour log set up to issue all msgs. or only error msgs.? see HSM.Parmlib
ARCCMDxx
SETSYS-
ACTLOGTYPE(DASD) -
ACTLOGMSG(FULL)
I hold issue a Hold Expirebv immediately
Re-run Listcat for BCDS to see if any records have been deleted.
Check ACTLOGMSG value.
Release Expirebv and run Expirebv display to see what remains to be deleted
and whether those backups ought to be deleted.
>>> A.Cecilio wrote:
I did another BCDS cds reorg last sunday, now it has:
STATISTICS
REC-TOTAL--------4650469 SPLITS-CI--------------0
REC-DELETED------------0 SPLITS-CA--------------0
REC-INSERTED-----------0 FREESPACE-%CI----------0
REC-UPDATED------------0 FREESPACE-%CA----------0
REC-RETRIEVED---16310129 FREESPC-------2024644608
ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------3428352000
SPACE-PRI-----------4650 HI-U-RBA------1403781120
SPACE-SEC--------------0
ARC0148I BCDS TOTAL SPACE=3348000 K-BYTES, CURRENTLY 422
ARC0148I (CONT.) ABOUT 67% FULL, WARNING THRESHOLD=80%, TOTAL
ARC0148I (CONT.) FREESPACE=59%, EA=NO, CANDIDATE VOLUMES=0
Besides of runing every day, EXPIREBV job:
HSEND WAIT EXPIREBV EXECUTE SYSOUT(J)
I checked backup log and saw this:
DFSMSHSM BACKUP LOG, TIME 19:03:20, DATE 10/01/03
ARC0680I EXPIRE BACKUP VERSIONS STARTING AT 19:03:21 ON 2010/01/03, SYSTEM
SYB1
ARC0184I ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET C RECORD FOR
PDFHSM.BACK.T392220.SYS3.DV.J1295, RC=0004
ARC0734I ACTION=EXBACKV FRVOL=****** TOVOL=****** TRACKS= *** RC=
4, REASON= 0, AGE=2993,
DSN=PDFHSM.BACK.T392220.SYS3.DV.J1295
ARC0184I ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET C RECORD FOR
PDFHSM.BACK.U122420.SYS3.DV.J1295, RC=0004
ARC0734I ACTION=EXBACKV FRVOL=****** TOVOL=****** TRACKS= *** RC=
4, REASON= 0, AGE=2993,
DSN=PDFHSM.BACK.U122420.SYS3.DV.J1295
ARC0734I ACTION=EXBACKV FRVOL=****** TOVOL=****** TRACKS= *** RC=
28, REASON= 0, AGE=2509,
DSN=SYS3.DV.PROJCL.BACKUP.DBRM
ARC0734I ACTION=EXBACKV FRVOL=****** TOVOL=****** TRACKS= *** RC=
28, REASON= 0, AGE= 0,
DSN=SYS3.DV.PROJCL.BACKUP.DBRM
however, I now did a HSEND WAIT EXPIREBV DISPLAY SYSOUT(J) and it's
generating a lot of records. At this time, job is still running and the
backup log has 28.761 lines.
Is it possible that the EXPIREBV EXECUTE is not working at all after giving
above errors ??
Any h'int is welcome
Many thx once more, A.Cecilio.
----------------------------------------------------------------------
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
