Re: WORM tape mount - type mismatch
Natasa, WORM and HSM; If this is something you really need, then do what I suggested in my last post. WORM and RMM; as others have said, you cannot returned a WORM to scratch. However, RMM has some smart stuff in it :-) that knows whether the volume has been used for user data and will allow you to scratch such a WORM tape. If the volume is still MASTER, check the release action is SCRATCH and then release it. It will/should go to scratch. Alternatives are listed (sorry for the bad list numbering) here http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2J101/8.10.3? SHELF=EZ2ZO10EDT=20040512154110 Also, a WORM volume can be relabelled to the same or different volser as long as no user data has been written to the volume. On Tue, 28 Jun 2005 08:03:03 -0500, Natasa Savinc [EMAIL PROTECTED] wrote: Mike, we had an idea to archive some data that way - one copy on one media (EMC Centera), and another on WORM tape as some kind of backup to the first one. HSM seemed like a logical choice, because it can fill a tape (but obviously not WORM), and it has some kind of record keeping capability. I have RMM related question about WORM - how can I return WORM tape to scratch? I read somewere that the only way to do that is to delete the volume from TCDB and re-define it. Is that correct? Regards, Natasa -- 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
Re: WORM tape mount - type mismatch
Mike, thank you for input, we will probably do that. Regards, Natasa -- 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
Re: WORM tape mount - type mismatch
I didn't specify DEVSUPxx. I also read that HSM can only use WORM for ABACKUP, so I will start form there and redesign my plans for WORM usage. Thank you all for help. Regards, Natasa -- 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
Re: WORM tape mount - type mismatch
Natasa, HSM currently only supports WORM tapes for ABARS; ABACKUP and ARECOVER. If you, or anyone else, believes they have a good reason to use WORM for other HSM functions please let HSM development know. They really do want to know why someone would want to do this. One way to do this might be to raise a ETR/PMR and explain your requirement; I am sure that would get to them. Mike WoodRMM Development On Mon, 27 Jun 2005 06:44:45 -0500, Natasa Savinc [EMAIL PROTECTED] wrote: Hello, we have 4-way HSMplex. ML2 migration is directed to 3590 tapes. I wanted to direct migration on one system to 3592 (WORM) tapes. I changed SETSYS definitions in ARCCMD member, created SMS constructs for WORM tapes, updated ACS routines and added VLPOOL definition in DFSMSrmm. When I tried migration, I see that the 3590 tape is being mounted on 3592 drive. This, of course, ends in error. Any ideas what else should be specified for this to work? Regards, Natasa -- 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
Re: WORM tape mount - type mismatch
Mike, we had an idea to archive some data that way - one copy on one media (EMC Centera), and another on WORM tape as some kind of backup to the first one. HSM seemed like a logical choice, because it can fill a tape (but obviously not WORM), and it has some kind of record keeping capability. I have RMM related question about WORM - how can I return WORM tape to scratch? I read somewere that the only way to do that is to delete the volume from TCDB and re-define it. Is that correct? Regards, Natasa -- 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
Re: WORM tape mount - type mismatch
Natasa, A WORM cartridge cannot be re-used (Write ONCE, Read Many). Once data has been written on a WORM cartridge, you can only add more data to it (either a MOD operation to the last file or adding secondary datasets behind it). Putting a WORM cartridge in SCRATCH status means you have destroyed the old one and have a new one that you want to relabel to have the same volser as the original; which means it has been deleted and then a new one re-defined. But it will be a completely new cartridge, you cannot re-initialize and you cannot re-use a WORM cartridge once data has been written to it. Only add additional data to it. Russell Witt CA-1 Level-2 Support Manager -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Natasa Savinc Sent: Tuesday, June 28, 2005 8:03 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: WORM tape mount - type mismatch Mike, we had an idea to archive some data that way - one copy on one media (EMC Centera), and another on WORM tape as some kind of backup to the first one. HSM seemed like a logical choice, because it can fill a tape (but obviously not WORM), and it has some kind of record keeping capability. I have RMM related question about WORM - how can I return WORM tape to scratch? I read somewere that the only way to do that is to delete the volume from TCDB and re-define it. Is that correct? Regards, Natasa -- 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
Re: WORM tape mount - type mismatch
Russell, I know that WORM cartridge cannot be re-used once user data is written on it. But I have a cartridge that was entered in library as PRIVATE (RMM status USER), and has never been used. So instead of doing eject/enter again, or delete/define via IDCAMS, I was wondering if there is a way to release it to scratch, because in this state it cannot satisfy scratch request. Regards, Natasa -- 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
Re: WORM tape mount - type mismatch
Natasa Savinc wrote: Russell, I know that WORM cartridge cannot be re-used once user data is written on it. But I have a cartridge that was entered in library as PRIVATE (RMM status USER), and has never been used. So instead of doing eject/enter again, or delete/define via IDCAMS, I was wondering if there is a way to release it to scratch, because in this state it cannot satisfy scratch request. I would eject it (using RMM command) and insert again. -- Radoslaw Skorupka Lodz, Poland -- 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
Re: WORM tape mount - type mismatch
Natasa Savinc wrote: Hello, we have 4-way HSMplex. ML2 migration is directed to 3590 tapes. I wanted to direct migration on one system to 3592 (WORM) tapes. I changed SETSYS definitions in ARCCMD member, created SMS constructs for WORM tapes, updated ACS routines and added VLPOOL definition in DFSMSrmm. When I tried migration, I see that the 3590 tape is being mounted on 3592 drive. This, of course, ends in error. Any ideas what else should be specified for this to work? 1. AFAIK HSM does not support WORM media, so it is not good idea to use WORM with HSM. 2. 3592 drives have the same unit name as 3590, it is 3590-1. It may be confusing, especially when you put generics into ARCCMDxx. 3. You have two parameters in data class definition: one describes media, another describes the drive. See Media Type nad Recording Technology. For 3592 with J1A carts (non-WORM) it should be EFMT1 and MEDIA5. HTH -- Radoslaw Skorupka Lodz, Poland -- 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
Re: WORM tape mount - type mismatch
This is not a specific HSM action, but have you also defined categories in the library and associated them with the correct media type (MEDIA6 or MEDIA8 for WORM i believe) in DEVSUPxx? Gil. On 6/27/05, Natasa Savinc [EMAIL PROTECTED] wrote: Hello, we have 4-way HSMplex. ML2 migration is directed to 3590 tapes. I wanted to direct migration on one system to 3592 (WORM) tapes. I changed SETSYS definitions in ARCCMD member, created SMS constructs for WORM tapes, updated ACS routines and added VLPOOL definition in DFSMSrmm. When I tried migration, I see that the 3590 tape is being mounted on 3592 drive. This, of course, ends in error. Any ideas what else should be specified for this to work? Regards, Natasa -- 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 -- 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
