The Batch Interface › SYSIN01 Parameters › General SYSIN01 Parameters › UMASK

UMASK

The file permissions that are removed from the XCOM default file or directory permissions for USS files or directories. UMASK is used only when a file or directory is being created.

Range: 000 to 777

Default: 022

On z/OS systems, the XCOM default file permission is 666, which means:

• Allow the owner of the file to read and write the file.
• Allow members of the owners group to read and write the file.
• Allow all other users read and write the file.

File permissions on USS files are implemented the same way as file permissions are on UNIX systems. The three basic permissions for each of the categories are read, write, and execute, commonly seen as rwx rwx rwx.

If each of these characters (r, w, x) is considered as a bit, then the possible value ranges are as follows:

• 000 to 111 in binary
• 0 to 7 in hex

So the default permissions of 666 (110 110 110) mean allow read and write to everyone, but not execute.

The UMASK value identifies the permissions that you want to remove from the default (666). If you remove 022 (000 010 010) from 666, what remains is 644. 644 means:

• Allow the owner of the file to read and write the file.
• Allow members of the owners group and all other users to read, but not write.

Notes:

• For directories—CA XCOM Data Transport sets permissions for a created directory to 7xx, no matter what owner UMASK value was specified. Group and other permissions, of xx, represent the permissions with the specified UMASK removed.
• For files – While the file is being transferred, CA XCOM Data Transport sets permissions for a created file to 6xx. Where xx represents the permissions with the specified UMASK removed. After the transfer has been completed, CA XCOM Data Transport sets the owner permission with the specified UMASK removed.