HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.os.vms
Subject: Question about lexical f$cvtime()
From: fowler@southpower.co.nz
Date: 15 Apr 92 16:51:37 NZDT


Hi,

I have a question about the use of the lexical function f$cvtime().

I need to calculate the elapsed time value and output the time in a format
similar to "Uptime" from the command "show system".

$ show system
VAX/VMS V5.4-3  on node ODIE  15-APR-1992 16:36:24.40   Uptime  13 21:54:40
                                                        ^^^^^^^^^^^^^^^^^^^

for example...

$       start_time = f$time()   ! Start time of DB scan
$!
$       run exe:db_scan         ! run database scan
$!
$       finish_time = f$time()  ! Finish time
$!

I need to use the symbols start_time and finish_time to calculate the
elapsed time. Can this be done at all from DCL.

Please respond via email and I will post a summary,
Thanks,
Ken.
------------------------------------------------------------------------------
 Ken Fowler (Info Services),   Phone (64)(03) 639-527,  Fax (64)(03) 639-816
 Southpower,                   Internet  in%"fowler@galaxy.southpower.co.nz"
 Private Bag,                  PSI       psi%0530147000090::galaxy::fowler
 Christchurch,              or PSI       psi%0530130010083::galaxy::fowler
 New Zealand.
 Disclaimer - Opinions expressed here are my own and nobody else's
         ____  ____       ____       ____  ____          ____  ___
        /___  /   / /   /  /  /___/ /___/ /   / /  /  / /___  /__/
       ____/ /___/ /___/  /  /   / /     /___/ /__/__/ /___  /  |
------------------------------------------------------------------------------
From: gavron@spades.aces.com (Ehud Gavron 602-570-2000 x. 2546)
Newsgroups: comp.os.vms
Subject: Re: SUMMARY:How to SET FORWARD to multiple users
Date: 14 Apr 92 16:41:00 GMT
Reply-To: gavron@Diamonds.ACES.COM
Organization: Associates in Consulting and Educational Services
News-Software: VAX/VMS VNEWS 1.4-b1

In article <KENW.92Apr13161603@skyler.arc.ab.ca>, kenw@skyler.arc.ab.ca (Ken Wallewein) writes...
# 
#  It boils down to this: DEC removed that capability from VMS Mail in V5.0,
#apparently because they were worried about mail loops.  I thought it was a
#bad decision then, and I still do.

	No, that's not why DEC removed it.

	MAIL-11 sends one ACK per valid address.  If user FRED has
	his mail forwarded to user JOE and you send mail to 
	NODE::FRED and NODE::JOE, only one ACK will be received, and only one
	copy will be delivered to JOE.

	Imagine this:

	NODE ALPHA:
	JOHNNY sets forward to  JOE AND JIM
	JOE sets forward to DESK::JIM
	JIM sets forward to DESK::JIM

	If you send mail to JOHNNY, you will hang forever pre V5.0.
	V5.0 prohibits JOHNNY from setting such a forwarding address.

#--
#/kenw
# 
#Ken Wallewein                                                   A L B E R T A
#kenw@noah.arc.ab.ca                                           R E S E A R C H
#(403)297-2660                                                   C O U N C I L

	Ehud

--
Ehud Gavron        (EG76)     
gavron@vesta.sunquest.com
Where's SANDY DUNCAN?
From: rice@ttd.teradyne.com
Newsgroups: comp.os.vms
Subject: Re: interesting fact about vms mail
Date: 15 Apr 92 18:20:37 GMT
Article-I.D.: ttd.1992Apr15.132159.1
Organization: Teradyne Inc., Telecommunications Division

In article <1992Apr12.172437.14749@yuma.acns.colostate.edu>, barbourj@CS.ColoState.EDU (jim barbour) writes:
> In article <9204061211.AA08065@sjosu1.sinet.slb.com> brydon@asl.SINet.SLB.COM (Eschew Obfuscation) writes:
>>John E. Davis ("davis@amy.tch.harvard.edu") says:
>>>   I notice something about VMS mail that I never noticed before: you can
>>>have VMS mail always put new mail in an ordinary sequential ascii file.
>>> ...
>>
***deleted**

