Problem:

After a server reboot, the following Enterprise Server processes are evident. Is this what should be expected (in the case of ESDEMO)?

es_admin 17102 17101  0 Jan11 ?        00:00:00 casmgr32 /rESDEMO /m127.0.0.1:86

es_admin 17103 17101  0 Jan11 ?        00:00:00 casjcp32 /rESDEMO

es_admin 17104 17101  0 Jan11 ?        00:00:00 cassi32 /rESDEMO -rESDEMO

es_admin 17105 17101  0 Jan11 ?        00:00:00 cassi32 /rESDEMO -rESDEMO

es_admin 17106 17101  0 Jan11 ?        00:00:00 /opt/microfocus/cobol/bin/mfcs32 -nESDEMO-m127.0.0.1:86 -l/var/mfcobol/es/ESDEMO -d -i01 -C

root     19323 19283  0 08:28 pts/2    00:00:00 grep 17101

Resolution:

These are normal when you start a server. When you manually run 'casstart' or press the server 'START' button from within Enterprise Server Administration, you initiate the following:

casstart, which starts cascd32, cascd32 starts casmgr32

cascd32 then starts cassi32 x n (number of sep's) and mfcs32 (mfcs32 is the Communications Manager)

casjcp32 is the Journal control process

A server would start automatically after the reboot if you check "Restore on Startup" field in the "Configure, Options" page.