File permissions - Unicode vs. Non-unicode

[Former Member]

Hi all -

We have a program that creates a file in both our Unicode-enabled system (SRM) and our non-unicode system (ECC 6.0). Both are Unix servers.

It's very strange - on the Unicode box, it creates the file with permissions 660, but on the non-unicode box, file permissions are created as 666.

Does anyone know how to alter the system so that files are created with specific permissions with the 'OPEN DATASET' command in a Unicode environment?

The help is appreciated - thanks very much!

Abby

[Former Member]

Hi all -

We have a program that creates a file in both our Unicode-enabled system (SRM) and our non-unicode system (ECC 6.0). Both are Unix servers.

It's very strange - on the Unicode box, it creates the file with permissions 660, but on the non-unicode box, file permissions are created as 666.

Does anyone know how to alter the system so that files are created with specific permissions with the 'OPEN DATASET' command in a Unicode environment?

The help is appreciated - thanks very much!

Abby

[Former Member]

ECC6.0 is a Unicode system. Am not sure why you said non-unicode.

Thanks,

Kiran

[Former Member]

Hi Kiran -

Yes, new installs of ECC 6.0 are Unicode. Due to our contracts with SAP as a non-Unicode 4.6C system, we were allowed to remain non-Unicode when upgrading to ECC 6.0 a few years ago. Seemed easier at the time, but we probably should have just converted to Unicode at the time of the upgrade.

Thansk -

Abby

[Former Member]

Please contact BASIS team or post this question to BASIS forum. Looks like an authorisation issue.

Regards

Vivek

[Former Member]

This is a Basis Setting. Check transaction RZ11. I think Profile install/umask allows you to control this setting.

[Former Member]

Thanks for the information. Any further insight into exactly which parameter in RZ11 should be modified to handle this change?