permission denied on ./install/install.rex z/os 1.9 only
permission denied on ./install/install.rex z/os 1.9 only
i am trying to install Co:Z 1.0.4 on a new z/os 1.9 system which has not yet been fully customized. I keep getting the following error i do not get under z/os 1.7. all of the permissions appear to be set.
any ideas?
thanks in advance
Do you agree to the above license terms? [yes or no]
yes
Enter home install directory [/usr/lpp/coz] :
/u/eileen/j1x/cox
/u/eileen/j1x/cox is an existing non-empty directory, reuse it? [y/n] :
y
./install/install.rexx: ./coz-1.0.4.bin 107: FSUM9209 cannot execute: reason cod
e = 5b4c0002: EDC5111I Permission denied.
$
________
SIMMERING
any ideas?
thanks in advance
Do you agree to the above license terms? [yes or no]
yes
Enter home install directory [/usr/lpp/coz] :
/u/eileen/j1x/cox
/u/eileen/j1x/cox is an existing non-empty directory, reuse it? [y/n] :
y
./install/install.rexx: ./coz-1.0.4.bin 107: FSUM9209 cannot execute: reason cod
e = 5b4c0002: EDC5111I Permission denied.
$
________
SIMMERING
Last edited by cscs010 on Sat Feb 12, 2011 2:20 pm, edited 1 time in total.
it is only the install directory it stops on, and actually does put something into it. the other stuff gets created.
and this error only happens on the z/os 1.9 system, not z/os 1.7.
there is also a RACF error with this - does this mean that my id is not allowed to execute? i can execute other things.
some of the RACF profiles may be different in the z/os 1.9 system.
ICH408I USER(EILEEN ) GROUP(CSCCICS ) NAME(EILEEN BARKOW 3585 ) 659
./install/install.rexx
CL(FSOBJ ) FID(01E9C8C6E2F0F1000F070000352B0000)
INSUFFICIENT AUTHORITY TO OPEN
ACCESS INTENT(--X) ACCESS ALLOWED(OWNER RW-)
EFFECTIVE UID(0420050912) EFFECTIVE GID(0420000000)
ICH408I USER(EILEEN ) GROUP(CSCCICS ) NAME(EILEEN BARKOW 3585 ) 659
./install/install.rexx
CL(FSOBJ ) FID(01E9C8C6E2F0F1000F070000352B0000)
INSUFFICIENT AUTHORITY TO OPEN
ACCESS INTENT(--X) ACCESS ALLOWED(OWNER RW-)
EFFECTIVE UID(0420050912) EFFECTIVE GID(0420000000)
$ ls -l coz
total 6960
-rw-r--r-- 1 EILEEN CIXGR1 570 Jan 24 17:06 LICENSE
-rw-r--r-- 1 EILEEN CIXGR1 135 Jan 24 17:06 README
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 bin
-rwxr-xr-x 1 EILEEN CIXGR1 3504729 Jan 29 09:48 coz-1.0.4.bin
drwxr-xr-x 4 EILEEN CIXGR1 8192 Jan 24 17:06 doc
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 install
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 loadmodules
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 sampjcl
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 testjcl
$
$ ls -l coz/install
total 16
-rw-r--r-- 1 EILEEN CIXGR1 4943 Jan 24 17:06 install.rexx
$
________
Digital Vaporizer
and this error only happens on the z/os 1.9 system, not z/os 1.7.
there is also a RACF error with this - does this mean that my id is not allowed to execute? i can execute other things.
some of the RACF profiles may be different in the z/os 1.9 system.
ICH408I USER(EILEEN ) GROUP(CSCCICS ) NAME(EILEEN BARKOW 3585 ) 659
./install/install.rexx
CL(FSOBJ ) FID(01E9C8C6E2F0F1000F070000352B0000)
INSUFFICIENT AUTHORITY TO OPEN
ACCESS INTENT(--X) ACCESS ALLOWED(OWNER RW-)
EFFECTIVE UID(0420050912) EFFECTIVE GID(0420000000)
ICH408I USER(EILEEN ) GROUP(CSCCICS ) NAME(EILEEN BARKOW 3585 ) 659
./install/install.rexx
CL(FSOBJ ) FID(01E9C8C6E2F0F1000F070000352B0000)
INSUFFICIENT AUTHORITY TO OPEN
ACCESS INTENT(--X) ACCESS ALLOWED(OWNER RW-)
EFFECTIVE UID(0420050912) EFFECTIVE GID(0420000000)
$ ls -l coz
total 6960
-rw-r--r-- 1 EILEEN CIXGR1 570 Jan 24 17:06 LICENSE
-rw-r--r-- 1 EILEEN CIXGR1 135 Jan 24 17:06 README
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 bin
-rwxr-xr-x 1 EILEEN CIXGR1 3504729 Jan 29 09:48 coz-1.0.4.bin
drwxr-xr-x 4 EILEEN CIXGR1 8192 Jan 24 17:06 doc
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 install
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 loadmodules
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 sampjcl
drwxr-xr-x 2 EILEEN CIXGR1 8192 Jan 24 17:06 testjcl
$
$ ls -l coz/install
total 16
-rw-r--r-- 1 EILEEN CIXGR1 4943 Jan 24 17:06 install.rexx
$
________
Digital Vaporizer
Last edited by cscs010 on Sat Feb 12, 2011 2:20 pm, edited 1 time in total.
Eileen -
The permissions on the ./install/install.rexx file should be 755 - yours is 644.
It looks like the permissions are being changed by your system when the file is unloaded.
You can see the permissions on all of the files as we ship them using this:
tail +113 coz-1.0.4.bin | pax -v | more
You should see that ./install/install.rexx is 755. I'm not sure why your system is changing it when it is unloaded.... maybe there is some RACF rule that I don't understand affecting it.
As a workaround, you can try this to complete the installation:
chmod 755 ./install/install.rexx
./install/install.rexx <COZ_HOME>
(Changing <COZ_HOME> to your COZ install directory)
The permissions on the ./install/install.rexx file should be 755 - yours is 644.
It looks like the permissions are being changed by your system when the file is unloaded.
You can see the permissions on all of the files as we ship them using this:
tail +113 coz-1.0.4.bin | pax -v | more
You should see that ./install/install.rexx is 755. I'm not sure why your system is changing it when it is unloaded.... maybe there is some RACF rule that I don't understand affecting it.
As a workaround, you can try this to complete the installation:
chmod 755 ./install/install.rexx
./install/install.rexx <COZ_HOME>
(Changing <COZ_HOME> to your COZ install directory)
i was able to finish the install by manually setting the permissions on the install library and running ./install/install.rexx /u/eileen/j1x/coz as you suggested.
thanks for the info about the umask command - i will keep it in mind for the future.
But we just started bringing up z/os 1.9 so does this mean that the umask setting is different from what we have for z/os 1.7 - the problem did not happen with z/os 1.7
________
Disability insurance advice
thanks for the info about the umask command - i will keep it in mind for the future.
But we just started bringing up z/os 1.9 so does this mean that the umask setting is different from what we have for z/os 1.7 - the problem did not happen with z/os 1.7
________
Disability insurance advice
Last edited by cscs010 on Sat Feb 12, 2011 2:20 pm, edited 1 time in total.
it looks like umask did not fix the error - and i do not see any more RACF errors about this either.
$ cd cox
$
$ ls
coz-1.0.4.bin
$ umask 000 ./coz-1.0.4.bin
$ ./coz-1.0.4.bin
Enter home install directory [/usr/lpp/coz] :
/u/eileen/j1x/cox
/u/eileen/j1x/cox is an existing non-empty directory, reuse it? [y/n] :
y
./install/install.rexx: ./coz-1.0.4.bin 107: FSUM9209 cannot execute: reason cod
e = 5b4c0002: EDC5111I Permission denied.
________
ACURA ARX-01 SPECIFICATIONS
$ cd cox
$
$ ls
coz-1.0.4.bin
$ umask 000 ./coz-1.0.4.bin
$ ./coz-1.0.4.bin
Enter home install directory [/usr/lpp/coz] :
/u/eileen/j1x/cox
/u/eileen/j1x/cox is an existing non-empty directory, reuse it? [y/n] :
y
./install/install.rexx: ./coz-1.0.4.bin 107: FSUM9209 cannot execute: reason cod
e = 5b4c0002: EDC5111I Permission denied.
________
ACURA ARX-01 SPECIFICATIONS
Last edited by cscs010 on Sat Feb 12, 2011 2:20 pm, edited 1 time in total.
i get the same error.
the cox directory was empty when i started and the coz..bin file was moved elsewhere.
$ umask 000
$ ./coz-1.0.4.bin
Do you agree to the above license terms? [yes or no]
yes
Enter home install directory [/usr/lpp/coz] :
/u/eileen/j1x/cox
./install/install.rexx: ./coz-1.0.4.bin 107: FSUM9209 cannot execute: reason cod
e = 5b4c0002: EDC5111I Permission denied.
$
________
Trichomes
the cox directory was empty when i started and the coz..bin file was moved elsewhere.
$ umask 000
$ ./coz-1.0.4.bin
Do you agree to the above license terms? [yes or no]
yes
Enter home install directory [/usr/lpp/coz] :
/u/eileen/j1x/cox
./install/install.rexx: ./coz-1.0.4.bin 107: FSUM9209 cannot execute: reason cod
e = 5b4c0002: EDC5111I Permission denied.
$
________
Trichomes
Last edited by cscs010 on Sat Feb 12, 2011 2:20 pm, edited 1 time in total.
Thanks - I guess that umask isn't the problem.
As it stands, you have a workaround by manually chmod and executing install.rexx... but we don't really understand why the permissions aren't getting restored.
I think that we will probably add a chmod in our install script, until we can figure it out.
Thanks for reporting this.
As it stands, you have a workaround by manually chmod and executing install.rexx... but we don't really understand why the permissions aren't getting restored.
I think that we will probably add a chmod in our install script, until we can figure it out.
Thanks for reporting this.
once again, this is a new z/os 1.9 system and it has a long way to go.
since the problem did not occur with z/os 1.7, it is likely that something in the system or RACF is causing the permissions to get changed.
i will take this up with the RACF group and thank you for your help.
________
Spice weed
since the problem did not occur with z/os 1.7, it is likely that something in the system or RACF is causing the permissions to get changed.
i will take this up with the RACF group and thank you for your help.
________
Spice weed
Last edited by cscs010 on Sat Feb 12, 2011 2:20 pm, edited 1 time in total.