> Also, I don't know of any editor scripting languages that support the
> callable mail interface without a lot of hacking.
> 

TPU will support callable mail, but it's alot easier to call TPU/EVE from
within VMSmail. 

    For reading off-line, I just use extract/all from the newmail folder (or
whatever folder I'm in) and then download the extracted file. This leaves me
all of the utility of VMSmail (multiple folders, multiple files, etc) which is
really where the power is.


-- 
   John Rice         K9IJ    |  "Did I say that ?" I must have, but It was
   rice@ttd.teradyne.com     |   MY opinion only, no one else's...Especially
   (708)-940-9000 - (work)   |   Not my Employer's....
   (708)-438-7011 - (home)   |   Purveyor of Miracles,Magic and Slight-of-hand
From: gezelter@rlgsc.com
Newsgroups: comp.os.vms
Subject: Re: INSTALL and "<>"s...
Date: 16 Apr 92 16:55:20 EST
Organization: Robert Gezelter Software Consultant, Flushing, NY

In article <1992Apr16.120228.5627@nocusuhs.nnmc.navy.mil>, yoshi@nocusuhs.nnmc.navy.mil (D M Yoshikami) writes:
> In article <1992Apr15.214813.19181@cco.caltech.edu> carl@SOL1.GPS.CALTECH.EDU writes:
> 
> If my memory is Ok, which it often isn't, I seem to recall that RMS came on
> a separate tape (back in 1982!!) which the sysmgr DIDN'T install because he
> figured nobody used it.  Well, you can still access junk without RMS directly
> through the XQP (actually back then I think it was the FILES-11 ACP that did
> the dirty work), so I think what he did is plausible.  But this was on the
> Files-11 On-disk Structure 1.
> 
Your memory is partially correct. On the RSX-11 family, RMS was 
an optional set of components which could be completely ignored. 
All of the utilities used a smaller, older set of access routines 
referred to as FCS (File Control Services). Indeed, the KEYED 
(ISAM) components of RMS were an extra charge product.
 
+--------------------------------------------------------------------------+
| Robert "Bob" Gezelter                       E-Mail:  gezelter@rlgsc.com  |
| Robert Gezelter Software Consultant         Voice:   +1 718 463 1079     |
| 35-20 167th Street, Suite 215               Fax:       (on Request)      |
| Flushing, New York  11358-1731                                           |
| United States of America                                                 |
+--------------------------------------------------------------------------+
Newsgroups: comp.os.vms
From: themos@umbc5.umbc.edu (Mr. Themos Pentakalos; ADMIN-COMP)
Subject: Job Controler 
Organization: University of Maryland Baltimore Campus
Date: Mon, 6 Apr 1992 12:57:16 GMT

Hello,

	Does anyone know what kind of an error whould put all the
queues in "stopped" mode, except for the batch queues?

	We do have a third-party software currently on the testing 
phase, which seems to be doing some business with the job controler.

	Any help is appreciated!

	Themos

	send e-mail to themos@umbc5.umbc.edu   please...
From: jackson@pravda.enet.dec.com
Newsgroups: comp.os.vms
Subject: Re: SET DISPLAY/SCREEN=??
Date: 8 Apr 92 11:27:26 GMT
Reply-To: jackson@pravda.enet.dec.com ()
Organization: Digital Equipment Corporation


In article <1992Apr8.063256.9669@news.Hawaii.Edu>, pnd@jach.hawaii.edu (Phil Daly, JAC, 665 Komohana St, Hilo HI 96720, USA) writes:
|>
|>Is there a way to re-direct output from a DECwindows application to
|>more than one screen at a time? I would like to do something like
|>
|>  $ SET DISPLAY/CREATE/NODE=(MYVAX,YOURVAX)
|>
There have been some implementations of "shared X" out there, but there
are none that are offered and supported by Digital.  

|>
|>The documentation mentions the /SCREEN option and suggests that some
|>configurations can do this. Another poster mentioned the fact that
|>
|>   $ SET DISPLAY/CREATE/NODE=curly
|>
|>is equivalent to
|>
|>   $ DEFINE DECW$DISPLAY CURLY::WSA0:

True story.  These are esentially the same, however the SET DISPLAY 
command is the preferred (and supported) way to redirect your display.

The /SCREEN is for those workstations that have multiple screens. (like 
my VAXstation 3100)  This is not for multiple workstations on a network

--


William M. Jackson
Workstation Product Marketing Manager
Workstation Engineering
Digital Equipment Corporation
146 Main Street
Maynard, MA 01754

Mail:	Jackson@pravda.enet.dec.com
From: ARNE@ko.hhs.dk (Arne Vajhxj)
Newsgroups: comp.os.vms
Subject: Re: TPU sources
Date: 14 Apr 92 07:13:00 GMT
Distribution: world
Organization: The Internet

> DEC has now come out with a TPU program for the RISC/ultrix machines.
> This comes with the EVE editor, but nothing else.  I'm trying to find
> out if/how to acquire some of the other TPU programs, in particular
> LSE.  Is there an archive somewhere?

Well - I do not think DEC would like it, if there were an archive with
the sources for LSE. LSE is a DEC product, which they sell for money
(big money).

                                                          Arne Vajhxj

Arne Vajhxj                             local DECNET:  KO::ARNE
Computer Department                     PSI:           PSI%238310013040::ARNE
Business School of Southern Denmark     Internet:      ARNE@KO.HHS.DK
From: jhfreeman@adus.ecn.uiowa.edu (James H Freeman)
Newsgroups: comp.os.vms
Subject: How to add new vax into family?
Date: 15 Apr 92 23:45:20 GMT
Distribution: na
Organization: International HP Workstation users' group (InterWorks)
Originator: jhfreeman@iworks

The Geology Department here at Cornell College will be getting a MV3100 
this summer.  It will be running specialized x-ray software under VMS.
The problem is it will be located in a building that does not have 
ethernet access.  Until the campus wide ethernet is installed, how can I
connect the lone vax to my vaxcluster?

I would like to be able to do remote logins, file copying, mail & 
maybe nntp news.

What we have now: serial lines to other building for terminals.
Vax Cluster with VS3100 & MV3300, 2 DS200MC's and 1 XYPLEX MAXSERVER 
1500 (LAT &TCP), router to internet, all on thinnet.

What we are getting: MV3100 w/ethernet & 8 port decserver 90L.

Can I set up a decnet link over a serial line to let me do decnet logins & 
also run UCX over this link(ftp & mail using MX?)?

If there is enough twists in the serial line and it is around 100 yards away,
how about 10baseT ethernet?

What does a SLIP connection need?

Thanks in advance for any help.  And this college is looking at ways to do this
inexpensively.

Bruce Cantrall
bruce@cornell-iowa.edu
From: brosen@BBN.COM (Bruce L. Rosen)
Newsgroups: comp.os.vms
Subject: C++ compiler for VMS
Date: 9 Apr 1992 18:51:26 GMT
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Distribution: usa
Reply-To: brosen@BBN.COM (Bruce L. Rosen)
NNTP-Posting-Host: bbn.com

We'd like to get hold of a reliable and supported C++ compiler for
use under VMS.  I'd appreciate any suggestions/recommendations.

Bruce Rosen (brosen@bbn.com)
BBN Software Products
Newsgroups: comp.os.vms
From: mdchaney@bronze.ucs.indiana.edu (M Darrin Chaney)
Subject: Re: Setting ICON and window titles on VT1200's "LAT Terminal Wi
Organization: Indiana University
Date: Mon, 13 Apr 92 15:07:55 GMT

In article <57262@cup.portal.com> Chris_F_Chiesa@cup.portal.com writes:
>Dan Wing, DWING@UH01.Colorado.EDU or WING_D@UCOLMCC.BITNET) writes:
>>Is it possible to change the window and icon titles on these connections like
>>you can with DECwindows, without going through the Customize window?
>
>Yes.  You can send some (undocumented?) OSC (operating system control) 
>sequences to the terminal-emulation window that will accomplish the change.
>I have a DCL procedure that came, ironically, right off THIS net about a
>year and a half ago or more, that makes the claim of a number of OSC
>sequences which are supposed to resize and reposition the window, too, but 
>I've tried 'em all and the only ones -=I=- can get to work are the window-
>and icon-NAME sequences.  I caught a subtle implication in a recent posting
>that these OSC sequences may be left over from UWS, which might explain
>the VT1200's half-hearted understanding of them.

