We recently published a couple of z/XDC updates (DBC-2108C and DBC-2108I) That reorganize all maintenance related topics into a more sensible and more readable structure, and consolidated them into one branch of the Built-in Help. That new branch is named HELP MAINTENANCE.

There also is a new, downloadable PDF named  z/XDC Maintenance and New Functionality Guide. 

And the old z/XDC Release Guide is now retired.

Update DBC-2108A adds T as a new Point-and-Shoot command. This is most useful when placed on the targeting operand of any branching (or jumping) instruction. It sets a temporary breakpoint at the branch's target. So if you have several branch instructions in view, you can easily set traps at all of their targets with a single ENTER press, and without having to actually view those targets first.

If your program needs to know where the XDC load module is, previously, you had to use IBM's LOAD macro which issues an SVC instruction. Now, you can instead use our #XDCLOC8 macro because it finds the XDC load module just by chaining through a couple of system control blocks.

This means that your programs that run in constrained environments that cannot tolerate LOAD macros, can still find XDC by using our #XDCLOC8 macro.

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.