Support Debug Profile Services debugger invocation when editing a JCL member

The z/OS debugger profiles provide the end user the usability features that makes initiating the debugger session more intuitive.

Perhaps the z/OS debugger profile could become a "one stop for all" step to engage the debugger with a little more work. This makes sense for a couple reasons:
a) The debugger profile could be the only place one would need to go to initiate the debugger
b) The debugger would be more consistent, allowing for the debugger to start the debug session with a subprogram, identified prior to the debug session for both CICS and batch programs.

The "Debug As" --> "z/OS Batch Applications using existing JCL" is a very nice, simple method to invoke the debugger. Most people already be editing the JCL member before invoking the debugger, so it is in the right place to initiate the debugger.

I thought we may want to add another option, such as "z/OS Batch using the Debug Profile". This invocation would:
a) Verify the z/OS debugger profile services started task is active on z/OS, thus honoring the interpreting the TEST command as a delay debug invocation. If not, don't show the option, or don't proceed with the process
b) Scan the JCL like the Debug As option. When the program is shown (note, JCL procedures need work to show scan the procedure), then prepare the DLAYDBG.EQAOPTS profile with the load module from the JCL member and * for the program. Then provide the panel filters panel to allow the user to modify the program with a subprogram to begin the debug session. The next action would be CANCEL, or SAVE and SUBMIT, meaning save the z/OS debugger profile, then submit the job. The SUBMIT option would generate the
//CEEOPTS DD *
TEST
lines prior to submission.


I believe this process would provide a single method to invoke the debugger for all z/OS debugging needs except for non-le programs and IMS transaction isolation.

I found out the delay debug option works with non-le programs, In the future, we could use the same process to invoke the debugger for non-LE programs, provided with additional changes for the program name and //EQANMDBG statement, and the LANGX files, and LDD statements.