Mainframe, MVS and zOS Discussion

Hi,

One of the question which I have never experienced in real life wasasked in this interview. Question goes like this, is it possible to extend the expiration date of a dataset? If we can do so, what is the command for it or do we need to write some JCL for it?

I have searched about it on google but I could really find out how to get it. It is also said that it should be done, why?

You can do this using the ALTER command of IDCAMS. Whether you do it online or batch, and whether there is standard JCL, is of course dependent on your installation's standards.

Note that this may, in real life, be a futile, even dangerous, effort. Usually data sets on DASD do not have an explicit expiration date, and an attempt to give such a data set one will likely be overridden by SMS, if it is active. Moreover, what appear to be attempts to circumvent SMS may result in negative attention from corporate security, and be punished by actions up to and including termination.

Using DISP=MOD and a new expiration date can extend the date. SMS allows a default expiration date (retention period) in the management class, which may invalidate this. Finally, tape management systems usually control tape expiration, so unless the expiration date is changed in both the tape management system AND the operating system, they will be out of sync and hence could cause unpredictable results.

It's an odd interview question that doesn't really address the complexities that can ensue.

Thanks both.

Akatsukami wrote: Note that this may, in real life, be a futile, even dangerous, effort. Usually data sets on DASD do not have an explicit expiration date, and an attempt to give such a data set one will likely be overridden by SMS, if it is active. Moreover, what appear to be attempts to circumvent SMS may result in negative attention from corporate security, and be punished by actions up to and including termination.

Why would it lead to a termination? You mean job termination, right? Why would this happen just changing the expiry date of the dataset?

Why would it lead to a termination? You mean job termination, right? Why would this happen just changing the expiry date of the dataset?

"Termination" in this context is referring to employee termination for cause. Company managers do NOT like people attempting to avoid their established policies and procedures (especially security policies that control data set expiration), and attempting to change the expiry date of a data set without the advice and consent of the site support group could be seen as just such an action. It may not lead to employee termination, but that is one possible outcome of the course of action you are talking about.

Robert Sample wrote:

Why would it lead to a termination? You mean job termination, right? Why would this happen just changing the expiry date of the dataset?

"Termination" in this context is referring to employee termination for cause. Company managers do NOT like people attempting to avoid their established policies and procedures (especially security policies that control data set expiration), and attempting to change the expiry date of a data set without the advice and consent of the site support group could be seen as just such an action. It may not lead to employee termination, but that is one possible outcome of the course of action you are talking about.

I was not aware about the severity of this. But if do it under proper supervision, will that still cause a problem? I think, no?

That is already answered in Robert's post.

Thanks ..I missed to read it carefully.