cannot open executable job file

jungle · Post by **jungle** » Tue Dec 16, 2003 11:04 am

Tell me more please... i'd like to understand exactly what is the matter.

I have read some lines of the service's startup script and, as you said, only the entries in the form of xyz=123 present in dsenv are loaded in the environment.
But...

In /etc/profile umask is 022
In /home/dsadm/.profile umask is not present

Why then RT_CONFIG's files permissions are compliant with umask 002?

kcbland · Post by **kcbland** » Tue Dec 16, 2003 11:19 am

Do us a favor and type in "SORT-ITEM RT_CONFIG1344" and paste the results. If the file is corrupted, you'll get a message saying so. Otherwise, you'll get a mostly text dump of the contents.

For the umask, you'll want 002, otherwise same-group users don't have execute or subdirectory access rights.

jungle · Post by **jungle** » Tue Dec 16, 2003 11:25 am

The result is:

Unable to open "RT_CONFIG1344" file

kcbland · Post by **kcbland** » Tue Dec 16, 2003 11:34 am

do a "CT VOC RT_CONFIG1344" and paste the results

jungle · Post by **jungle** » Tue Dec 16, 2003 11:47 am

Here is the result:

RT_CONFIG1344
0001 F Ardent DataStage Job File
0002 RT_CONFIG1344
0003 D_RT_CONFIG

kcbland · Post by **kcbland** » Tue Dec 16, 2003 11:53 am

You should be able to do the following from your TCL prompt:

Code: Select all

>SH
$ pwd
/var/opt/datastage/yourproject
$ cd RT_CONFIG1344
$ ls -al
total 136
drwxrwxr-x   2 ardent   ardent        96 Dec  7 00:35 .
drwxrwxr-x 2071 dsadm    ardent     51200 Dec 16 12:47 ..
-rw-rw-r--   1 ardent   ardent         0 Dec  7 00:35 .Type30
-rw-rw-r--   1 ardent   ardent      8192 Dec 16 12:52 DATA.30
-rw-rw-r--   1 ardent   ardent     10240 Dec 12 14:47 OVER.30

Somewhere in here things go wrong, so please try this step and see where a message appears.

jungle · Post by **jungle** » Tue Dec 16, 2003 12:00 pm

i already did that thing... but i have done it again:

h3mis279:/app/Ascential/DataStage/interface-> pwd
/app/Ascential/DataStage/interface
h3mis279:/app/Ascential/DataStage/interface-> cd RT_CONFIG1344
h3mis279:/app/Ascential/DataStage/interface/RT_CONFIG1344-> ls -al
total 262
drwxrwxr-x 2 dsadm dsadm 512 Nov 27 12:36 .
drwxrwxr-x 4551 dsadm dsadm 118272 Dec 16 18:27 ..
-rw-rw-r-- 1 dsadm dsadm 0 Nov 27 12:36 .Type30
-rw-rw-r-- 1 dsadm dsadm 0 Nov 27 12:46 DATA.30
-rw-rw-r-- 1 dsadm dsadm 2048 Nov 27 12:36 OVER.30
h3mis279:/app/Ascential/DataStage/interface/RT_CONFIG1344->

If you think it's a thing that could be done, let's talk using a messenger.

kcbland · Post by **kcbland** » Tue Dec 16, 2003 12:08 pm

Sent you a private message.

Teej · Post by **Teej** » Tue Dec 16, 2003 1:59 pm

jungle wrote:In /etc/profile umask is 022
In /home/dsadm/.profile umask is not present

DataStage requires full access for all users intending to use the product. For security purpose, you should limit your users to those authorized to use DataStage within /etc/group. However, both dsadm and users on that group should have full access - 770 at the very least.

You could umask up to 007, but not further.

Ken is right, put the umask on the .rc file. In fact, it is already there by default for 6.x installation, just disabled (#umask 002).

-T.J.