Here it is, ICON.COM:

$ OSC[0,8] = 157
$ ST[0,8] = 156
$ Write Sys$Output OSC,"2L;",P1,ST
$ If P2 .NES. ""
$ Then
$   Write Sys$Output OSC,"21;",P2,ST
$ Else
$   Write Sys$Output OSC,"21;",P1,ST
$ EndIf

You type "@icon icon_name window_name" or "@icon name_for_both."  It's
on the last page of the "DECwindows Cookbook."

	Darrin
-- 

mdchaney@iubacs mdchaney@bronze.ucs.indiana.edu mdchaney@rose.ucs.indiana.edu

"It's a marvel of vegetable containment..."
From: jackson@pravda.enet.dec.com
Newsgroups: comp.os.vms
Subject: Re: 3 Motif Questions
Date: 14 Apr 92 12:50:07 GMT
Reply-To: jackson@pravda.enet.dec.com ()
Organization: Digital Equipment Corporation


In article <1992Apr13.103418.1@travis.llnl.gov>, massey@travis.llnl.gov writes:
|>
|>Does anyone know why I cannot do a cut/paste from/to a pair of Motif windows,
|>one being local to the workstation that I'm at, the other belonging to a 
|>remote machine (created with "Set Display/Create/Node" & "Create/Term/Detached
|>/Window"). This worked before I switched to Motif.

The motif style has changed the buttons around.  MB2 is now MB3 and MB3 is 
now MB2.  It'll take a while to get used to it, but I think you'll find that
everything that you had before will continue to work

|>
|>The program from mdchaney@iubacs to reposition the login box under Decwindows 
|>does not appear to work under Motif. Does anyone have a program that does or 
|>know how to fix Darrin's?

The designators changed between DECwindows XUI and DECwindows Motif.    Much
of the customization stuff is explained in the Motif users guide that you can
get from OSF.

I put the following in my DECW$XDEFAULTS.DAT to position the icon box and 
set its geometry.  Remember, you also have to tell the window manager that it
should USE an icon box!


Mwm*iconBoxGeometry:    2x5+0+285

The syntax is is 	2:	Icon box is two icons wide
			5:	Icon box is five icons high
			0:	X position, offset from left edge
			285:	Y position, offset from top edge

--


William M. Jackson
Workstation Product Marketing Manager
Workstation Engineering
Digital Equipment Corporation
146 Main Street
Maynard, MA 01754

Mail:	Jackson@pravda.enet.dec.com
Xref: sparky comp.os.vms:8361 comp.sys.dec:2575
From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.)
Newsgroups: comp.os.vms,comp.sys.dec
Subject: Re: CONDIST discrepencies in media!
Date: 15 Apr 92 11:10:33 GMT
Organization: St. Peter's College, US

