Export from DB2 causes file to be created with permissions of 640

[SysProg]

I need some help with a problem I've encountered. I am a zLinux, WAS, and DB2 noob so please bear with me.

I am helping to support two WebSphere applications which utilize DB2 under zLinux. One application is for Europe and the other for the US. Each application has multiple WAS servers and HTTP servers backed by their own DB2 server. A script is run for each application that exports data from a z/OS-based DB2 database into a file on the zLinux DB2 server. Another script is then run to take that exported data and import it into the DB2 database on that zLinux server.

Up until November 3rd, the files created by the export scripts (European and US) were given permissions of 644. This allowed the import scripts to read the exported files. Since November 3rd, the files created on the US DB2 server are getting permissions of 640, which is causing the import script to fail. We have circumvented the problem by placing a chown command in the export script to change the permissions to 644.

I am looking for help in determining what caused the processing to change the permissions from 644 to 640. I want to change whatever caused this back to the way it was before and remove the chown command from the script. I added code to the script to display the umask at the beginning and end of the script. The umask is 022 in both cases.

I also determined that the 640 change is coming from DB2 somehow. If I create a new file within the script (beginning or end), it gets permissions of 644 as expected. The script and the file containing the SQL code were last modified in 2005.

• zLinux is SUSE (I don't remember the actual version but know that it is SLES 8).
• WAS is Version 6.0.1.
• DB2 is Version 8.1

The SQL code is:

export to /winxs/tmp/xrt001.exp
of IXF messages /winxs/tmp/xrt001_export.msg
SELECT *
FROM WCSDB2P.xrt001_vw
for read only with ur;
 

Thanks,
Harley

[xalo]

I have the same problem. Can anybody help ?