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
 

 

Preventing users from opening Common Lib in edit mode

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF
View previous topic :: :: View next topic  
Author Message
Hari Hara Krishnan N

New User


Joined: 16 Mar 2007
Posts: 5
Location: Chennai

PostPosted: Tue Mar 20, 2007 11:40 am    Post subject: Preventing users from opening Common Lib in edit mode
Reply with quote

How to prevent the users from opening the Common librabies such as the Copy libraries in the edit mode?
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: Tue Mar 20, 2007 1:32 pm    Post subject:
Reply with quote

Ask the security people to make it READ only except for authorised users.
Back to top
View user's profile Send private message
nevilh

Active User


Joined: 01 Sep 2006
Posts: 258

PostPosted: Tue Mar 20, 2007 6:07 pm    Post subject:
Reply with quote

If you have read access to a dataset (RACF ) you can still EDIT it. You just can't save the changes
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: Tue Mar 20, 2007 6:18 pm    Post subject:
Reply with quote

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
View user's profile Send private message
nevilh

Active User


Joined: 01 Sep 2006
Posts: 258

PostPosted: Tue Mar 20, 2007 6:50 pm    Post subject:
Reply with quote

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
View user's profile Send private message
nevilh

Active User


Joined: 01 Sep 2006
Posts: 258

PostPosted: Tue Mar 20, 2007 6:56 pm    Post subject:
Reply with quote

One word of qualification this is for PDS datasets only PDSE's are handled differently
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: Tue Mar 20, 2007 7:12 pm    Post subject:
Reply with quote

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
View user's profile Send private message
nevilh

Active User


Joined: 01 Sep 2006
Posts: 258

PostPosted: Tue Mar 20, 2007 7:22 pm    Post subject:
Reply with quote

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
View user's profile Send private message
nevilh

Active User


Joined: 01 Sep 2006
Posts: 258

PostPosted: Tue Mar 20, 2007 7:26 pm    Post subject:
Reply with quote

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
View user's profile Send private message
expat

Global Moderator


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

PostPosted: Tue Mar 20, 2007 7:33 pm    Post subject:
Reply with quote

Nice one Nevil
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Mar 20, 2007 7:57 pm    Post subject:
Reply with quote

Hello,

I may be missing something (and i'm sure someone will set me straight if i am icon_smile.gif ), 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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Mainframe Opening in Chennai ( 2 to 4... muralikrishnan_new Mainframe Jobs 0 Tue Jul 18, 2017 2:20 pm
No new posts Getting error while opening a variabl... apandey1 COBOL Programming 5 Fri May 05, 2017 12:22 pm
This topic is locked: you cannot edit posts or make replies. Mainframe Opening in Allianz India- T... Rajesh Gopinathan Mainframe Jobs 0 Wed Apr 19, 2017 11:33 am
No new posts Edit large number of datasets (QSAM) zh_lad TSO/ISPF 3 Tue Apr 04, 2017 6:08 pm
No new posts Mass comment and edit elixir1986 IBM Tools 3 Thu Mar 02, 2017 10:09 pm


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