Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(1 Rating)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

FAQ: What should umask be set to in order to use Operating System Profiles?
Answer

In order to use Operating system profiles, the umask should be set to 0 for the userid who starts the Informatica services.

Check if the umask is 0. This can be done by executing the command umask at the UNIX command prompt.
If the value is not zero, then set the value to zero by executing the command at the command prompt:

umask 0

The profile file of the user starting Informatica Services can also be modified by adding the above entry.
If the profile file is modified, then log back in as the user so that the profile is executed and the umask is set in the environment.

Once the umask is set to 0, restart the node.​


More Information

When a workflow is executed using OS profiles, the Integration Service will initiate the pmimpprocess to do a context switch to the OS profile user to execute certain tasks (session, event wait, command task). 
Any output file generated by these tasks (command and session) is owned by the OS profile user.

 

During an event wait on a file, the Integration Service communicates with the pmdtm using OS pipes (In UNIX, pipes are also treated as files). This pipe has to be open so that both users (the OS user Integration Service runs as, and the OS profile user that pmdtm runs as) can read from and write to it. The only way to do this is to set the umask to 0.

 

While trying to fetch the session log from the workflow monitor, the PCSF invokes the pmimpprocess to get the session log. The PCSF runs as the user that started the Informatica Services and the session log is created and therefore owned by the OS profile user. So, the session log has to be created with read-write permissions so that the PCSF can access the session log. Hence the need to set umask to 0.

 

However, if the umask is set to 0, then the target files created by the session have read-write permissions enabled for all (user, group and other). If this is a concern, then a post-session task should be executed to reset the permissions appropriately.


Starting with PowerCenter 9.6.0, the requirement of setting the umask to 000 has been removed. For instance, you can now set the umask to 077 for maximum security.
Note 
 

If changes are made to the umask setting, the Informatica services need to be restarted to take effect. 


Applies To
Product: PowerCenter
Problem Type:
User Type:
Project Phase:
Product Version: PowerCenter 8.5; PowerCenter 8.5.1; PowerCenter 8.6; PowerCenter 8.6.1; PowerCenter 9.0.1; PowerCenter 9.1.0; PowerCenter 9.6.1
Database:
Operating System: AIX; HP-UX; Redhat Linux; SUSE Linux ES; Solaris
Other Software:

Reference
For more information, see PowerCenter Administrator Guide > "Creating and Configuring the Integration Service" > "Using Operating System Profiles" > "Configuring Operating System Profiles"

Attachments

Last Modified Date:1/9/2019 6:02 PMID:32013
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)