Debug for z/OS

Showing 244

Expand HLASM macro display by command

For a debugging session of an HLASM module, we currently have to decide whether to expand all macros (i.e. show the code they generate) or only show the macro call itself. The first option renders the display nearly useless, because of the sheer n...

over 5 years ago in Debug for z/OS 0 Future consideration

22 VOTE

Debug a Cobol program (6.3) using LangX side file

With Cobol 6, we cannot debug programs using LANGX side files. We would like to continue using this feature as we were able to do with Cobol 4 programs

almost 3 years ago in Debug for z/OS 0 Not under consideration

19 VOTE

Cross debugging

There are some scenarios where the user who is intended to debug some program isn't the one who submits the JCL. Among other situations, this happens when the job is launched from ControlM. In this case, the principal is a service user instead of ...

3 months ago in Debug for z/OS 0 Future consideration

15 VOTE

Debug Tool should start up when transactions get an AICA

If the application gets an AICA (CICS), the only message the developer gets is a connection lost. We figured out that the AICA is explicit trapped in the Debug Tool. But we want the AICA to be passed to the frontend.

almost 8 years ago in Debug for z/OS 2 Not under consideration

13 VOTE

Debugger clean-up job should stop all debugger message regions that are waiting for input

We are using Debug for Z/OS in our test regions. We have scheduled the clean-up job to run every night. This job executes the Program EQANIPSB. It has 2 steps - the first step stops all the debugger message regions and the next step deregisters al...

over 1 year ago in Debug for z/OS 0 Future consideration

13 VOTE

Add customization/rules for 'Code Coverage'

This is request to add 'customization/rules' to 'Code Coverage'. One example, is 'ELSE' statements for each DB2 SQL statement. All 'ELSE' statements are marked as 'not covered' and report statistics do not provide accurate picture. Number may be c...

over 12 years ago in Debug for z/OS 4 Not under consideration

12 VOTE

Debug Tool should report the Jobname and Jobnumber in message +EQA4037I

It is very difficult in transaction systems like IMS MPP's, to find out the messages (i.e. Displays) if the user does not know in what region the IMS transaction was debugged. Therefore the Jobname and Jobnumber would be very helpfull

about 11 years ago in Debug for z/OS 3 Not under consideration

11 VOTE

Add timeout for active and parked debug sessions in IBM Z Open Debug in VS Code

It is common that developers leave active debug sessions open, leaving for lunch or afternoon tea. Even more common that multiple sessions are parked without ever being connected to. It would be VERY helpful if these sessions could timeout. We wou...

10 months ago in Debug for z/OS 0 Future consideration

11 VOTE

Provide additional commands in Remote Debugger

As we try to run DebugTool MFI and remote using the same configuration and command files we would like to have the following commands supported in RemoteDebugger:- COMMENT- CLEAR LOG- %IF- EVALUATE- LIST %dt-var- GO Also we would like to have a De...

over 9 years ago in Debug for z/OS 3 Not under consideration

10 VOTE

Ability to determine if any CICS transactions have debug session active

Currently there is no way to query if any CICS transaction have debug sessions active

almost 3 years ago in Debug for z/OS 0 Not under consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use