Did you know the CICS Explorer not only includes a great development environment for Java, but also a remote debugger?
Quick guide to starting a debug session:
  1. Ensure the JVMSERVER resource used by your Java application is disabled, or not yet installed.
  2. Add the following two lines to the JVM profile.

    Change the "address=" option to a IP port number on z/OS that is not already being used, the default CICS region userid is authorised to open, and your workstation can connect to. A link describing the options for runjdwp – run Java Debug Wire Protocol –  is in the references section below.

  3. Enable the JVMSERVER resource.
  4. Install the BUNDLE resource that contains your CICS Java application.
  5. In CICS Explorer, switch to the debug perspective via menu option Window > Open Perspective > Other > Debug > OK
  6. Select menu Run > Debug Configurations…
  7. Create a new entry under "Remote Java Application", filling in the Project (your OSGi plug-in project that contains the source to debug), Host and Port (your z/OS system host name, and port entered in step 2).


  1. Click "Debug" to start the debug session.
    If a "Failed to connect to remote VM" message is shown, check the JVMSERVER resource is enabled and that your workstation can reach the z/OS host.
  2. Switch to the Plug-in perspective, navigate to the Java class you need to debug and edit it.
  3. Double click in the margin to create a break point. Each break point appears as a blue dot in this margin.
  4. Run your CICS Java application.
  5. When the break point hits, CICS Explorer will switch automatically to the Debug perspective and you can now step through your code, watch variables etc. If you hover the mouse over a variable in the source a popup window will show you the current value.




Once you have this working, you may also want to look at the free  IBM Monitoring and Diagnostic Tools for Java (aka IBM Health Center) that can be used to profile and tune your CICS Java application. Add "-Xhealthcenter:port=27509" (replacing the port number) to your JVM profile.





Join The Discussion

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.