|
View previous topic :: View next topic
|
| Author |
Message |
santoshkumarmanilakkoju
New User
.jpg)
Joined: 24 Nov 2009
Posts: 37
Location: Don't know
|
|
|
|
Hi,
We had an issue with our production runs and the job failed due to SB37.
We increased the space(for the failed DS) to max and tested but the job still failed.So used CART and the job did fine.
But when we checked the file's properties the file would disappear on 02/08/2010 as per the expiry date.
Is it possible to change the properties of the file to increase the retention/expiry period.By the way this file is GDG DS.
Thanks in advance,
Santosh. |
|
| Back to top |
|
 |
Mathiv Anan
Active User
Joined: 23 Jul 2008
Posts: 106
Location: USA
|
|
| Back to top |
|
|
santoshkumarmanilakkoju
New User
Joined: 24 Nov 2009
Posts: 37
Location: Don't know
|
|
|
|
Hi,
I have checked the manual and it is mentioned about new files.
But the problem is with existing catalogued file.
Is their any way to change th eproperties of the existing file so that it would not disappear after the expiry date. |
|
| Back to top |
|
|
Mathiv Anan
Active User
Joined: 23 Jul 2008
Posts: 106
Location: USA
|
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Is the tape under control of some tape management system?
Suggest you talk with the storage management people. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Yes, your storage management people are the one to contact as they are responsible for the policies and procedures at your site.
Every shop that I have implemented storage management procedures there is no way to over ride the retention and/or management of daatsets without the explicit involvement of the storage team. The policies are set in stone and only the storage team have the access to make amendments - which are accompanied by a written request. |
|
| Back to top |
|
|
santoshkumarmanilakkoju
New User
Joined: 24 Nov 2009
Posts: 37
Location: Don't know
|
|
|
|
| Thank you ALL |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Expat - if one code new EXPDT=?? on the DCB of tape-file in question and use MGMTCLAS which allows the range used for new value on EXPDT, should that help OP? |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
That depends on the setup of the storage environment. I set it up so that only trusted people can bend the rules.
For DASD datasets I always set up the SMS constructs to ignore specified retention / expiry dates. There was always one or two constructs that allowed specific users to specify these criteria and accept the values, but access to this was strictly controlled by the storage people and RACF.
Same with MGMTCLAS, if you wasn't allowed to specify a particular MGMTCLAS in your JCL or online allocation then the SMS routines ignored what the user put in and used the default for that dataset. So you would specify MGMTCLAS=RET00366 in the JCL but in fact SMS would allocate the default, for example MGMTCLAS=RET00090.
It's about a zillion years since I last set up CA-1, but know that it can be set up to ignore user specified retention or expiry dates, unless of course you are an authorised user. Valid requests to change retention were easily actioned by storage management via the CA-1 ISPF interface.
Let's face it, that is why we have retention policies and procedures to stop people keeping things for 20 years when they no longer need it after 10 days. It is natural for developers etc. etc. to want to keep everything, but it's equally natural for us storage guys to smile with satisfaction as we watch the datasets being expired  |
|
| Back to top |
|
|
|
|
