Using EJB trace and serviceability commands

You might want to trace an EJB request when you are trying to diagnose hanging or failing requests, or when you need to be able to uniquely identify all transactions associated with a single request in order to monitor that activity or perhaps for accounting purposes.

The main problems when trying to diagnose hanging or failing requests when an EJB logical server comprises multiple CICS regions are that you have to determine:
The system programming interface (SPI) commands INQUIRE WORKREQUEST and SET WORKREQUEST enable you to: Each request shows:
For more information about these commands see:

The INQUIRE and SET WORKREQUEST commands are only available for IIOP tasks.

WorkRequests associated with RequestReceivers are not included, they are very lightweight and all this information is available in the RequestProcessor. A RequestReceiver may process more that one request per instance and may have left the system long before the request has completed.

When you interrogate a logical server using the CPSM WUI, you have a single screen displaying all WorkRequests in the server

You are able with these commands to purge a RequestProcessor in a manner similar to purging a task from the CEMT INQ TASK list.