In article <1992Apr14.234335.612@fps.mcw.edu>, brodie@fps.mcw.edu writes:
> I have a nasty gripe about CONDIST  (DEC, are you listening?   I need
> this one to go to the engineers!).
> 
> My current issue of CONDIST has the latest and greatest TSM
> (terminal server manager) product--   V1.5.   [just released
> a few months ago].
> 
> On the SAME condist issue (the same DISC, even), is MCCSMS021
> (DECmcc site management station software, V2.1).    DECmcc,
> includes with it a lot of things, *including* TSM.
> 
> Guess what?     DECmcc installs its OWN copy of the TSM
> distribution media, and lo and behold, it's V1.4!

  It's my understanding that the ConDist folks aren't allowed to mess with
the content of the individual packages on ConDist - they just master them
all onto the CD and ensure that the SPD's, installation guides, etc. are
present.

  I think that if you got DECmcc on magtape you'd have the same problem.

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381
From: HOLDREGE+_MP%A1%PacifiCare@MCIMAIL.COM (Matthew Holdrege)
Newsgroups: comp.os.vms
Subject: Setting ICON and window titles on VT1200's
Date: 15 Apr 92 18:21:00 GMT
Distribution: world
Organization: The Internet


DATE: Wed Apr 15, 1992 10:56 am

mdchaney@bronze.ucs.indiana.edu writes...

