Debug for z/OS

Showing 244

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

9 VOTE

Improve DTCNDELETEDEADPROF to delete only unused profiles for a specific period

Enabling DTCNDELETEDEADPROF parameter causes to delete all profiles after logoff of the user. Unfortunately, debugger users should redefine deleted profiles at their next logon. A new parameter so to delete only DTCN profiles that have not been us...

8 months ago in Debug for z/OS 1 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

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

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

32 VOTE

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

4 VOTE

Prevent users from debugging excluded programs

Due to many reasons (privacy, performance, ...) organizations might want some programs to be excluded from debugging. Currently, the command NAMES EXCLUDE allows for that. However, it lacks fine-grain control over that exclusion. Worse than that, ...

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

2 VOTE

Do a Logical Or on the target of an Execute instruction

When the debugger uses the in-storage copy of the Execute target, it usually only displays the first byte of the operand and sometimes displays the wrong operand entirely. When the Ex target is an SS instruction then the length can only be determi...

6 months ago in Debug for z/OS 4 Not under consideration

1 VOTE

Switching between transactions to debug is no longer possible in the new version of Debugger

A test user has registered many transactions, as sometimes one transaction is debugged and sometimes the other. In this case, however, only one transaction should be debugged. With the newly installed version of the debug tool (V16.02), it is now ...

4 months ago in Debug for z/OS 0 Under review

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