The LIST SUBPOOLS command produces several reports regarding the organization of storage subpools within common storage and within an address space’s private area. We have recently completed a complete rewrite that allows the command to be used both in Foreign Address Space Mode (FASM) and in dump/XDC.

Until now, in order to load/save session profiles, you needed to have a //ISPPROF (or //XDCPROF) allocation in the job (or TSO session ) that you are debugging. Well, when debugging something running in TSO, that’s no problem since //ISPPROF allocations are nearly always present. But in batch jobs, that can be problematic.

z/XDC’s ability to recognize load modules within a CICS address space has been extended. We now support all CICS releases from 4.2 to 5.5.

As some of you have observed, z/XDC has gotten a bit sluggish over the years, and unfortunately, I have to agree. So identifying and correcting significan performance issues has become a priority for us.

z/XDC has a very useful Session Log that it automatically writes to spool. It simply records everything that goes on in the display’s top window (the Working Window). But it never includes anything that occurs in Watch Windows. The problem is, that’s where the PSW and registers are normally displayed.

We have added a new shortcut command: LO can be placed to the left of any displayed machine instruction. If that instruction references storage, the locations will be decoded and the one or two locations referenced will be displayed.

Occasionally, a customer may have severe problems with z/XDC, and he may want to revert to an older level of z/XDC. However, due to the design of z/XDC’s installation process, it is not possible to revert to an older level without either reIPL’ing or somehow clobbering z/XDC’s SSCT entry to make it not findable by z/XDC.

No… We can’t actually run your program backwards, but if you want to see where you’ve been, we’ve got a new and easier way of doing that. We can actually make it look like your program is running backwards!

This may be of particular interest when you’re trying to step execution through reentrant code, but your program is in problem state. The difficulty arises, of course, because the System has loaded the reentrant code into key-0 storage, and z/XDC, being in problem state, cannot set breakpoints into the code.

I have just published Z22-1711B that adds support in z/XDC for all the rest of the new machine instructions introduced on IBM’s Z14 hardware. All of the new opcodes, the new mnemonics and the new extended mnemonics are now recognized and understood.