APAR status
Closed as documentation error.
Error description
On a system where environment variable MQSI_SET_DFE_UMASK has been incorrectly set to the actual required file permissions, for example 775, rather than the mask value that controls the file permissions, the integration server may report deployment failures or fail to start due to directory permission problems. Message BIP2113E is logged reporting the directory path that could not be accessed. For example: BIP2113E: Integration node internal error: diagnostic information 'Permission denied', '13', '/var/mqsi/components/integrationNodeName/integrationServerUUID/ config/JAR/rollBackChangeList.txt'. BIP2113E: Integration node internal error: diagnostic information 'Permission denied', '13', '/var/mqsi/components/integrationNodeName/integrationServerUUID/ config/applicationUUID/Adapter'. This is due to new directories being created by a deployment operation with permissions that allow read and write, but not execute. Additional Symptom(s) Search Keyword(s):MQSI_SET_DFE_UMASK, BIP2113E, file permissions,
Local fix
Correct the MQSI_SET_DFE_UMASK value and ensure all integration node workpath directories have 'user' permissions set to 'rwx.'
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus V9.0,V10.0 and IBM App Connect Enterprise V11.0 using the FileOutput node. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: On a system where environment variable MQSI_SET_DFE_UMASK has been incorrectly set to the actual required file permissions, for example 775, rather than the mask value that controls the file permissions, the integration server may report deployment failures or fail to start due to directory permission problems. Message BIP2113E is logged reporting the directory path that could not be accessed. For example: BIP2113E: Integration node internal error: diagnostic information 'Permission denied', '13', '/var/mqsi/components/integrationNodeName/integrationServerUUID/ config/JAR/rollBackChangeList.txt'. BIP2113E: Integration node internal error: diagnostic information 'Permission denied', '13', '/var/mqsi/components/integrationNodeName/integrationServerUUID/ config/applicationUUID/Adapter'. This is due to new directories being created by a deployment operation with permissions that allow read and write, but not execute.
Problem conclusion
The documentation for new files created by the FileOutput node (ac55160_.htm) will be updated to clarify the use of the MQSI_SET_DFE_UMASK environment variable. On Linux, UNIX and z/OS systems, the permissions that new files are created with are determined by the umask value. The minimum permission required by the product for all files (including internal configuration files) is for user and group to have read/write access (660), and therefore by default the product sets the umask to 0006. The following environment variables are available to override this default umask of 0006: MQSI_SET_DFE_UMASK=nnnn Used to override the umask for new files created by integration server processes. MQSI_UMASK_COPY If this environment variable is set (to any value), and MQSI_SET_DFE_UMASK is not set, the umask value will be copied from the user environment umask setting. Note: When overriding the umask value, care must be taken to ensure that directories and files created by the product have a minimum permission of 660 and 770 respectively. A good understanding of umask is needed before choosing to use the overrides. If the permissions of newly created directories and files is restricted too much, the product may not be able to restart successfully.
Temporary fix
Comments
APAR Information
APAR number
IT20993
Reported component name
INTEGRATION BUS
Reported component ID
5724J0530
Reported release
900
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-12
Closed date
2019-12-24
Last modified date
2019-12-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020