Scripts Cannot Be Started After Deployment 

Problem 1

After deployment of file system SCAs on a UNIX system, some UNIX scripts cannot be started.

Possible Reasons

UNIX scripts do not have executable rights.

Solution

Add executable rights to each UNIX script using the UNIX command according to your UNIX system.

For example, chmod 755 <Script name>.

Problem 2

After deployment on an IBM eServer iSeries system, the go script cannot be started.

Possible Reasons

The go script does not have executable rights.

Solution

Add executable rights to the go script in Qshell by executing the following commands:

QSH

cd /usr/sap/<SID>/<Central instance name>/j2ee/JSPM

mv go go_cp

cp go_cp go

chmod 755 go

rm go_cp