IBM Mainframe Forum

1> HRECALL on the migrated datasets in production leads to access violation. Is there any alternative way to perform the same without leading to access violation?

2> If we want to find the properties of the datasets we generally do I infront of the dataset. In production this leads to access violation. Is there any alternative way to perform the same without leading to access violation?

1) NO
2) NO

Or
YES
YES

BUT... you will have to get your access changed

chinkump wrote:1> HRECALL on the migrated datasets in production leads to access violation. Is there any alternative way to perform the same without leading to access violation?

a) obtain the security required (READ at the minimum)
b) contact someone with authority to recall the dataset
c) submit a batch job via your production scheduler to recall the dataset, BR14 with a DISP=OLD may recall the dataset
..... these options come to mind off the top of my head

chinkump wrote:2> If we want to find the properties of the datasets we generally do I infront of the dataset. In production this leads to access violation. Is there any alternative way to perform the same without leading to access violation?

a) PF11 (scroll) LEFT of the 3.4 display to see the attributes....
b) prior to ENTER on the 3.4 menu select option 4 (TOTAL) from the initial view option
HTH

chinkump wrote:... 2> If we want to find the properties of the datasets we generally do I infront of the dataset. In production this leads to access violation. Is there any alternative way to perform the same without leading to access violation?

For a PDS it has to open the data set to get the directory stats, hence the access violation. For sequential data sets it can get the DCB and data set size attributes from the data set label in the VTOC, so there is no need to open the data set and I don't understand why you would get access violations.

These users thanked the author steve-myers for the post:

Peter_Mann (Wed Apr 03, 2013 11:54 pm)

I answered NO/NO because of the other topics started from the same
where he wants to prevent accessing to avoid getting the RACF warning

chinkump, site security policies are generally set to allow access to protected resources (such as data sets) to those who need that access and prevent access to those who do not need the access. You have posted on this forum a number of questions basically asking how to bypass security at your site. Either you are attempting to do things you have been asked to do (in which case your solution is to go to your manager and get your access changed to allow you to do things like HRECALL on data sets), or you are attempting to do things that you are not allowed to do (in which the site security policy is working precisely as it is intended to do).

Asking for help in breaking site security on a forum is NOT a career-enhancing move. You need to either talk to your manager to be granted more access, or stop trying to access things you are not allowed to do at your site, or find a different job. The number and tone of the posts you have made raise questions about your true goals and definintely you should be addressing your issues with your site security group and / or site maangement, not us.

from the post that was locked

Now it by mistake if I am trying to access the production dataset then violation does not occur and it pop ups as the message that I have set "You dont have authority to check for these datasets"

it seems to me that the TS is trying to be proactive, and warn about and then deny the access before it happens !

TS is still attempting to avoid site security. If too many warnings are issued by the site security package, that should be a red flag for the security group to review and possibly change the access. If those warnings don't occur, then the security group won't be aware of the need to change access levels. TS may have the best of intentions but the access violation messages serve a purpose in a well-designed site security system and there should not be a way to avoid getting them.

Besides, the topic started about HRECALL on a PRODUCTION data set -- so (1) the data set should be recalled (if at all necessary; most of my site's production data sets are used often enough not to be migrated) by the batch job using the data set, (2) there probably is someone authorized to recall the production data set, just not the TS, and (3) the site security group almost certainly wants to know who is attempting and failing to do anything with a production data set.

enrico-sorichetti wrote:from the post that was locked

Now it by mistake if I am trying to access the production dataset then violation does not occur and it pop ups as the message that I have set "You dont have authority to check for these datasets"

it seems to me that the TS is trying to be proactive, and warn about and then deny the access before it happens !

Thanks Enrico. This time my requirement is very clear
I am trying to be proactive, and warn about and then deny the security violation happens !

Thanks,
Chinkump