Did you know the CICS Explorer SDK not only includes a great development environment for Java, but also a remote debugger?
Quick guide to starting a debug session:
- Ensure the JVMSERVER resource used by your Java application is disabled, or not yet installed.
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.
- Enable the JVMSERVER resource.
- Install the BUNDLE resource that contains your CICS Java application.
- In CICS Explorer SDK, switch to the debug perspective via menu option Window > Open Perspective > Other > Debug > OK
- Select menu Run > Debug Configurations...
- 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).
- Debugging a Java application in the CICS Information Center has further advice on setting up debug support.
- Java support in CICS in the CICS Information Center describes how CICS supports Java, the new JVM server capabilities, and setup.
- Debug Java applications remotely with Eclipse in developerWorks is a nice, if now a bit dated, article about debug support in Eclipse.
- Options for -Xrunjdwp in the Oracle Java SE documentation.
- Running Java workloads with JVM servers and OSGi white paper.