Administering the License Management Facility

To use a debug service execution process for Enterprise Server debugging

Start the enterprise server under your own user id. The simplest way to do this is by using the casstart command. For example,

casstart /rESDEMO

Note: The /r option specifies the enterprise server that you want to start.

Start a debug service execution process (SEP) on the server by using the cassi command with the /a option. For example,

cassi /a /rESDEMO

If you want to debug a JCL application, you must also use the /b option to specify the job classes that the debug SEP will be able to run. For example, cassi /a /bABC /rESDEMO where ABC is the list of classes.

The debug SEP starts an associated Net Express debugging session.

If you have not already done so, deploy the service or application to the server.

To deploy a service interface using the Deploy tool

Note: Please make sure to include the .idy files for the application in the set of files that you deploy.

If your program is a service (Web Service or J2EE), as opposed to a CICS or JCL application, you will need to create a client program to submit requests for that service.

To generate a COBOL client from a Web service interface

Start the service or application on your enterprise server. How you do this depends on what type of application it is.

For example:

For a Web Service, you can run the client program and enter some input.
For a CICS application, you can start a TN3270 terminal session and run your transaction.

When the service or application starts, the enterprise server will attach your Net Express debugging session to it.

You can now step through the deployed service in the usual manner.

Notes:

You have to start the enterprise server using casstart so that you can start a debug service execution process using cassi /a. This is not possible if you start the enterprise server from Enterprise Server Administration with the Directory Server running as a system service.
When the end of the program is reached, usually the Debugger session remains open and any further services or applications that run in the debug service execution process are also debugged. However, the program being debugged might cause the service execution process to terminate. In this case the Debugger session ends but the new IDE remains open until you close it.
When you have finished debugging, you can close the debug service execution process using ESMAC; see the section Service Execution Processes in the chapter Administrating Servers Using ESMAC in your Configuration and Administration Guide
Since the debug session is not associated with a project, you cannot save breakpoints or monitors between sessions.
If you move the sources of the application to a different location in order to debug, remember to set the COBCPY environment variable to point to the new location. Similarly, you may also need to set COBIDY to point to the location of the .idy files.

Related Topics: