Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

expiration date for a dataset

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
sparrow

New User


Joined: 26 Mar 2007
Posts: 57
Location: Pune

PostPosted: Wed Dec 30, 2009 7:06 pm    Post subject: expiration date for a dataset
Reply with quote

How to find the Expiration date for a dataset. I or S in front of the file didn't help.
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Wed Dec 30, 2009 7:37 pm    Post subject:
Reply with quote

Typically, tape data sets have expiration dates while disk data sets do not. So if the data set is on disk, tell us why you think it would have an expiration date and we can proceed from there. If it is on tape, unless you have very special privileges you will not be able to use ISPF I or S to get information about the data set since most TSO sessions are NOT allowed to mount tapes.

Usually your best bet is to contact your site support group for assistance.
Back to top
View user's profile Send private message
sparrow

New User


Joined: 26 Mar 2007
Posts: 57
Location: Pune

PostPosted: Wed Dec 30, 2009 7:53 pm    Post subject: Re: Reply to: expiration date for a dataset
Reply with quote

superk wrote:
LISTCAT didn't give you any information either?


Thanks Kevin...LISTCAT didn't show me the Expieation date..

HISTORY
DATASET-OWNER-----(NULL) CREATION--------2009.232
RELEASE----------------2 EXPIRATION------0000.000
Back to top
View user's profile Send private message
sparrow

New User


Joined: 26 Mar 2007
Posts: 57
Location: Pune

PostPosted: Wed Dec 30, 2009 7:56 pm    Post subject:
Reply with quote

Robert Sample wrote:
Typically, tape data sets have expiration dates while disk data sets do not. So if the data set is on disk, tell us why you think it would have an expiration date and we can proceed from there. If it is on tape, unless you have very special privileges you will not be able to use ISPF I or S to get information about the data set since most TSO sessions are NOT allowed to mount tapes.

Usually your best bet is to contact your site support group for assistance.


Robert,

the file is on disk..not on tape..I wanted to increase the retention period for the file..i used
DISP=SHR,
LABEL=RETPD=45

So wanted to check whether my retention period command worked..
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Wed Dec 30, 2009 8:44 pm    Post subject:
Reply with quote

Contact your site support group. Disk data set retention policies are created by and enforced by the storage management people. Usually data sets are assigned to a data class, and that class has the number of days to retain the data set. If you attempt to override the data class expiration, you may or may not be successful -- only your storage management group can provide you with the information you are asking. This is extremely site specific, so asking on this forum cannot provide you with any answers that will apply to your shop (except in the most general sense).
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Wed Dec 30, 2009 9:14 pm    Post subject:
Reply with quote

Robert Sample wrote:
Typically, tape data sets have expiration dates while disk data sets do not. So if the data set is on disk, tell us why you think it would have an expiration date and we can proceed from there.

I respectfully disagree. In my shop, every data set, whether it is on disk or on tape, must have an expiration date; else, it is considered volatile, and deleted by SMS at midnight (this prevents clueless junior "software engineers" from using up all the DASD with test data sets that they never delete).
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Wed Dec 30, 2009 10:10 pm    Post subject:
Reply with quote

Yours is the first shop I've heard of that does that (of course, I only have experience with 30 or 40 shops) ... usually there's a policy about how long before they migrate in HSM, but not actual expiration date for each data set. I suspect your site's catalog gets pretty hammered every day, too.
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Wed Dec 30, 2009 10:58 pm    Post subject:
Reply with quote

Robert Sample wrote:
I suspect your site's catalog gets pretty hammered every day, too.

Probably. OTOH, considering everything else going on here, I suspect that expiration processing is not a significant proportion of the hits that it gets. Our test data repository consists of about half a million data sets; the several thousand system analysts and test analysts seldom read them directly (and, to be sure, some of them need writing to for a meaningful test), but use various tools (some of which have my fingerprints on them) to make their own copies. Usually not more than a couple dozen data sets amounting to a pack or two per test, of course, but if they all stayed out there until IBM released z/OS V3...
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Thu Dec 31, 2009 4:03 am    Post subject:
Reply with quote

Akatsukami wrote:
I respectfully disagree. In my shop, every data set, whether it is on disk or on tape, must have an expiration date; else, it is considered volatile, and deleted by SMS at midnight (this prevents clueless junior "software engineers" from using up all the DASD with test data sets that they never delete).

Actually no, it need not have an explicit expiration date. The expiration policies may depend on a "since last referenced" date, which is not in effect an explicit expiration date. In a correctly defined storage environment even "clueless" software engineers are accomodated, and by George I've met enough of them on this forum.

Seems to me a rather draconian set up at your shop, maybe more thought and less sledgehammer icon_biggrin.gif
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Thu Dec 31, 2009 5:09 am    Post subject:
Reply with quote

expat wrote:
Akatsukami wrote:
I respectfully disagree. In my shop, every data set, whether it is on disk or on tape, must have an expiration date; else, it is considered volatile, and deleted by SMS at midnight (this prevents clueless junior "software engineers" from using up all the DASD with test data sets that they never delete).

Actually no, it need not have an explicit expiration date. The expiration policies may depend on a "since last referenced" date, which is not in effect an explicit expiration date.

Nope, I have looked at JCL, data set labels, etc. An explicit expiration date (or explicit retention period) must be specified, except when a PSdata set is given a TSO ID as HLQ (in which case it will be volatile ) or the data set is allocated on one of a small number of non-SMS-managed volumes...but you'd better have a bloody good business case for so doing!
Quote:
Seems to me a rather draconian set up at your shop, maybe more thought and less sledgehammer icon_biggrin.gif

I'm not on the storage management team, but I think it's been this way for decades; my shop has a quite inbred culture which should not be assumed to bear even a passing resemblance to best practices or even industry standards icon_smile.gif
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Thu Dec 31, 2009 2:57 pm    Post subject:
Reply with quote

Then I am pretty happy that I do not work there icon_biggrin.gif
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 437
Location: London

PostPosted: Thu Dec 31, 2009 8:17 pm    Post subject:
Reply with quote

I have worked at one shop that used explicity expiration dates for almost everything. A bizzare practice in my view!

The key here is if the dataset is SMS managed, and what Mgmtclas it has assigned to it. It is generally the case that Storage people will specify the max RETPD value to 0 in the Mgmtclas definition and this means requested EXPDT or RETPD is not accepted and just ignored, no matter what you code.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts FTP - JCL failed while passing FTP co... Suneetha1612 JCL & VSAM 12 Wed Nov 16, 2016 7:33 pm
No new posts TOT & DATE parameter in ICEMAN hemanthj642 DFSORT/ICETOOL 4 Mon Nov 14, 2016 5:19 am
This topic is locked: you cannot edit posts or make replies. How to pass the previous month date i... Suganya87 DFSORT/ICETOOL 5 Mon Oct 31, 2016 4:13 pm
This topic is locked: you cannot edit posts or make replies. Get correct date and time when curren... balaji81_k DB2 24 Fri Oct 14, 2016 10:40 pm
No new posts To trim spaces in a pipe delimited da... Nish84 COBOL Programming 16 Mon Oct 10, 2016 1:54 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us