ColeSoft Marketing produces superior debugging products for software engineers and support staff working on IBM Mainframes.
It turns out that c/XDC users have reasons to issue the LIST LKEDMAP command a lot. This is because:
- It sometimes is the case that the external name of a function differs from its internal name,
- And it is sometimes the case that the user needs to provide a function’s external name in order to load the right source image map,
- And normally, AUTOMAP would do the job for you, but sometimes you might want to load a map or two that AUTOMAP would not be able to realize you might need.
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.
We’ve just now pushed out an update (Z21-1505E) that adds support for a //xxxNOALC DD DUMMY jcl statement. When this ddname is present in the TIOT, z/XDC will abort any command or internal service that attempts to use Dynamic Allocation (SVC 99).
We want to thank Bob Edmond of BMC Software for requesting this feature.
A couple years ago, we discovered that we had posted some bad maintenance and we had no way of knowing how many times it was downloaded and who had done the downloading. To help deal with this, we built an interface that requests some basic user information, just a name and email, before the maintenance file can be downloaded. This process gives us a list of users that we can contact in case of an error in the maintenance or an older maintenance has been superseded.