File permissions for destination files

The file permissions for destination files written by Managed File Transfer destination agents are determined by the platform that the agent is running on.


Destination agents on z/OS, UNIX, and Linux platforms

We need to alter the value of umask on the system.

For example, assume that the default umask value for the user ID on your z/OS system is 0022.

When an MFT agent is running as this user, and writes a destination file, the file has the following permissions: 
 -rw-r--r--
If we change the umask value to, for example, 0006, by running the command 
umask 0006
and the agent restarted, then any destination files that the agent writes has the permissions: 
 -rw-rw----

Note, that we must restart the agent after you have run the umask command in order for the agent to pick up the new value.

Although z/OS is used as an example here, the same information applies to UNIX, and Linux platforms.


Destination agents on Windows

By default, permissions are inherited from a root folder to the files and sub-folders beneath it, though this inheritance can be turned off.

Your Windows administrator or domain administrator should review and manage the permissions and change them if necessary. They can use the icalcs command to view, add, update, and remove permissions.

Parent topic: Managed File Transfer administration reference


Related information