HDTenEightyP/NetNews huggingface dataset:
From: CSDRFLOOD@VAX.LIVERPOOL-POLY.AC.UK
Newsgroups: comp.os.vms
Subject: Re: How do you set pre-expired passwords with $SETUAI
Date: 22 Jul 92 09:27:35 GMT
Distribution: world
Organization: The Internet


In article <1992Jul21.182543.28188@nntpd.lkg.dec.com>, Coar@Nephi.Enet.DEC.Com
(various unidentifiable cute names) writes:

>In article <110510@muvms3.bitnet>, boag@muvms3.bitnet (Bob Boag) writes...
>
>>It could be that I just missed it somewhere in the manuals, but I can't seem
>> to 
>>find any way to mark a password as pre-expired when using the $SETUAI system
>>service.
>> 
>>Does anyone know how to do this with VMS V5.4?
>
>    Simply put, a pre-expired password is one whose binary representation has
>    all bits set.  So you can do this by giving UAI$_PWD a quadword with both
>    longwords containing -1.

Far be it from me to correct a DEC person, but NO NO NO!!

Setting UAI$_PWD to -1 will render the account unusable interactively, (at a
guess - I haven't tried it).  Pre-expired passwords are marked by having the
quadword UAI$_PWD_DATE set to both longwords = -1.  From the description of
SYS$SETUAI, it appears that this is not an input parameter, although SYS$GETUAI
will return it.  (Might be worth trying $SETUAI with UAI$_PWD_DATE and seeing
if it accepts it).

I suggest trying $GETUAI for UAI$_FLAGS, setting the UAI$M_PWD_EXPIRED bit, and
$SETUAI the flags again, and see how that goes.  This flag is used, I believe,
when LOGINOUT notices that the password lifeime has been exceeded.

Regards,
Ronan Flood, Systems Manager (pro tem),          CSDRFLOOD@VAX.LIVPOL.AC.UK
Liverpool Polytechnic Computer Services.

Newsgroups: comp.os.vms
From: randy@kean.ucs.mun.ca
Subject: Re: Talaris TLAPSMB Versions
Organization: Memorial University. St.John's Nfld, Canada
Date: Tue, 21 Jul 1992 22:45:46 GMT

In article <0095DE61.F72CF380.9012@hg.uleth.ca>, wilton@hg.uleth.ca ("Russ Wilton, Systems Manager") writes:
> Hi:
>   I am running VMS 5.4-3, soon to be 5.5-1.  I have a Xerox/Talaris XT2492
> laser printer which I have connected through Ethernet using the TLAPSMB
> print symbiont, Version 5.6.  I have heard that there are problems with
> third party symbionts when converting to VMS 5.5-1.  Can anyone tell me
> what version of TLAPSMB is required for VMS 5.5-1?  Thanks for any help.
> 

For others in the same situation, call the 1-800 number for Xerox and 
ask for the latest TLAP symbiont software for VMS 5.5. Its now called
SAVK V1.0 and works on VMS 5.5

Xerox got a tape to me in less than 2 days and it installed without
problem. This is typical of the support I have received from Xerox.
From: coar@Nephi.Enet.DEC.Com (Rodent of Unusual Size)
Subject: Re: How do you set pre-expired passwords with $SETUAI
Summary: Use UAI$_PWD[2]_DATE, not UAI$_PWD[2]
Keywords: $SETUAI, password, pre-expiration
Organisation: Employed by (*NOT* speaker for) DEC, Boxborough, MA, U.S.A.
Organization: Digital Equipment Corp.
Distribution: comp
Date: Wed, 22 Jul 1992 11:53:58 GMT


In article <1992Jul22.004714.23947@cco.caltech.edu>, carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes...
>In article <1992Jul21.182543.28188@nntpd.lkg.dec.com>, coar@Nephi.Enet.DEC.Com (Rodent of Unusual Size) writes:
>>
>>In article <110510@muvms3.bitnet>, boag@muvms3.bitnet (Bob Boag) writes...
>>>It could be that I just missed it somewhere in the manuals, but I can't seem to 
>>>find any way to mark a password as pre-expired when using the $SETUAI system
>>>service.
>>> 
>>>Does anyone know how to do this with VMS V5.4?
>>
>>    Simply put, a pre-expired password is one whose binary representation has
>>    all bits set.  So you can do this by giving UAI$_PWD a quadword with both
>>    longwords containing -1.
> 
>This doesn't sound right.  How can it tell whether or not you supply the
>correct password when you log in?  Perhaps you meant to refer to the PWDCHANGE
>field, which isn't accessible via $SETUAI?

    Bing!  You're absolutely correct, Carl; thanx for spotting that.  The UAI
    item you want to feed a quadword of -1 is UAI$_PWD_DATE, *not* UAI$_PWD.
    UAI$_PWD[2]_DATE is an item code in VMS V5.5-1, if not earlier.  Since
    it's there, I *hope* $SETUAI will honour it, but I've never tried it.
    Lessee..  On a quick test, it appears to *not* be acceptable to $SETUAI,
    so perhaps it's intended only for $GETUAI..  foo!

>Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

    #ken    :-)}	Jeratol the Chaotic

Coar@Nephi.Enet.DEC.Com	 | All opinions herein contained, stated or implied,
Coar@DECUS.Org		 | are solely those of the author.  And he's fullovem.
Coar@Eisner.DECUS.Org	 | `... it was mine art, ... that made gape the pine 
Massachusetts, USA       | and let thee out.'  - Prospero (_The Tempest_)
From: sysop
Newsgroups: comp.os.vms
Subject: Fix for XLOCK for pre VMS 5.4
Date: 22 Jul 92 17:49:00 GMT
Organization: Department of Nuclear Engineering Sciences
News-Software: VAX/VMS VNEWS 1.4-b1

If anyone is running pre-5.4 VMS and would like to use the XLOCK program
from:  public.tgv.com
I wrote an ugly kludge using some code I had lying around that made
use of Joel Snyder's  LGI$HPWD.MAR  source.

If there is enough interest, I will post the additions/mods.

-Shawn


-------------------------------------------------------------------------------
Shawn A. Clifford, System Manager | Internet: sysop@robot.nuceng.ufl.edu
Nuclear Engineering Sciences      |		sac@eng.ufl.edu
University of Florida             | Home Phone: 904/335-4914
Gainesville, Florida  32611       | Work Phone: 904/392-1450  FAX: 904/392-3380
-------------------------------------------------------------------------------
From: venard@bms.com
Newsgroups: comp.os.vms
Subject: Improved Data Recording Capability (IDRC) actual performance
Date: 23 Jul 92 15:15:32 GMT
Reply-To: venard@bms.com
Organization: Bristol-Myers Squibb

Howdy,

Is there anyone out there who uses 3480-type cartridge tape backup systems 
which implement the IDRC compression algorithm? If so, do you have any 
information on how much increased storage capacity you are seeing with the 
IDRC vs the same backups without IDRC enabled? I realize that the amount of 
savings will vary depending on the nature of the input data, but I just 
wonder if anyone has a feel from their own experience as to how much it is 
actually helping their real-life backup situation. DEC's literature says 
"cartridge capacity can be increased by a factor of two to four times (
depending upon the type of data being written." But what are users actually 
seeing in general?

-- Robert Venard
   VAX Systems Manager
   Bristol-Myers Squibb
Xref: sparky comp.os.vms:12643 comp.sys.dec:4126 comp.unix.misc:2987 comp.unix.programmer:3844 comp.unix.questions:9284
From: fish@daacdev1.stx.com
Newsgroups: comp.os.vms,comp.sys.dec,comp.unix.misc,comp.unix.programmer,comp.unix.questions
Subject: Re: VAM/VMS mail file format
Keywords: mail ascii
Date: 22 Jul 92 14:36:59 GMT
Organization: Goddard Space Flight Center

dejesus@archimedes.nwc.navy.mil (Francisco X DeJesus) writes:

>I need to know if there is a way, on a Unix machine, to read/convert a
>mail.mai file which was ftp'd from a VAX machine.

>Here's the deal: mail is received on a VAX periodically. Also periodically
>(every 15 minutes) a Unix machine will ftp to the VAX and get the mail.mai
>file, which contains uuencoded data. The problem is that the mail.mai file
>is not regular ASCII format, and cannot be stripped/decoded the way a
>Unix mail file can.

>To eliminate the obvious responses before they are made: I cannot just
>forward or bounce the mail from the VAX machine to the Unix one (which is
>why we're ftp'ing it - long story), and I cannot do the conversion on
>the VAX because it would require me to log in and do it manually, and what
>I'm trying to do is automate this (of course, if you know of a way to
>automate the conversion on the VAX, *please* let me know!).

>With that in mind, what do you recommend? I see converting the file on
>the receiving Unix machine as the best option, but I'll need either a
>converter program/script, or information about the .mai file format so
>I can write one myself. Any help will be greatly appreciated!!

what you need to do is just write a VMS DCL .com file that joes into mail
does a read/new, extract/all and then ftp put's the extracted file to the
unix box - i can send you a .com file i have that loops thru and picks only
certain ones (using dir/from i think)  -fish
--
John R. Vanderpool                INTERNET: fish@daacdev1.stx.com
NASA/GSFC                         VOX: 301-513-1683                
Hughes/STX Corporation            FAX: 301-513-1608
"arcadian driftwood, gypsy tailwind; they call my home, the land of snow" -jrr
Newsgroups: comp.os.vms
From: dkl@xcluud.sccsi.com (David Karl Leikam)
Subject: Re: Trouble debugging 'Access violation'
Organization: Greater Montrose UFO Appreciation Society & Data Haven
Date: Mon, 27 Jul 1992 17:00:18 GMT

In article <Bruzq5.AEz@andy.bgsu.edu> jburian@andy.bgsu.edu (John M. Burian) writes:
>
>The problem: when my project starts a Wollengong daemon, the daemon
>exits immediately, with what I believe is an Access Violation error.
>The daemon is being started with sys$creprc, and I provide a mailbox
>to write to after the process terminates. Reading the mailbox with
>sys$qiow, I get the accounting message from the daemons termination,
>and the final status field is (hex) 1000000C. Since the C (dec 12)
>is listed as an Access Violation, I assume that's the error, but
>that 1 way over there makes me wonder, and I don't find any error
>codes that large.
>
>I don't have access to the source for the daemon, and the daemon 
>works fine without my project in there. I guess the question is
>what are causes for Access Violation errors? I understand that 
>they are actually fairly generic. Why does it work with our local
>echo daemon (which works with the master server alone, without 
>my project), and not work with Wollengong daemons? Anyone have 
>experience with this?
  
   Access violation is an attempt to address protected memory. The
best way (or at least the most popular way) to cause one, is with
an uninitialized pointer. Your problem sounds like a bad parameter
or incorrect reference mode to an otherwise good parameter, being
passed.
From: dp@FALCON.NATINST.COM (Debapriya Ray)
Newsgroups: comp.os.vms
Subject: RE: Configuring Device Drivers
Date: 30 Jul 92 19:17:58 GMT
Distribution: world
Organization: The Internet

Thanks Richard.
But, I was wondering, how you can specify parameters like board addresses,
addresses of devices on boards, and other parameters in the CSR etc.. ?
Thanks again. Debapriya
From: bleau@umdsp.umd.edu
Newsgroups: comp.os.vms
Subject: Large SCSI disks: fixed?
Date: 30 Jul 92 20:05:13 GMT
Reply-To: bleau@umdsp.umd.edu
Organization: University of Maryland Physics Dept., College Park, MD

I seem to recall there being a problem with using 3rd party SCSI disks on DEC
workstations that were over about 1GB in size.  If memory serves me right, the
DEC SCSI disk driver didn't handle that size properly, and when the disk was
written to near the end, it wrapped around and overwrote track 0.  Does anyone
know if this problems has been fixed and, if so, in what version of VMS and for
what workstations?  The system I have in mind will be a VAXstation 4000 model
90 running VMS 5.5-2, and I want to hang a 1.4GB disk on it.
Larry Bleau
University of Maryland
bleau@umdsp.umd.edu
301-405-6223
Newsgroups: comp.os.vms
From: PCOEN@DRUNIVAC.DREW.EDU ("Paul R. Coen")
Newsgroups: comp.os.vms
Subject: 5.2 --> 5.4 upgrade on an 11/750, startup_p1 problem
Date: 27 Jul 92 16:50:00 GMT
Distribution: world
Organization: The Internet

When we follow the upgrade notes, and set startup_p1 to MIN, and then the
system boots, it doesn't allow logins on opa0:, apparantly because the
driver for the console isn't loaded.  (Note: it doesn't allow logins from
anywhere else, either).

Now, since the upgrade requires that the system is booted with MIN set,
this is a bit of a problem, since you can't start an upgrade without being
able to log in and start VMSINSTAL.

Any ideas?

(Oh, and I'm also assuming that you can start the 11/750 from SYSF from the
console rather than the console tape -- we have our VAX set to boot
off the disk directly, w/out going to the console.)
--

Paul Coen, Drew University Academic Computer Center
	pcoen@drunivac.drew.edu, pcoen@drunivac.bitnet


Disclaimer:  We _do_ have a real VAX, too.
From: oberman@ptavv.llnl.gov
Newsgroups: comp.os.vms
Subject: Re: Summary of responses re: Ethernet monitoring tools
Date: 22 Jul 92 15:46:27 GMT

In article <10993@rls.UUCP>, randy@rls.UUCP (randy) writes:
>> The most useful tip came from Kevin Oberman who suggested FTPing
>> ETHERMON from gw.syr.ge.com. 
> 
> Which version is it?  I had nothing but problems running it.  It would
> hang in a variety of circumstances, particularly when changing screens
> for different monitoring modes.  Mine came off some ancient DECUS tapes. 
 
The only version that will work with VMS V5.5-* is V2.4 which is currently in
beta. The saveset is ETHERMON_24BETA3.BCK (with an external FDL file for those
with brain dead FTPs).

Ethermon has come a LONG way since I brought up my first buggy version (V1.1)
which I would only run on my workstation. (I didn't want to crash other users.)

The current beta has been pretty clean. I think there may be a problem with the
nifty MAP function, but I have not had time to look into it. The problem is
only the MAP fails. It does not cause any system problems.

R. Kevin Oberman			Lawrence Livermore National Laboratory
Internet: oberman1@llnl.gov		(510) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything.
Newsgroups: comp.os.vms
From: freedmanm@woods.ulowell.edu
Subject: Formating Disks under VMS
Organization: University of Lowell
Date: Fri, 31 Jul 1992 20:09:54 GMT

HELP... I need to format two RD54s and two RD53s in two separate Microvax IIs
But I dont have the maintenance kit from DEC..... Does anyone know of or have
a prog to do it?????????????????

						Mike.
Xref: sparky comp.os.vms:12928 comp.lang.c++:11770
From: pbu@drsrv1.hmi.de (pbu)
Newsgroups: comp.os.vms,comp.lang.c++
Subject: DEC-C++ for VMS ?
Keywords: c++,vms
Date: 28 Jul 92 11:04:56 GMT
Followup-To: comp.os.vms
Organization: Hahn-Meitner-Institut Berlin GmbH


Does anybody out there have any experience with DEC-C++ for VMS ?
Especially , what type of compiler is it (precompiler a la cfront or 
real compiler a la g++ ) , incompatibilities with other compilers
, especially Glockenspiel-C++ , debugging-support . 

Any comments welcome 


	Frank (Hoffmann-f@vax.hmi.dbp.de) 
Newsgroups: comp.os.vms
From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
Subject: Re: Am I in SYLOGIN?
Reply-To: carl@SOL1.GPS.CALTECH.EDU
Organization: HST Wide Field/Planetary Camera
Date: Thu, 23 Jul 1992 20:50:34 GMT

In article <01GMPOUMHYGWANBRS5@ccmail.sunysb.edu>, SKAPUR@CCMAIL.SUNYSB.EDU (Sanjay Kapur) writes:
>>
>>How about having the image check for a known executive-mode logical name in the
>>job table?  If it finds the logical name, it assumes it's already been run and
>>exits.  If it doesn't find it, it creates it, does whatever it's supposed to
>>do, and exits.  For this to be effective, you'd have to set the DISCTLY flag in
>>the UAF for all the accounts, and have SYS$SYLOGIN set NOCONTROL=Y after
                                                     ^^^^^^^^^^^^^^^
Sorry, should've been SET CONTROL=Y.

>>running the image.

>Don't forget to also set the RESTRICTED and DEFCLI flags in the UAF if you do 
>not want users to bypass the SYS$SYLOGIN procedure.  See HELP LOGIN.

Unnecessary.  All three supported CLIs check for the logical SYS$SYLOGIN and
execute the appropriate file if they can find it.  Please note:  On systems
that support CLIs other than DCL, you should NOT
	$ DEFINE/SYS/EXEC SYS$SYLOGIN SYS$MANAGER:SYLOGIN.COM
instead, you should
	$ DEFINE/SYS/EXEC SYS$SYLOGIN SYS$MANAGER:SYLOGIN
and have a SYLOGIN.COM for DCL, a SYLOGIN.CMD for MCR, and a SYLOGIN.SH (I
think) for DECShell in SYS$MANAGER:.

If you've got alternate CLITABLES INSTALLed, you should make sure that none of
the definitions in them don't break the corresponding SYLOGIN.  A user cannot
use the /TABLES qualifier to use an alternate CLITABLE unless that alternate
table is INSTALLed.

This takes care of the /CLI and the /TABLES qualifiers for login.  The other
three, /COMMAND, /DISK, and /NEW_PASSWORD have absolutely no affect on
executing SYS$SYLOGIN.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen 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.
Newsgroups: comp.os.vms
From: rusterj@nijmeg.ingr.com (John Rusterholz)
Subject: Re: Last page of *.txt
Organization: Intergraph Nijmegen
Date: Tue, 28 Jul 1992 18:14:45 GMT

rusterj@nijmeg.ingr.com (John Rusterholz) writes:


>	O DCL GURU's,

	Here's some more info about the last page problem:

	The file is a plain ASCII one, the number of pages is unknown.
	What I'm looking for basically is something like

	$ PRINT/PAGES=(""-1,"") FILE.TXT

>	Any help is greatly appreciated.

>	John Rusterholz

>	e-mail: j_rusterholz@eis_john.nijmeg.ingr.com
Newsgroups: comp.os.vms
From: sday@lacerta.unm.edu (Stephen F. Day   UNM CIRT)
Subject: Re: "Vacation" program for VMS Mail
Date: Thu, 30 Jul 92 05:11:10 GMT
Organization: University of New Mexico, Albuquerque

In article <28JUL199212383029@vax2.concordia.ca> timl@vax2.concordia.ca (TIM LAPIN) writes:
>I am looking for a ".com" or other executable to provide a "vacation" 
>utility similar to what exists for MH mail on UNIX.
>
>The utility must:
>	1)	Auto-answer all incoming mail with a prepared text
>
>	2)	Leave all incoming mail marked as "NEWMAIL"
>		I want to see them when I get back.  ** IMPORTANT **

If you have PMDF, look into the DELIVER utility.  That is what I have set
up here...   Funny you should ask this now, since I was just about to write
my 'vacation message' for the weekend.  ;-)

>Tim Lapin
>Computing Services        Concordia University     Montreal, Quebec, Canada
>timl@vax2.concordia.ca    TEL:  (514) 848-7639         FAX:  (514) 848-7622

-- 
    Stephen F. Day         (SFD7)  AT&TNET:      (505) 277-8499
    Systems Analyst/Programmer     BITNET/CREN:  SDAY@UNMB
    CIRT-APSYS                     INTERNET:     sday@ariel.UNM.EDU
    University of New Mexico       TECHNET:      UNMSDAY
From: omalley.mike@a1.dv780.dvo.MTS.dec.com ("Mike O'Malley")
Newsgroups: comp.os.vms
Subject: LPR/LPD for UCX                                                        1
Date: 29 Jul 92 20:25:01 GMT
Distribution: world
Organization: The Internet


    
    Didn't Murphy say "Mean time to needing something is two weeks 
    after you through it away."  Well I need that list of PD UCX 
    things that was send out recently.  In particular I would like to 
    grab the LPR/LPD code.
    
    thanks in advance,
    	...Mike
From: cchd@lucifer.latrobe.edu.au (Huw Davies)
Newsgroups: comp.os.vms
Subject: Re: Redirect printer queue
Date: 24 Jul 92 03:49:37 GMT
Organization: La Trobe University

>Is there any easy and quick way to catch what is sent to a printer queue and
>redirect it to another file? The only way I can think of is to modify the
>symbiont. Any suggestions?

We have a program (written locally) that allows a queue to point to file
rather than a device. For example, the queue

    $ sh queue/all file$print
    Terminal queue FILE$PRINT, stopped, on LURE::DSK2B:[OPER]FILE$PRINT.LIS,
    mounted form DEFAULT (stock=NORMAL)

looks like a normal queue, except that output goes to the file
FILE$PRINT.LIS.

-- 
  Huw Davies           | cchd@lucifer.latrobe.edu.au
  Computing Services   | Phone: +61 3 479 1500   Fax: +61 3 479 1999
  La Trobe University  | I own an Alfa to keep me poor in a monetary
  Melbourne Australia  | sense, but rich in so many other ways
Newsgroups: comp.os.vms
From: gs50@cunixf.cc.columbia.edu (Gong Su)
Subject: Re: Redirect printer queue
Reply-To: gs50@cunixf.cc.columbia.edu (Gong Su)
Organization: Columbia University
Date: Fri, 24 Jul 1992 09:28:02 GMT

In article <1992Jul24.034937.12836@lugb.latrobe.edu.au> cchd@lucifer.latrobe.edu.au (Huw Davies) writes:
>>Is there any easy and quick way to catch what is sent to a printer queue and
>>redirect it to another file? The only way I can think of is to modify the
>>symbiont. Any suggestions?
>
>We have a program (written locally) that allows a queue to point to file
>rather than a device. For example, the queue
>
>    $ sh queue/all file$print
>    Terminal queue FILE$PRINT, stopped, on LURE::DSK2B:[OPER]FILE$PRINT.LIS,
>    mounted form DEFAULT (stock=NORMAL)
>
>looks like a normal queue, except that output goes to the file
>FILE$PRINT.LIS.

Can I have a copy of this program? Thanx.

>
>-- 
>  Huw Davies           | cchd@lucifer.latrobe.edu.au
>  Computing Services   | Phone: +61 3 479 1500   Fax: +61 3 479 1999
>  La Trobe University  | I own an Alfa to keep me poor in a monetary
>  Melbourne Australia  | sense, but rich in so many other ways

Gong Su
Columbia University
gs50@cunixf.cc.columbia.edu

Newsgroups: comp.os.vms
From: uugblum@ariel.lerc.nasa.gov (VMScluster Administrator)
Subject: Re: DECterm loops on exit?
News-Software: VAX/VMS VNEWS 1.41    
Organization: NASA Lewis Research Center
Date: 29 Jul 1992 08:24 EST  

In article <29JUL199211334809@vxcrna.cern.ch>, engelh@vxcrna.cern.ch (Allan Engelhardt, CERN) writes...

>Using DECWindows/mwm and VMS 5.5 the command
> 
>CERATE/TERMINAL/DETACH/INPUT=disk:[dir]EXIT.COM
> 
>where EXIT.COM contains the single line
> 
>$ EXIT
> 
>when started from the session manager gives me a process that just loops
>eating all my CPU time. Selecting "Exit" from the "File" menu on the
>DECterm gives me a process without a DECterm that just loops etc.

You can execute a command when creating a DECterm window, but the command
should be passed as a P1 parameter not as a /INPUT qualifier.  Note that this
only works in non-detached mode.  The DECterm window will disappear after the
command has completed.

$ CREATE /TERMINAL /NODETACH @EXIT.COM

I've used this method to start DECterm windows on our VAXcluster Console.

$ CREATE /TERMINAL /NODETACH VCS CONNECT 'node'

In this case, the DECterm window will stay around as long as you don't exit
the VCS CONNECT program.  In order to use the DECwindow Session Manager's
autostart feature, the process which executes the CREATE/TERMINAL must also
stay around since the DECterm window is a subprocess not a detached process.
I ended up suspending the parent process after executing the CREATE/TERMINAL
command.

--------------------------------------------------------------------------------
Greg Blumers				Sverdrup Technology, Inc.
VAXcluster Administrator		c/o NASA Lewis Research Center
(216)433-6777				Mail Stop 142-2
					21000 Brookpark Road
uugblum@scivax.lerc.nasa.gov		Cleveland, OH 44135
--------------------------------------------------------------------------------

Newsgroups: comp.os.vms