Use these guidelines to create match criteria for a particular service or application. When the criteria are met, a live recording file is produced that you can play in your Eclipse IDE, for debugging purposes.
|Specify either CICS | JCL | WS | J2EE | IMS, depending on the type of application or service you want to debug.
|The CICS or IMS transaction to debug
|Only debug CICS or IMS transactions started from terminal <terminal-id>
|Only debug CICS or IMS transactions started by <user-id>
|Only debug CICS or IMS program <prog-id>
|Only debug the JCL job <job-name>
|Only debug the JCL step <step-name>
|Only debug the JCL job <job-number>
|Only debug the JCL program <program-name>
Specify the IP address of the client that will be used to request the web service you want to debug. Enter the address in the formxxx.xxx.xxx.xxx
|Web service only
Specify the fully qualified name of the service. This is formed by taking the name of the service and appending a hash character (#) for Web Services, or a dot (.) for J2EE, followed by the name of the operation that you want to debug. For example, if the service name for the web service that you deployed is http://tempuri.org/wmapserv, and the operation to be debugged is Read, the fully qualified service name is:
|Web service and J2EE
|Specify the enterprise server region running the services that you want to debug
For example: cobeslr type=WS server=ESDEMO servicename=http://tempuri.org/wmapserv#Read
cobeslr now passes the details to the enterprise server region specified by the server parameter.
A live recording file (.mfr file) is created in the System Directory of the enterprise server region when the criteria triggers the Live Recorder. For example, the example above triggers a recording when the client submits a request; CICS criteria might live record when a particular transaction is run; or JCL criteria might live record when a particular step is executed.
The match criteria remain in place, so the next time a match is met, it will also be Live Recorded. This could mean that many .mfr files get created in a short space of time (for example, a CICS transaction gets run multiple times). The name of the recording file includes the SEP, task, and PID details to ensure the file name is unique and helps you to identify a particular recording if many are created.
cobeslr remove type=WS server=ESDEMO servicename=http://tempuri.org/wmapserv#Read
Alternatively, you can remove the criteria from the Dyn.Debug ESMAC page.
Now that you have a live recording file, you can debug it in your IDE, as you would any other generated native COBOL live recording; see To debug a live recording.