>Here it is, ICON.COM:
>$ OSC[0,8] = 157
>$ ST[0,8] = 156
>$ Write Sys$Output OSC,"2L;",P1,ST
>$ If P2 .NES. ""
>$ Then
>$   Write Sys$Output OSC,"21;",P2,ST
>$ Else
>$   Write Sys$Output OSC,"21;",P1,ST
>$ EndIf

Thanx for this useful information. I put this in my login.com but I changed P1
and P2 to F$GETSYI("NODENAME"). This works great on my Vaxstation 3100
running VMS 5.5 Decwindows except for one problem.

If I set host or telnet to another VMS node, my icon updates itself to the new
nodename. But when I logout and return to the originating node the icon, of
course, doesn't change.

My question: 

Is there any way to kick off a command procedure upon returning from a CTERM 
or TELNET session?
==============================================================================
Matt Holdrege               Internet: 5156065@mcimail.com
Pacificare Health Systems   Voice:    714-229-2518
From: brydon@asl.SINet.SLB.COM (Eschew Obfuscation)
Newsgroups: comp.os.vms
Subject: RE: interesting fact about vms mail
Date: 6 Apr 92 12:11:37 GMT
Article-I.D.: sjosu1.9204061211.AA08065
Organization: The Internet

John E. Davis ("davis@amy.tch.harvard.edu") says:
>   I notice something about VMS mail that I never noticed before: you can
>have VMS mail always put new mail in an ordinary sequential ascii file.  That
>is, do the following:
>
>  1.  Move to your mail directory where the indexed mail.mai file is kept.
>  2.  Create another mail.mai file as in:
>
>            $ create mail.mai
>            ^Z
>
>Now any mail that arrives will be put in this sequential mail file.  You can
>read it with type/most/edt or whatever. Mail messages will be separated with
>a "^L\nFrom:^I" string.  Of course mail.exe will not work with it.  But this
>is great since one is now free to write one's own mail interface without all
>of the complexity of the callable mail interface.

You are causing mail to use the mail file format that was used in VMS V1 up to
V3 (to 1984).  From VMS V4 up to the present it is now an indexed sequential
file.  MAIL.EXE does still work with the old format for compatibility
reasons.  You can also create a mail file in the old format with the command
"MAIL> extract /mail [/otherquals] filespec".  There are some things you can't
do with the mail file in the old format.  Not sure why you think this is
"great because..." since you can now use callable mail to do almost anything
with your mail using a supported interface.

____________________________________________________________________________
Harvey Brydon         | Internet:   brydon@asl.sinet.slb.com
Schlumberger Anadrill | FAX:        (713)274-8399
200 Macco Blvd        | Telex:      1565030001 SINET ASL SLB
Sugar Land, TX 77478  | P.O.T.S.:   (713)274-8000 x8281 or 274-8281 (d.i.d.)
 He who has a respect for the law or love of Italian sausage should not see
  how either one is made.
From: jnelson@gauche.zko.dec.com (Jeff E. Nelson)
Newsgroups: comp.os.vms
Subject: Re: Debugger problem, VMS 5.5, VWS4.3 & DECwindows/Motif
Date: 8 Apr 92 12:15:40 GMT
Reply-To: jnelson@gauche.zko.dec.com (Jeff E. Nelson)
Organization: Digital Equipment Corporation


In article <56998@cup.portal.com>, Chris_F_Chiesa@cup.portal.com writes:
|>Oh, goodie, a Debugger developer at LAST!  I've only been trying to get
|>YOUR ear for the last two or three years... :-)

