Lets take a look how we can leverage a debug profile to debug a batch application.
First lets create a non-CICS profile by clicking on the toolbar button:
The editor shows us some general information for each section in the editor, and I can choose to hide that by clicking on the
Hide Hints link.
Since I have the Debug Profile Service running, the location of my profile is automatically determined:
The editor shows that I have one error, and when I hover over the message it shows I am missing a mandatory field:
I scroll until I see the field in error:
I add the module I want to debug:
After I’ve specified the values, I click on the
Save and Activate for Debug button
I am almost ready to go! I just need to modify my JCL, so I open it in the JCL editor, and add the simplified TEST runtime option (see
Simple TEST option for more details):
And submit my JCL. I like to use the context menu in the editor:
I can now see my debug session start up:
After I finish my debug session, I can now inactivate my profile in the z/OS Debugger Profiles view:
And when I resubmit my JCL, even though the simple TEST option remains, the debug session does not start. Instead my program runs to completion, and I can just reactivate my profile when I want to debug again.
For more information on non-CICS debug profiles, see
Creating a debug profile for a non-CICS application.