Was step 1 in the instructions successful ? Given that the error says that the console daemon, which should be started by casstart, is not active I suspect that that has not worked.

Hello Sanjay Singh,

Thank you for posting to the Micro Focus Community Site. As my colleague Gael Wilson has mentioned, this might indicate that the region was not successfully started.

Also, I want to note that the option for debugging that you are trying (using cassi -a)  is no longer supported in recent versions of the product. What version of Visual COBOL Development Hub are you using? You can display the detailed version information - in a Unix/Linux shell that has the COBOL environment is set - with the following command (note the V in the following is Upper Case):

cob -V

 And, what operating system and version are you using?

Finally, investigating issues with Enterprise Server can be complex, and might require gathering diagnostics that should not be shared on a public forum. For these reasons (and to get faster assistance) you might want to create a Support Case for this problem.

Hi Blair,

we are using Visual COBOL 6.0 and OS - RHEL 8.4

Hi Sanjay Singh,

Thanks for responding with your version info. The documentation you originally referenced was from Visual COBOL 4.0; the support for using the "cassi -a" option was removed in Visual COBOL 5.0. Since you are using Visual COBOL 6.0, here is a link to the documentation for that version with information about debugging Web Services from the command line.