Joined: 14 Aug 2006 Posts: 20 Location: Pune,India
Hi,
Is it possible to specify expiry date for a DASD dataset thru JCL, I tried using the LABEL parameter, but it is not taking the Expiry date that, I have specified.
Joined: 14 Aug 2006 Posts: 20 Location: Pune,India
Hi kumaresh,
I have mentioned it that it is not picking the expiry date i have given, The job is not abending or saying that there is any violation while defining the dataset.
The JCL is a simple IEBCOPY, i want the backup to be deleted after some days automatically. The STEP is as shown below.
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
It is entirely possible that your SMS environment has been set up to ignore user specified retention and expiry dates. That's the way I set up my environments to maintain the storage policies.
If your environment is not set up as above, the fact that you have said that a dataset may be expired at a certain date, dependingon the SMS setup, it may or may not honour your desires and actually delete your file when you want it to.
I don't know which version of the JCL manuals you have, but RETPD is a parameter in its own right, so you only need to code RETPD=5
Joined: 14 Aug 2006 Posts: 20 Location: Pune,India
Hi,
I am using a Vendor provided mainframe system, so I am unable to contact any admin guy. We just get our accesses when needed thats it. If there is any other way to specify the expiry date, thru REXX or anything will be helpful, or atleaset know that the RACF or SMS is ignoring my expiry date.
I think RACF is not sllowing you to do this,,,,Please read this,I dont think so how much its helpful to you.But you can provide the expiry date in RACF Panels.
One main thing you have to be Authorized to do this,Better you can get help from REXX Peoples in the form.I didnt know REXX.
IF any Security Related problem in RACF I guide you.
Cheers,
Kumaresh.M
DATA SET PROFILES
RACF keeps information about Groups and Users in profiles.
The key information that RACF stores in the data set profile is
• Data set profile name.
• Profile owner, which can be either a RACF defined user or group.
• Security classification.
• Access list
• Userid to notify if an access violation occurs.
• A user data set is one where the high-level qualifier must match the user’s id.
• The user can protect their own data sets by defining a data set profile with the userid as the HLQ of the profile.
• A group data set is one where the high level qualifier matches the name of a RACF defined group.
• To define a GROUP data set profiles to RACF.
• You must have the SPECIAL attribute or group-SPECIAL attribute or at least CREATE authority in the group, or OPERATIONS or group-OPERATIONS attribute.
DATA SET AUTHORIZATION CHECKING.
• Whenever an attempt is made to access a data set, RACF gets called and checks the access authority to determine whether to allow to the requested resource or not.
• The first check done by RACF is to see if the user is marked as either trusted or privileged in the RACF started procedures table. In either case, the user is allowed access.
• RACF does not look at a data set profile to make this decision.
• A user is always allowed to access those data sets that have a high-level-qualifier equal to user’s userid.
• Finally, a user who has the OPERATIONS attribute will be allowed access at any level.
