hsm cds question - can we update cds to add new abars version at d.r?

2013-10-14 Thread Michael Bieganski
Help?...We are conducting an offsite disaster recovery drill tomorrow. The tapes with all the vsm and HSM cds files were cut on friday morning and already sent off to the d.r site in N.Y. An application needed to rerun an hsm-abars aggregate backup AFTER the files were on the truck. We re-ran the

Size limits on hsm cds files?

2013-11-06 Thread Michael Bieganski
Hi, We have an hsm ocds cds file sized cyl(4000,0) a bcds1 cds file sized cyl(4000,0) a bcds2 cds also sized cyl,(4000,0) an mcds1 cds file sized cyl(4000,0) and an mcds2 file also sized cyl(4000,0) About every 3 months or so, 1 or more of these start creeping into the 90%+ full range and we do

ISMF /SMS questions - Why aren't these datasets whacked?

2013-05-01 Thread Michael Bieganski
Hi, We are trying to lasso the extreme growth/size that our hsm has grown to in the last 2 years. The a large majority of our tapes (virtual) seem to tied to hsm backups. One big side-issue is that the lions share of our sms management classes all specify Expire-Non-Usage of Nolimit and also

Datasets not hsm migrating

2013-05-10 Thread Michael Bieganski
Hi, I have a number of datasets whose management class reflects Primary Days of 2 and yet after 2 weeks of non-reference, they still are on dasd. Cmd/Auto Migrate is set to BOTH, Auto-Backup set to No. I can hmigrate it in ispf 3.4 ok to ml2, but wondering why auto-migration is not kicking in. Is

RMM common practices

2013-07-08 Thread Michael Bieganski
Hi, I have 3 questions that I hope someone out there can share answers with me. After running an rmm EDGHSKP,PARM='CATSYNCH,VERIFY' I am left with about 3 dozen datasets showing cataloged in rmm but not in the usercat (eg EDG2233E DFSMSrmm CDS CATALOG STATUS YES FOR dsn VOLUME nn FILE 1

dfhsm expirebv command idles even though expirebv not held

2013-08-05 Thread Michael Bieganski
Hello, I've issued this tso hsend cmd: hsend expirebv abarsversions(agname(bkmcics) retainversions(0)) display and have been waiting for over an hour for the response to the terminal. When I issue an tso hsend q req, I see but only a tape being recycled, and MWEs ahead of my simple request:

ca - reclaim for hsm, rmm, cdses (and ucats??)

2013-08-14 Thread Michael Bieganski
Hello, we just upgraded our last lpar to zos 1.13 so now have the option of utilizing the ca-reclaim option. As of now, it is not defined in our parmlib so is dormant. I have both an rmm cds and an hsm bcds reorg necessary in the upcoming months and was wondering if anyone has experience yet

DFHSM expire processing

2013-08-23 Thread Michael Bieganski
Hi, We have four lpars, running zOS 1.13 and use dfhsm. On 3 of the lpars, expirebv is always held. Every morning at 7:30,automation issues this command on just one of our four lpars: HSEND EXPIREBV NONSMSVERSIONS(DBU(5) CATALOGEDDATA(50) - UNCATALOGEDDATA(0)) EXECUTE RESUME and at

Increase in tape usage since zOS 1.13??

2013-09-19 Thread Michael Bieganski
Hi, We have a set of weekly full volume dasd dumps just for our non-sms mvs volumes (sysres, pre-ipl vols etc), housing many of our system datasets that are almost purely static...ie do not grow or do not get written to. On July 21st, the lpar that run our weekly full volume dumps was upgraded to

Why does a dataset that should never migrate does occassionally (hsm)

2014-02-21 Thread Michael Bieganski
Hi, we have a mainframe dataset that is used daily used in our automated scheduling processes. Occassionally, our ops support gets paged out because a process is delayed and it turns out it was because said dataset was migrated and had to be recalled. this dataset's management class has nolimit

Deleting a nonexisting volser from hsm

2013-01-08 Thread Michael Bieganski
Looking at hsm logs, I see that a recycle failed on volume 300706 along with message ARC0184I ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X RECORD FOR 300706. Apparently, hsm is trying to recycle this 300706 volser twice daily and failing each time. I ran AUDIT MEDIACONTROLS VOLUMES(300706)

Re: Deleting a nonexisting volser from hsm

2013-01-09 Thread Michael Bieganski
THE DFSMSHSM CONTROL DATA SET X RECORD FOR 300706 Short of reconstructive surgery on the cds...is there any other commands I can try to tell HSM to just fuhget-about this non-existing volser 300706?? On Tue, Jan 8, 2013 at 10:32 AM, Michael Bieganski mbiegans...@gmail.comwrote: Looking at hsm

Is there a way to get all dsnames of a given sms mgmtclas, regardless if some are hsm-migrated?

2013-03-16 Thread Michael Bieganski
Using dcollect, or some other method, Is it possible to get list of all dsnames with a mgmtclas xyz even if some of the dsns are hsm-migrated ml1 or ml2? I coded this dcollect jcl: DCOLLECT - OUTFILE(DCOUT) - VOLUMES( - * - ) - MIGRATEDATA -

Re: Is there a way to get all dsnames of a given sms mgmtclas, regardless if some are hsm-migrated?

2013-03-17 Thread Michael Bieganski
Good point...thanks Scott -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Is there a way to get all dsnames of a given sms mgmtclas, regardless if some are hsm-migrated?

2013-03-17 Thread Michael Bieganski
Thanks for the tip Lizetteyour suggestion does indeed show all data I was hoping for. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: DFHSM audit error 39 on non-existing datasets

2013-04-05 Thread Michael Bieganski
Dave, Allen...where are we coming up with racf and arc1139?...the error is from hsm audit: I have alter to the dsn profile. The hsm storage admin guide has this for err 39...nothing about racf: *ERR 39 userdsn IS MISSING version The BCDS data set (B) record for userdsn refers to a backup version

Rename of hsm migrated files due to userid change

2013-04-21 Thread Michael Bieganski
Hi...in the coming months, our company plans to completely change the format of our mainframe userids. For example, current mainframe userid a#xyz123 will change to mainframe userid e123456. We have literally tens of thousands of mainframe userids and tens of thousands of hsm migrated datasets