You must have missed my posts (not that I'm trying to call attention to myself).

|>Namely, if I have a data declaration like this:
|>
|>mystring:	.ascid	\Bogus\
|>
|>I'd like the debugger to interpret the symbol "mystring," when issued in
|>a command (e.g. EVAL/ADDRESS MYSTRING; SHOW SYM/ADDR MYSTRING; EXAM/QUAD
|>MYSTRING; etc.), as the address of the DESCRIPTOR, which is what the symbol
|>actually defines in terms of memory addresses.

The debugger gets its information about symbols in your program from the
compiler (in this case, the assembler). This information includes the symbol
name, the symbol type and the symbol address. The information is recorded in
a structure called the Debug Symbol Table (DST). Thus, the debugger's knowledge
about the symbols in your program is only as good as the information that is
passed along to it by the compiler (assembler).

In any case, I tried your example on VMS V5.4 using MACRO32 with the following
image identification:

                image name: "MACRO32"
                image file identification: "X-8"
                link date/time: 19-JUN-1990 05:19:57.17
                linker identification: "05-05"

Source code:
-----------------------------------
mystring:       .ascid  \Bogus\
        .external    lib$put_output
        .entry main,^m<>
        pushab  mystring
        calls   #1,g^lib$put_output
        ret
        .end    main
-----------------------------------

Sample run:
-----------------------------------
$ r test

         VAX DEBUG Version V5.4-019

%DEBUG-I-INITIAL, language is MACRO, module set to .MAIN.
DBG> show symbol/address/type mystring
data .MAIN.\MYSTRING
    descriptor address: 00000200
    string descriptor type, character-coded text, size: 5 bytes
DBG> e mystring
MAIN.\MYSTRING:        'Bogus'
-----------------------------------

Thanks for bringing the problem to our attention. I'm happy to report
that it is fixed.

-Jeff E. Nelson
-Digital Equipment Corporation
-Internet: jnelson@gauche.zko.dec.com
-Affiliation given for identification purposes only
Newsgroups: comp.os.vms
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Subject: Re: Total number of files on a volume
Reply-To: carl@SOL1.GPS.CALTECH.EDU
Organization: HST Wide Field/Planetary Camera
Date: Fri, 17 Apr 1992 07:20:30 GMT

In article <1992Apr16.162008.42@rlgsc.com>, gezelter@rlgsc.com writes:
>help init
>In article <9204152025.AA24577@ucbvax.Berkeley.EDU>, tja@KIRK.SAFB.AF.MIL ("Thomas J. Adams") writes:
>> Hello net folks,
>> 
>> What is the maximum number of files on a volume?  I had a problem creating any
>> more files on a disk.  
>> 
>The maximum number of files is specified when the volume is 
>initialized (using the INITIALIZE command). 
> 
>The default value for the /MAXIMUM_FILES switch is computed using 
>the formula:  
> 
>	(Volume_Size_in_Blocks)/((Cluster_Factor+1)*0.5).
> 
>The Maximum number of files on a FILES-11 Level 2 volume is 
>computed using the formula: 
> 
>	(Volume_Size_in_Blocks)/((Cluster_Factor+1)
> 
>In both of these formulae, the Volume_Size_in_Blocks is the 
>actual size of the volume (formatted capacity) expressed in 512 
>byte blocks.

Not quite.  It's
	FORMATTED_CAPACITY/CLUSTER_FACTOR*CLUSTER_FACTOR
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXes and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
From: diewald@virrus.zko.dec.com (Jeff M. Diewald)
Newsgroups: comp.os.vms
Subject: Re: Debugger problem, VMS 5.5, VWS4.3 & DECwindows/Motif
Date: 6 Apr 92 15:16:17 GMT
Reply-To: diewald@virrus.zko.dec.com (Jeff M. Diewald)
Organization: Digital Equipment Corporation

> 
> Does anyone out there know if there is/was any substance to the rumor that
> the debugger was going back to a single window (instead of three) ??
> 
  
   We've completely rewritten the Debugger user interface in light of all
the feedback we got about the problems.

   1. It's *significantly* faster.  We've also implemented RUN and RERUN
       commands in the Debugger, so you can fire it up once and leave it
       up.

   2. It's *significantly* easier to use.  We've run extensive field
tests asking for 
       user feedback.  Then we've incorporated the appropriate changes
in the UI.
       The response has been very very positive.  
   
   3. If you don't like what you see, you can customize a lot more of
it.  You can
       add buttons to the control area, with your own commands.

   4. There are two windows.  One is the source window.  The other is a paned 
       window with the controls and optional views.

   5. Want the same UI on VMS and Ultrix?  We've put this new UI on top of dbx,
       so you have essentially the same look and feel on both systems.

  In short - if you've turned off the DECwindows interface in the past because
it was unusable, check out the new and improved debugger when it's available
in your area.  I think you'll like the changes.

						Jeff Diewald
						Debug developer