View previous topic :: View next topic
|
Author |
Message |
Hari Hara Krishnan N
New User
Joined: 16 Mar 2007 Posts: 5 Location: Chennai
|
|
|
|
How to prevent the users from opening the Common librabies such as the Copy libraries in the edit mode? |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
Ask the security people to make it READ only except for authorised users. |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
If you have read access to a dataset (RACF ) you can still EDIT it. You just can't save the changes |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
When you open a dataset in EDIT it will be opened in UPDATE.
If you do not have update authority the access request would be denied. |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
I hate to disagree but you can edit a dataset if you only have READ access you just can't change it . Try it |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
One word of qualification this is for PDS datasets only PDSE's are handled differently |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
Damn, the way RACF has the different sections grouped, I can't add extra profiles and change the access to test this.
Until such time as I can, I shall have to let it rest. |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
To save you testing the following is a quote from the IBM lab.
When editing a PDS under ISPF, ISPF issues an
OPEN for input. If the user issues the SAVE command (or END after
making changes), ISPF CLOSES the data set, and issues an OPEN for
UPDATE. At that point, a user with READ access will fail with a 913.
ISPF opens the file for output because a PDSE may be multiply open for output. SO ISPF has to open the data set for output before displaying the data. |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
Sorry Hari we forgot about your original question . The answer would appear to be that if the user has read access to the library and it is a PDS you cannot stop him editing it. You could convert the dataset to a PDSE and then with access Read the user would no longer be able to EDIT it |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
Nice one Nevil |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
I may be missing something (and i'm sure someone will set me straight if i am ), but why is there a concern about editing a member if the changes cannot be saved? If someone has read access, they can easily copy the member to their own pds and "really" edit the menber.
Is the goal to prevent any editing on the member or just to protect the member in the "Common Library"? |
|
Back to top |
|
|
|