Locking a PDS created by myself

Select-mf · New User Joined: 11 May 2007 Posts: 42 Location: bangalore

Hi,

I want to lock my personal PDS created by myself. Is there any option while creating a PDS or if its already created then some one can't open it.

Please let me know if there is any option to do it?

Thanks.

enrico-sorichetti · Posted: Thu Mar 26, 2009 10:31 pm

speak to Your security support

all depends on Your organization standards and rules

Craq Giegerich · Posted: Thu Mar 26, 2009 11:00 pm

Management is usually more impressed with what you develope and share rather than with what you develope and hide.

dick scherrer · Posted: Thu Mar 26, 2009 11:37 pm

Hello,

zhanghz · New User Joined: 15 Oct 2008 Posts: 6 Location: Singapore

If you can define your own security profile, you might be able to do what you want. But, as pointed out by others, why you need to do that?

Anuj Dhawan · Posted: Fri Mar 27, 2009 10:25 am

Hi,

Copy this PDS with Your RACF-ID (user ID) as HLQ and delete the other. . .

PS. I'm tired of this question . . .

enrico-sorichetti · Posted: Fri Mar 27, 2009 12:29 pm

repeating myself

speak to Your security support
and ask about Your organization standards and rules

Select-mf · New User Joined: 11 May 2007 Posts: 42 Location: bangalore

Hi,

Well, I asked this question just to make sure that somebody should not change the contents of my members in a PDS. I have created the PDS with my user id as a first qualifier but anybody can access it.

I thought there might be some option to lock a PDS while creating it through 3.2 utility or so.

Thanks.

Robert Sample · Posted: Fri Mar 27, 2009 11:13 pm

No, that's what the security package is for. If the concern about people changing your code is so strong, talk to the security group about setting up a specific profile for your PDS with universal access of read and update authority limited to you. But expect some resistance since it is a rare shop that would do this without finding out why it is needed first.

dick scherrer · Posted: Fri Mar 27, 2009 11:58 pm

Hello,

Suggest that if others are changing things in a pds that is not for common udate, it is a mangement problem and the issue is not locking the pds but rather changing the improper behavior. . .

Also, anything that matters should be backed up - either on the mainframe (preferably) or downloaded to a backup directory of your own.

Terry Heinze · Posted: Sat Mar 28, 2009 6:58 am

Most shops I've worked at allow read access to other developers, but update access to only the owner (HLQ). Are you sure others can update your PDS or only read it?

dbzTHEdinosauer · Posted: Sat Mar 28, 2009 1:07 pm

not all shops allow you to use your userid as the HLQ.

Anuj Dhawan · Posted: Sat Mar 28, 2009 2:44 pm

dbzTHEdinosauer · Posted: Sat Mar 28, 2009 5:33 pm

the fewer HLQ, the easier it is for the systems people.

small shops (by that i mean a mainframe for one (1) business) can afford the luxury of userid's as HLQ.

mainframes that are driving terminals in 10 or so countries, 40 or 50 business, you can forget it.

job numbers roll every other day...........