Hello Gobi,
wow, it's back to the futur!! well back to the past...
Ok... then first thing first.
What happened? Did it work before not starting anymore? What are the changes that happened that makes CMOD not working anymore? Something to do with an upgrade of your unix server?
Now to get more trace, you must modify your ars.cfg to be more like that:
ARS_TMP=/sbcimp/dyn/data/RAR/OD_App1/temp
ARS_PRINT_PATH=/tmp
ARS_TRACE_SETTINGS=/opt/ondemand/config/FILENAME
And the file called /opt/ondemand/config/FILENAME can be like that (exactly what you did):
[TRACE]
COMPONENT_LEVEL=FFFFFFFFFFFFFFFFFFFFFF
#TRACE_FILE=ARCHIVE.trace.log
TRACE_FILE=ARCHIVE.trace.log
TRACE_FORMAT=TEXT
APPEND=0
MAX_LOG_SIZE=0
One of the main error I get when CMOD cannot start are the following:
- Problem of permissions somewhere -> Check all the path that CMOD needs to access
- Problem with TSM, check that you don't have any error (again permissions) with TSM
- Problem with the DB, you need to ensure that your DB is not corrupted and working, and that everything is setup correctly, that the CMOD instance owner has dba rights on the database
What can help me from time to time, is the following, I change the file /opt/ondemand/bin/arslog to have something like that:
#!/bin/ksh
echo "$@" >> /tmp/myOD.log
exit 0
That way I can see if CMOD writes something in the System Log, which could help me to solve the problem.
Another thing that I do, even if it doesn't work always, is to use (Solaris/AIX) the "truss" command when running arssockd. In Linux you must use the command "strace". Then look for any problem with permissions, etc...
Hope that helps a little bit.