TADS.View and System/Editor
Ross Klatte
This was kind of cool in itself--there is a feature that if the
program blows up, it pops you right in at the line of
guilty source. I found a manual. It was kind of dirty,
because the janitor has been using to prop his buckets
off the restroom floor.
The manual had something about TADS Frequency, but
nothing about TADS.View. How do I activate that?
Ross
http://community.webshots.com/user/ross_klatte
Scottie
what version level is your copy of Editor?
The hard copy of the manual may be outdated,
or not updated.
I tended to use the online version through help
so I dont know if the manual has it or if its just
in the d-notes - not unusual.
It's been a while since I worked on MCP, but
I will try to help here if I can with some leads/ideas.
You should have on-line help available
(assuming Editor was installed properly).
Does the on-line help not have TADSVIEW
information?
Online help tends to have accurate up-to-date info.
Documentation is on-line at the Unisys support page,
and I didnt need to log in to get this stuff.
e.g. at,
http://public.support.unisys.com/OS1/TXT/WEB-VERITY?COLLECTION=461&PLATFORM=
PS
or a later release level,
if you type in tads.view and press the select documents button,
you'll get a list of results with references to TADS.View.
e.g. Take, D-Notes for Editor Operations Guide
Scrolling down to SSR44.1 you will find a description of
TADS.View.
You may get more information from each of the TADS
manual D-notes.
e.g.Take, D-Notes for COBOL ANSI-85 Test and Debug System (TADS) Programming
Reference Manual
and by scrolling down to SSR44.1 you will find more
info on TADS.View. Or you may choose a different
TADS set of D-notes for the other compilers.
There may be additional D-notes more recent than these.
I'd think all this information should be available online
through HELP.
There are a number of ways to intitiate TADS.View, and
depending on the nature/complexity of your application
some may be more convenient/appropriate than others.
The easiest way is to enter RUN <program>;TADS
from inside Editor.
(Or if your program is fully contained in your
workfile, RUN;TADS will compile if needed and then
run the compiled codefile with TADS.)
Assuming that TADS is installed, and you have the
proper versions of software running then the Editor
screen should "split" in two, the source code showing
in the upper half of the screen, and the current offered line
established at the beginning point of execution.
Splitting the screen is a TADS bar of buttons,
below which you have a view to TADS.
Can you get this far?
Some applications dont lend themselves to this arrangement.
e.g. libraries, MCS's(?), screen oriented applications that need their own
TD screen/REMOTE file.
In these cases, you can start up TADS the way you would normally
and then use the TADS command VIEW .... to pass control to an
Editor session that has offered to host the symbolic debugging
session by accepting the port file connection with TADS.
"Ross Klatte" <klatt...@aol.commmm> wrote in message
news:20020521185441...@mb-fl.aol.com...
Ross Klatte
>Date: 5/21/2002 11:09 PM Eastern Daylight Time
I will check out some of your suggestions later today.
>Documentation is on-line at the Unisys support page,
>and I didnt need to log in to get this stuff.
>e.g. at,
>http://public.support.unisys.com/OS1/TXT/WEB-VERITY?COLLECTION=461&PLATFORM=
>PS
>or a later release level,
>if you type in tads.view and press the select documents button,
>you'll get a list of results with references to TADS.View.
This raises another point.
The documentation is PDF format.
I am in a motel with a laptop and no printer.
The Unisys box is an office with no Internet.
The PDF documentation cannot be saved or sent. (At least,
I don't know how to do it.)
Does anyone know how to Save a PDF file?
Or, is the same documentation available in a user-friendly format?
Ross
http://community.webshots.com/user/ross_klatte
Alan Ponting
select "save target as" ?
Hope it helps,
Alan
"Ross Klatte" <klatt...@aol.commmm> wrote in message
news:20020522073311...@mb-fa.aol.com...
A Ponting
Try this...
Before viewing the actual document, right click on the link, and select
"save target as".
Hope it helps,
Alan Ponting
"Ross Klatte" <klatt...@aol.commmm> wrote in message
news:20020522073311...@mb-fa.aol.com...
Ross Klatte
>Date: 5/22/2002 6:21 PM Eastern Daylight Time
>>Does anyone know how to Save a PDF file?
>
>Try this...
>Before viewing the actual document, right click on the link, and select
>"save target as".
>
Thanks. That worked just fine.
I got TADS running on System/Editor today. But I was disappointed.
The screen displaying the source code was nice. But I still
have to keep typing "STEP." Reprogramming the keyboard is
awkward, because all the Function keys have already been
programmed with stuff like PRINT("DESTINATION=PRT07386"),
which I don't want to lose.
Indeed, the System Editor version of TADS is inferior to the
CANDE version. With CANDE, you can keep several commands
on the screen, arrow to the command, and hit line-xmt. But in
System Editor, it is only one command at a time.
Also, in System Editor, I can't figure out how to quit without
saving, other than by alt+f4.
Ross
http://community.webshots.com/user/ross_klatte
Scottie
Glad to hear that.
> But I still have to keep typing "STEP."
If you prefer to do so you can.
The most obvious thing to do is to use the TADS view
to enter TADS commands as you would have done
in a typical CANDE TADS session.
But then youre missing out on most of the TADS.View
capabilities.
But you do not have to.
There is a STEP button on the screen.
- "Select" the STEP button and STEP is sent to
TADS on your behalf without you typing it.
"Selecting" the button may mean doing different things
depending on your environment.
In the most crude form, and not very convenient,
is if you are using a real TD, with no mouse.
In that case you would have to use the cursor
keys to move over the STEP button and then
hit SPCFY. Yuck! Then, it might be just as well
to type in more of the commands.
Nowadays, access is common through terminal
emulation running on some workstation, pc, mac etc.
So, just move the mouse over the STEP button
like you would for a pc GUI.
There is usually a way to program the mouse, e.g. the
right mouse key (or the middle one or..) to instruct
the emulator to set position and send SPCFY.
If you cant do that, you should still be able to use
the mouse to move the cursor position and then hit
the SPCFY key, which isnt as good, but still far more
convenient than typing in TADS commands.
With the mouse programmed there is no difference
between the actions here and those on a pc - moving
the mouse click the button, and STEP!
The same applies for all the buttons on the screen.
When you put yourself into Display mode, pointing
at a variable and clicking your mouse over a variable
will do a DISPLAY <variable> query on your behalf.
I know I could rapid fire 4 or 5 DISPLAY queries
with my Mouse in 2 or 3 seconds and have the
results all output on the screen immediately.
No way I could ever type that fast!
You can in effect do most popular TADS operations
with a point and click.
No typing of STEP, or those other commands needed.
> With CANDE, you can keep several commands
> on the screen, arrow to the command, and hit line-xmt. But in
> System Editor, it is only one command at a time.
Hmm.. I never came across that limitation myself, but you are
probably right. (I just cant check for myself but I believe you.)
There is an option through the secondary TADSbar to echo input
which will include showing all your input commands (including
those that get sent on your behalf when you point and click).
You should be able to select the command you need with your
mouse to copy/paste from the screen into the form area
- but the point and click method should reduce the need for
typing in the common commands.
If that isnt convenient, sending the TADS commands from the
editor (]TADS <tads command>) half of the screen, will cause
a list of previous commands (PREVIOUS) to be stored that
can be viewed and selected from. (This isnt probably obvious
to someone just starting out - and still not very convenient for
a TADS user; I admit this might be a lame detour just to note
a way exists.)
I found the amount of actually typing TADS commands was close
to being very rare if at all.
Maybe you need to repeatedly type in obscure/detailed commands?
If so, you could record an editor macro that would make this easier?
> Also, in System Editor, I can't figure out how to quit without
> saving, other than by alt+f4.
You can type FORGET and you will lose any changes from that
session and any previously recessed and recovered sessions leading
to this one.
Have you wondered what the TADS buttons do?
e.g. Try selecting HISTORY, or WALK or +/-BP.
What about selecting Menu or ? to put you in Display mode?
Are you familiar with XREFFILES and are you using them to
browse in the Editor? You can always return to your current
point in the TADS session by selecting TRACE.
> Indeed, the System Editor version of TADS is inferior to the
> CANDE version.
I never looked back, but then I was already a big Editor user.
"Ross Klatte" <klatt...@aol.commmm> wrote in message
news:20020522194321...@mb-ck.aol.com...
Ron Brody
"Scottie" <Sco...@nowhere.COM> wrote in message
news:AQYG8.43156$Q93.2...@news1.west.cox.net...
> > I got TADS running on System/Editor today.
>
> Glad to hear that.
>
>
> If that isnt convenient, sending the TADS commands from the
> editor (]TADS <tads command>) half of the screen, will cause
> a list of previous commands (PREVIOUS) to be stored that
> can be viewed and selected from. (This isnt probably obvious
> to someone just starting out - and still not very convenient for
> a TADS user; I admit this might be a lame detour just to note
> a way exists.)
>
Scottie, I'm pleased that you are an Editor fan.
In your response you suggest using the PREVIOUS command. In my opinion this
command is obsolete, being replaced by the SHOW, RETRIEVE, and REPEAT
commands (as well as the OOPS RETRIEVE variant).
The SHOW command is very similar to PREVIOUS except that it displays both
commands and text input for the entire Editor session. (It does not provide
the ability to move the edit line to where you were when you entered the
command as PREVIOUS does.) The SHOW command also accepts a <pattern>
parameter which limits the display to only those entries that match the
<pattern>.
The OOPS RETRIEVE variant (as well the CTRL 08 sequence) undoes the last
input and redisplays it.
The RETRIEVE command (which can also be entered as a "*") redisplays the
last input (that matches a <pattern> if specified). For example, ]*COMPILE
redisplays the last input the contains "COMPILE".
The REPEAT command (which can also be entered as a "!") reenters the last
line of input (that matches a <pattern> if specified). For example, ]!ALL
will reenter the last input (command or text) that contains "ALL".
---Ron Brody