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.

We have just published update Z22-1709E to add to z/XDC release z2.2 support for the new BIC machine instruction.

I have just uploaded update Z22-1707B.* It implements the following in z/XDC:

RMODE64 support: When z/OS R2.3 comes out, it will have support for loading modules into above-the-bar storage. z/XDC is now ready to fully support mapping, displaying and stepping through such modules.

It recently came to our attention that under certain circumstances, attempting to use XDC in task mode FRR debugging causes the address space to hang at a pause. Turns out we had a bug in the Z21-1509H maintenance that allowed an incompatible TCB to be selected and used. This caused the “unpause” to never occur and things end up at a standstill.

This will interest Sysprogs who have to install and maintain the VTAM network nodes that cs-cdf/XDC needs.

I have just posted Z21-1509F that adds System Symbol support (&SYSCLONE &SYSNAME and friends) to server/XDC’s parsing of its //SYSIN parameter file.

I’ve just published update Z21-1506C that fixes a problem in the vector support introduced in Z21-1505F. We were using an incorrect flag bit in one of our vector support checks. Oops! That causes a S0C7-FE abend to pop up when starting a debugging session for a SRB.

I’ve just finished publishing update Z21-1505F. It implements vector register support in z/XDC. Vector registers are now saved and restored by z/XDC for both task mode and SRB mode execution.