Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

UNIX permissions - open dataset for output

Former Member
0 Kudos

in abap when using open dataset for output my files are being created but as 660.

what control this?

the owner is kp1adm:sapsys

i need read by all.

basis checked and the kp1adm umask is 022

not sure what is controlling this

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Probably a longshot, but you might want to check to see if a shell is being created and a logon script (e.g. .cshrc) executed while the file is created. There could be a umask command in the logon script.

8 REPLIES 8

Former Member
0 Kudos

Probably a longshot, but you might want to check to see if a shell is being created and a logon script (e.g. .cshrc) executed while the file is created. There could be a umask command in the logon script.

nkr1shna
Contributor
0 Kudos

Hi,

Whether you are referring 660 in UNIX read/write/execute permissions for the file or folder?.

Based on your response I will think of possible solution.

Best Regards,

Krishna

Former Member
0 Kudos

The folder is drwxrwxrwx

Files being created in there are:

-rw-rw---- 1 kp1adm sapsys

0 Kudos

Hi,

Please check with your basis consultant whether your user (unix username that appears in your ls command) is part of any group. Looks like he is not part of group, hence you are not getting any read/write/execute permission.

Let me know if you have further questions.

Best Regards,

Krishna

0 Kudos

Hi Wayne,

Unix file permissions goes this way

Owner Group Others

read/write/execute read/write/execute read/write/execute.

In your case you are not getting any values for "Others". Please check with your basis consultant why it is not populating. Mostly he will get into UNIX level and can resolve your issue.

Best Regards,

Krishna

Former Member
0 Kudos

Basis checked kp1adm and umask is 022.

Not aware of what else would control this

0 Kudos

HI Wayne,

Can you please add following code after your file has been created.

CONCATENATE 'chmod ugo=rw ' lc_filename

INTO lc_chmod SEPARATED BY space.

CALL 'SYSTEM' ID 'COMMAND' FIELD lc_chmod.

Best Regards,

Krishna

Former Member
0 Kudos

Thanks. I'd rather try and find the true reason as I dont have this problem in other systems.