On Mon, 10 Jul 2006 19:50:41 -0600, Anne & Lynn Wheeler wrote:

>"Rostyslaw J. Lewyckyj" <[EMAIL PROTECTED]> writes:
> > Well I had exposure, access, to an IBM MVT product called TESTTRAN
> > which was sort of available on our system with assembler F and , if
> > I remember correctly, Fortran G, both in batch and TSO.  One had to
> > compile/assemble with the TEST option, which produced and kept a
> > variables symbol table and a statement location table.  One could
> > then set breakpoints, examine program values etc. etc.  But it was
> > very awkward to use, badly documented, and buggy.  When I asked I
> > was told that it wasn't developed because it wasn't used. Which I
> > considered to be a very much a chicken and egg kind of argument.
> >
> > I had a little exposure to TEST under our CMS systems. But as we
> > didn't really support VM/CMS too well at TUCC&UNC I can't comment
> > much except that I didn't find out much about what it was capable
> > of.
>
>huge amount of OS/360 TESTRAN was outputing all the (12-2-9) "SYM"
>cards as part of assemble/compile ... so that you effectively could
>support symbolic debugging. I don't know anybody that actually used it
>... I remember having a TESTRAN manual at one point and running with 
>option to generate SYM cards (just to see what they looked like) ... but 
>never actually using it.
>
>old post that has mention of "SYM" cards (as well as formats of most of 
>the other 12-2-9 cards):
I never used TESTTRAN, but the VP/CSS debugger used the SYM cards, and that 
debugger was used heavily until 
the early to mid 90s.  We ported moat of it to CMS, but never did all of the 
work to make it run in XA virtual machines 
so we when started to use XA and XC virtual machines for our developing work, 
we had to use TRACE and PER.

Lloyd Fuller

Reply via email to