ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

When sosite is invoked from the command line, it hangs.


Article ID: 88911


Updated On:


CA Automic Applications Manager (AM)


When sosite is invoked from the command line, it hangs.


Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent



When the sosite file is invoked from the command line it hangs. If you hit enter it seems to finish but it still does not add the $AW_HOME.exec directory to the path.  If you attempt to start the Applications Manager processes with the alias set it will hang when the start scripts try to invoke the sosite file.


Make sure you don't have the Unix/Linux rm command aliased to:

rm -i

This can be set by default as a safety measure (to prompt before deletes to ensure you really want to delete) but it affects our software because it makes the rm command interactive.


Unset the rm command alias by issuing the following command logged in as the Applications Manager OS user:

unalias rm

If the alias is defined in the profile script, you will need to remove it from the script so that it will not be set for the AM user's login.