HDTenEightyP/NetNews huggingface dataset:
From: tihor@acf3.NYU.EDU (Stephen Tihor)
Subject: Re: suggestions for suppliers.... AND ...
Organization: New York University
Date: Mon, 17 Aug 1992 12:57:00 GMT

The DCL level solution to make the list of all holders of an id 
is to run authorize and do a 
SHOW/ID/FULL identifiername
But making a mailing list out of these means parsing the output 
of a command and thus m,ay need minor rewrites if the format of the output 
changes.
Newsgroups: comp.os.vms
From: bear@nuc.anu.edu.au (Bernhard Fabricius)
Subject: VAXstation rodent port pin configuration ?
Reply-To: BEAR@NUC.ANU.EDU.AU
Organization: Nuclear Physics, ANU
Date: Fri, 21 Aug 92 01:50:30 GMT


Hi there,

      does anyone know the pin-outs on the VAXstation rodent (mouse) port 
      (the Mini-DIN plug on VAXstation 31xx/40xx) ?

      What is the communication speed of the VSXXX-AA rodents ?

      (I have a spare rodent I want to turn into cheap dial/button box
      using one of the terminal ports - in case you wondered...)
      

Cheers

Bernhard
--------------------------------------------------------------------------------
Dr Bernhard Fabricius              |
Academic VAX/VMS Support           |  "I am a Bear of Very Little Brain,
Department of Nuclear Physics      |           and long words Bother me."
Australian National University     |
                                   |                           - A.A. Milne
InterNet: BEAR@NUC.ANU.EDU.AU      |
    POSTMASTER@NUC.ANU.EDU.AU      |
From: allebrandi@inland.com (Tom Allebrandi)
Newsgroups: comp.os.vms
Subject: Re: Will lmf kill alpha?
Date: 21 Aug 92 14:00:33 CST
Distribution: world
Organization: Inland Steel Company; East Chicago, IN

In article <9208191732.AA11146@ucbvax.Berkeley.EDU>, HGK@PTBIB.BITNET (Hans G. Kerkhoff, PTB Institut Berlin) writes:
> My understanding is that VMS and ultrix is not widely used in universities and
> other research institutions compared to other unix derivations because of the
> administrative overhead caused by correctly using lmf.

In a word - poppycock! The "distaste" for VMS and Ultrix was in place long
before the introduction of the LMF.

> administrative overhead caused by correctly using lmf.

If you want to talk about administrative overhead, open your eyes. We 
just went through a main CPU upgrade for our VAX/VMS cluster. For the
most part, for those products which needed new licenses, the LMF
managed products came right up; the non-LMF managed products gave us
some form of trouble.

Many, many, many, of our third party software vendors are providing
some form of license management and access control. Most of them are
inventing their own schemes rather than use the LMF - even for products
that are designed to run only in a VAX/VMS environment.

I can kind of understand creating your own license management system if
your product is targeted for mutiple hardware/software platforms. But,
the bottom line is that we have about 15 different license management
schemes active in our cluster - three of which require an active
detached process running all the time!

Talk about administrative overhead!

--- Tom
Tom Allebrandi             | Mail guru   - DECUS UUCP Development Team
Inland Steel Research Labs | NFS grunt   - CMU/Tek-IP
East Chicago, IN           | Chairperson - VMSnet Working Group, DECUS VAX SIG
219 399 6306               | Internet:  allebrandi@inland.com
DECUServe: allebrandi      | UUCP:      ...!uunet!inland!allebrandi
From: hasan%avax.dnet@UNIVAX.FHDA.EDU (HASAN%AVAX.DNET@UNIVAX.FHDA.EDU)
Newsgroups: comp.os.vms
Subject: Set Forward via VMS MAIL
Date: 18 Aug 92 16:46:28 GMT
Distribution: world
Organization: The Internet


	Hello All,

		Is there a way in VMS MAIL to set forward to multiple
		accounts?

		From the MAIL help and the manual it seems that it
		can not be done.  But I want to confirm it anyway?

		I was hoping to issue a command like:

		MAIL> SET FORWARD LUCAS,DEBLER
		
		
	 	Any help or suggestions will be greatly appreciated!


	Note:
	====
		While I have this opportunity, I would like to thank all
		Who helped me out in running a  C program via detached
		process.  My question was related to the below given
		program which was trying to submit a C executable to run
		as a detached process.

	=====================================================================
   	$	set proc/priv=all
	$	ON CONTROL_Y THEN GOTO EXIT
	$	ON CONTROL_C THEN GOTO EXIT
	$!
	$	WS := WRITE SYS$OUTPUT
	$	PID = F$GETJPI("","PID")
	$!
	$ 	RUN/DET		 SYS$SYSTEM:LOGINOUT.EXE - 
  				/UIC=[1,4] -
				/INPUT = SS$EXE:CHECK_STUDENT_DIR.EXE -
				/OUTPUT = SS$LOG:CHECK_STUDENT_DIR.LOG -
				/ERROR  = SS$LOG:CHECK_STUDENT_DIR.LOG -
		  		/PROCESS_NAME = "Chkstudir" -
				/PRIORITY = 6 -
		       		/WORKING_SET=100 -
		       		/MAXIMUM_WORKING_SET=100 -
		       		/EXTENT=512 -
		       		/NOSWAPPING
	$!
	$ EXIT:
	$	EXIT 1 + F$VERIFY(SAVE_VER)
	=====================================================================

        Answer:
	======
                The solution which I recieved from you told me that I had
		two problems in the above procedure:

		1)  /INPUT  - Should point to a .COM file containing the
			      run statement for the .EXE and not to the
			      .EXE fiel itself.

		2) LOGICALS - SS$LOG, SS$EXE logicals which I was using
			      were not accessible to the detached process.

		After taking care of the above two problems, the program
		ran as expected via detached process.
		


		 //================================\\
		||        Syed Mahmood Hasan       ||
                ||                                 ||
                || hasan%avax.dnet@univax.fhda.edu ||
                ||                                 ||
		||    Foothill-De Anza Community   ||
		||         College District        ||
      		||     Data Services, Bldg - L71   ||
      		||     21250 Stevens Creek Blvd.   ||
      		||       Cupertino, CA 95014       ||
                ||                                 ||
		||         (408) 864-8242          ||
		 \\================================//
From: cohnen@fs1.rockefeller.edu (Stuart Cohnen)
Newsgroups: comp.os.vms
Subject: Help attaching AppleLaserwriter to  VMS
Reply-To: cohnen@rockvax.rockefeller.edu (Stuart Cohnen)
Organization: Rockefeller University
Date: Tue, 18 Aug 92 17:39:42 EDT

I know this has been before, In fact, I've done this before,
alas the mind losses cells after too many beers..

What do I have to do to make the Apple Laserwriter look
like an LN03R?  I know there is a mismatch in the password,
but what do I do about it?
Many thanks!

--
Stuart Cohnen   (cohnen@rockvax.rockefeller.edu) 
Manager of Engineering and Technical Services
Computing Services 
The Rockefeller University
From: kjb@calmasd.prime.com (Ken Brucker)
Newsgroups: comp.os.vms
Subject: Re: Backup and Tape Management Utility
Date: 21 Aug 92 17:24:31 GMT
Organization: Computervision - A Division of Prime Computer

In article <9653110919081992.A08742.POSSE.11689A4B3200*@mrgate.uwyo.edu>, ZUC03AA@corral.uwyo.edu (Jim Kirkpatrick) writes:
> In article <01GNOKTR962A9UMQ1U@LAGUNA.EPCC.EDU>, ARTG@LAGUNA.EPCC.EDU writes:
>>
>> We are looking for a Backup utility that has a Tape Management System with
>> it.  Since we have a C.S.L.G. through DEC, we'd like it to be a DEC
>> product.  However, third party software will be considered also.
>>
> 
> and Ken Brucker replies:
>>
>>Then take a look at SLS from DEC.  It uses the regular VMS BACKUP utility and
>>has a pretty complete tape management system built into it.
> 
> 
> This is not entirely correct.  SLS uses a "pirated" version of BACKUP to which
> source code modifications are made.  On our VMS 5.4-2 system, the version of
> SLS we are using writes tapes identifying themselves as being written by
> BACKUP version 5.3.  Thus, if you use SLS, you are using an "obsolete"
> version of BACKUP.  All those nifty patches CSC distributes to fix BACKUP
> problems, are of no use to the SLS user because the only way to get SLS to
> use a new version of BACKUP is to get a new version of SLS, which seems to
> be released roughly annually.  I'm aware of no cases where BACKUP patches
> caused a corresponding SLS patch.  Look in the accounting log, the image
> name isn't BACKUP; BACKUP is not callable.
> 
> What they *should* do, is modify BACKUP to support the features SLS needs
> such as smart reel switching, rather than stealing the source and modifying
> it.  But no, DEC can't be bothered to do a job *right*.

If DEC is still doing things similar to the way Tapesys did, they made a copy
of Backup as the startup ran and patched it.  The file name used the VMS
version as a piece of the name so the startup routines would determine that no
patch was needed if a "current" version was already available.

Back when I used Tapesys, I'd just remove the tapesys version of backup and it
would recreate it during the product startup.  Your mileage may vary since I'm
working on 3 year old information regarding Tapesys and not SLS.

I guess the point I was trying to make in saying that it uses the VMS backup
utility was that you'll wind up with tapes that you can use via Standalone
Backup and VMS Backup.  There are some backup/tape management systems out there
that use their own proprietary data format on the tapes so you have to be using
their product to read the tapes.

Ken

-- 
-------------------------------------------------------------------------------
**  Ken Brucker -- VMS/Ultrix Systems Programmer/Mangler -- Computer Vision
 **  kjb@calmasd.Prime.COM  
  **  Practice Random Kindness and Senseless Acts of Beauty
Newsgroups: comp.os.vms
From: kferg@vpnet.chi.il.us (Kevin Ferguson)
Subject: Re: ZMODEM help needed
Organization: Vpnet Public Access
Date: Tue, 18 Aug 1992 17:50:27 GMT

In article <1992Aug15.153957.6185@av8r.uucp> mrandall@av8r.uucp (Mark Randall) writes:

>> ...
>>     I have recently tried using rzsz9107.tlb. After setting everything up  
>>  and using the same command line (sz -L 512), I get the following: warning no 
>>  alt_typeahead. The download screen pops up and that is it. No bytes expected 
>>  or transfered. It just locks up at this point. Any ideas or suggestions?
>> 
>
>First, look at SYSGEN parameter **alttypahead** (or something like this -
>has a xxx_ prefix). This must be set to a reletively large value, from
>what I know. Then, do a SET TERM/ALTTYPAHEAD/PERM (again, check help - not
>exact). Then logout and log back in - you will be using the alternate
>typahead buffer limit. You can now use rz/sz successfully. Note that
>you cannot use this on a decserver or a DECwindow, as all sessions are
>virtual terminals (you won't get the same terminal when logging back
>in).
>

The SYSGEN parameter that sets the size of the alternate typeahead
buffer is TTY_ALTYPAHD.  We have ours set at 2048, which works just
fine for us.  

In order to specify the alternate buffer as the default, you need
to set a bit in another SYSGEN parameter, TTY_DEFCHAR2.  This lists
some of the default terminal cahracteristics.  Add the hex value
'80' to the current value of this parameter.  This will enable
altypeahd for ALL terminal sessions.

good luck,
kevin
From: leichter@lrw.com (Jerry Leichter)
Newsgroups: comp.os.vms
Subject: Re: VMS Mail - USERNAME Lookup Needed...
Date: 15 Aug 92 20:14:37 GMT
Distribution: world
Organization: The Internet


	[Discussion of using SET FORWARD to create useful alias names for
	users.]  Well, we actually use a command procedure to create all the
	combinations and remove any duplicates (wouldn't want John Doe and
	Jane Doe to get confused, so we wouldn't create a j.doe for instance).

Useful hack:  If you send mail to a forwarded address, and the address for-
warded to is invalid, the message shows the forwarding address, not the
original one.  This allows you to hide useful information in a forwarding
address.  Hence:

	MAIL> set forward/user:"j.doe" USE_JANE.OR_JOE.DOE

	MAIL> sen
	To:     j.doe
	No such user USE_JANE.OR_JOE.DOE

							-- Jerry
From: ewilts@galaxy.gov.bc.ca (Ed Wilts)
Newsgroups: comp.os.vms
Subject: Re: Photo v5.1-1 and CPUSPINWAIT bugcheck
Date: 20 Aug 92 13:13:07 -0700
Reply-To: EWILTS@GALAXY.GOV.BC.CA
Organization: BC Systems Corporation

In article <Bt9AIy.8AF@acsu.buffalo.edu>, tkslen@ubvmsb.cc.buffalo.edu (Lenny Miceli) writes:
> I just had a bugcheck on my vax 6520.  I called RDC and when they researched
> the problem they said it was PHOTO that caused the crash.
> 
> The bugcheck was CPUSPINWAIT, CPU SPINWAIT time expired.
> 
> The person from RDC said they have seen PHOTO cause this bugcheck before
> on multi processor machines.
> 
> So my question is, Has anyone else had this problem?  If so, is there a fix?
> I am running PHOTO v5.1-1 and VMS v5.5-1.

The current version of the Supervisor Series includes Photo v5.3.  It
explicitely states that it fixes this crash.

The new version is retrievable via ftp from ftp.spc.edu.  

-- 

Ed Wilts, BC Systems Corp., 4000 Seymour Place, Victoria, B.C., Canada, V8X 4S8
EWilts@Galaxy.Gov.BC.CA   |   Ed.Wilts@BCSystems.Gov.BC.CA   |   (604) 389-3430
From: tihor@acf3.NYU.EDU (Stephen Tihor)
Newsgroups: comp.os.vms
Subject: Re: Undocumented MAIL qualifier
Date: 20 Aug 92 02:19:00 GMT
Organization: New York University

That will depend on the Mail Transfer Agent you use.   If you use a MIME 
compatible MTA such as PMDf it should take the file, encode it, ship the 
encoded file to the other end, which hopefully decodes it and all is well.
From: SRDANIELS@RCKHRST1.BITNET ("SCOTT R. DANIELS")
Newsgroups: comp.os.vms
Subject: LINDO-(Math Package) For VAX's
Date: 18 Aug 92 16:08:27 GMT
Distribution: world
Organization: The Internet

Has anybody out there ever heard of LINDO for the VAX.  We have a version from
1986 on our VAX, and have been asked for information on the vendor.  A phone
number or address would be greatly appreciated !  Thanks in advance...

       _______     _______    _______   _______   _______         (__==__)
      / _____/\   / _____/\  / ___  /\ /______/\ /______/\          (oo)
     / /\____\/  / /\____\/ / /__/ / / \_/ /\_\/ \_/ /\_\/   /-------\/
    / /_____    / / /      / // / / /   / / /     / / /     / | K.C.|| (MOO...)
   /_____  /\  / / /      / // / / /   / / /     / / /     *  ||----||
  ______/ / / / /____    / /__/ / /   / / /     / / /         ^^    ^^
 /_______/ / /______/\  /______/ /   /_/ /     /_/ /        SRD@RCKHRST1
 \_______\/  \______\/  \______\/    \_\/      \_\/         SRD@RCKHRST2

+----------------------------+--------------------------+----------------------+
| Scott R. Daniels           |  Rockhurst College       |   +1 816.926.4065    |
| VAX/VMS Systems Programmer |  Kansas City, MO  64110  |   +1 816.926.4162    |
+----------------------------+--------------------------+----------------------+
From: fox@rudolf.nscl.msu.edu (Ron Fox)
Newsgroups: comp.os.vms
Subject: SUN RPC on VMS
Keywords: RPC
Date: 20 Aug 92 12:12:43 GMT
Reply-To: fox@rudolf.nscl.msu.edu (Ron Fox)
Organization: National Superconducting Cyclotron Lab.

--
  Does anyone know of implementations of SUN RPC on VMS? The underlying
transport mechanism would be TCP/IP via DEC UCX.
  
	Thanks,
	Ron
Ron Fox                     | FOX@MSUNSCL.BITNET      | Where the name 
NSCL                        | FOX@RUDOLF.NSCL.MSU.EDU | goes on before
Michigan State University   | MSUHEP::RUDOLF::FOX     | the quality
East Lansing, MI 48824-1321 |                         | goes in.
USA
From: brydon@asl.slb.com (Harvey Brydon (918)250-4312)
Newsgroups: comp.os.vms
Subject: Re: SET TRANSPORT command in VMS MAIL
Date: 14 Aug 92 12:31:24 GMT
Reply-To: brydon@asl.slb.com
Organization: Schlumberger/Anadrill Sugar Land, TX

In article <1992Aug11.143633.23348@ll.mit.edu>, jordan@ll.mit.edu writes:
>In article <1992Aug10.120547.838@slcs.slb.com>, brydon@asl.slb.com (Harvey
Brydon (918)250-4312) writes:
>>...            MX for example works for all cases except this one.  If you
>>have MX on your system and you specify SET TRANSPORT MX, you will have to
>                                        ----------------
>When I do this, I get:
>
>MAIL-E-ILLTRPT  MX is an invalid transport specification
>
>I have MX installed under VMS 5.5.     What am I doing wrong?

Sorry that should have been SET TRANSPORT MX%
____________________________________________________________________________
Harvey Brydon         | Internet:   brydon@dsn.SINet.slb.com
Dowell Schlumberger   | P.O.T.S.:   (918)250-4312
I bought my VAXstation from my uncle on his deathbead - I wrote him a check.
From: MRL@PFC.MIT.EDU (MARK LONDON)
Newsgroups: comp.os.vms
Subject: New LASER symbiont for postscript printers.
Date: 20 Aug 92 16:11:00 GMT
Distribution: world
Organization: The Internet

Sometime ago I announced that I had taken the postscript LASER symbiont and had
made many changes to it, including adding tektronix support.  I recently fixed
several bugs I had found with it, so I am announcing it again.  Anyone
interested in it should FTP it from PFC.MIT.EDU.  Some of the new features are:

	Automatic detection of postscript and tektronix files.  
	Notification and error messages broadcasted to user's terminal.
	Emulation of DECPrint PRINT/PARAMETER= commands.  
	Can specify start and end pages.  
	NUMBER_UP capability.
	HEADERS form modified to allow specifying font size and
	allow alternating left and right margins at end of page for
	double sided output.

If there is interest, I can post the sources here.
 
Mark
From: ARNE@ko.hhs.dk (Arne Vajhxj)
Newsgroups: comp.os.vms
Subject: Re: RE: get first name
Date: 17 Aug 92 06:55:00 GMT
Distribution: world
Organization: The Internet

> >You can not get the owner-fiels from SYSUAF by DCL (not until DEC implements
> >F$GETUAI !).
> 
> You sure about that?
> 
> $ if p1 .eqs. "" then p1 = f$getjpi(0,"username")
> $ say := write sys$output
> $ prv = f$setprv("sysprv")
> $ open/read/share uaf 'f$parse("sysuaf","sys$system:.dat")
> $ prv = f$setprv(prv)
> $ read/key=&p1/error=x uaf rec
> $ close uaf

I do know that, but I have apperently made some susumption, that you did
not make.

  - The user did not want to hardcode the first name in his com-file, so
    I assume that the com-file will be used by multiple users.
  - I assume that not many users have sysprv on that machine.

So that little (undocumented and unsupported - but who cares about that)
hack about reading SYSUAF.DAT do not sound as a good solution.

The good thing about SYS$GETUAI (and the lexical F$GETUAI - if it existed !)
is that you can extract information about your own user-name without any
privs !

                                                          Arne

Arne Vajhxj                             local DECNET:  KO::ARNE
Computer Department                     PSI:           PSI%23831001304030::ARNE
Business School of Southern Denmark     Internet:      ARNE@KO.HHS.DK
From: jim@mivax.mc.duke.edu (James D Dryfoos - Systems)
Newsgroups: comp.os.vms
Subject: Installing images?
Date: 21 Aug 92 14:24:00 GMT
Organization: Duke University Medical Center
News-Software: VAX/VMS VNEWS 1.41

Can one install any image (.exe)?  How do you decide which options
are needed (i.e.  /open/share/header ...).  What kind of problems
can one run into?

Thanks in advance, 

Jim 

*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
*  James Dryfoos  -- Medical Informatics - Duke University Medical Center     *
*                                                                             * 
*  VMS Systems Programmer -- Postmaster - Duke Electronic Medical Post Office * 
*  dryfo001@mc.duke.edu - dryfo001@dukemc.bitnet                              *
*  Box 2914 Durham NC, 27710 USA - EARTH (919) 684-6421                       *
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*

*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
* James Dryfoos  -- Medical Informatics - Duke University Medical Center      *
* VMS Systems Programmer -- Postmaster - Duke Electronic Medical Post Office  * 
*                                                                             * 
* INTERnet:  DRYFO001@MC.DUKE.EDU          BITnet: DRYFO001@DUKEMC            *
* INTERnet POSTMASTER: DMPM@MC.DUKE.EDU    BITnet POSTMASTER: DMPM@DUKEMC     *
* Concert Net DECnet:  MEDINF::JIM or 3073::JIM                               *
* Box 2914 DUMC Durham, NC  27710 USA, EARTH --  (919) 684-6421/fax 684-8675  *
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
From: ewilts@galaxy.gov.bc.ca (Ed Wilts)
Newsgroups: comp.os.vms
Subject: Re: Posix device name problems
Date: 12 Aug 92 08:20:43 -0700
Reply-To: EWILTS@GALAXY.GOV.BC.CA
Organization: BC Systems Corporation

In article <1992Aug12.134322.25179@constellation.ecn.uoknor.edu>, dwight@geohub.gcn.uoknor.edu (Dwight D. Moore) writes:
>> 
>> 	/dummy_path/disk2/whatever
>> 	/dummy_path/bcsc$disk2/whatever
> 
> You should probably try to avoid file system names in UCX/POSIX that contain
> a "$" since the shell will recognize this special character unless escaped with
> a 
> backslash. This will try to translate bcsc$disk2  using the shell variable
> $disk2 (if
> one exists, else it will translate to empty space). This isn't a problem for
> people
> who know better, but that can really confuse alot of users.

I ran into this already.  It's ugly but the logical name standards are so well
entrenched in this site (and before my time) that we're stuck with them :-(. 
The lucky thing is that normally only the device name has the $ in it.  When I
invoke the Posix shell, the device is translated to its original mount point
name anyway:

$ ucx bind disk1 "/disk1"
$ def/sys/exec/trans=(conc,term) disk1 falcon$dua1:
$ set def bcsc$disk1:[test]	
$ posix
psx> pwd
/disk1/test

So much for concealed logical names...
-- 

Ed Wilts, BC Systems Corp., 4000 Seymour Place, Victoria, B.C., Canada, V8X 4S8
EWilts@Galaxy.Gov.BC.CA   |   Ed.Wilts@BCSystems.Gov.BC.CA   |   (604) 389-3430
From: tihor@acf3.NYU.EDU (Stephen Tihor)
Newsgroups: comp.os.vms
Subject: Re: Undocumented MAIL qualifier
Date: 17 Aug 92 23:15:00 GMT
Organization: New York University

With SEND/FOREIGN
From: paul@lsl.co.uk (Paul Hardy)
Newsgroups: comp.os.vms
Subject: Re: VFE file editor
Date: 21 Aug 92 08:35:03 GMT
Organization: Laser-Scan Ltd., Cambridge

In article <1992Aug20.135131.27021@news.iastate.edu>, gvrod@isuvax.iastate.edu (R Eldridge, VMS FOREVER) writes:
> In article <1992Aug20.131008.2321@lsl.co.uk>,
> paul@lsl.co.uk (Paul Hardy) writes:
>>[...text deleted...]
>>
>>However we now have a need to use VFE to modify the last block of a 17MB ascii
>>file, and can't remember how to persuade VFE to open a file for write. I have
>>tried the obvious things of /WRITE, /UPDATE, -w, etc before and after the
>>filename but no joy. The HELP facility is good but lacks this vital piece of
>>information. I haven't got a FM to RT!
>>
>>[...more text deleted...]
>>
> If you have the symbol VFE defined as  a foreign command, the  following  is
> the full format of the VFE command:
> 
>      $ VFE [/set-options] [filename] [/file-qualifiers]
> 
> For example:
> 
>      $ VFE/NOCASE/RADIX=HEX/LOG=FILEX.LOG FILEX.DAT/WRITE
> 
> rod eldridge
> vms systems support      gvrod@isuvax.iastate.edu
> iowa state university    gvrod@isuvax.bitnet    
> (515) 294-7498           fax: (515) 294-1717

The above is true for VFE version 2, which Rod kindly sent me. However,
buried in the documentation for version 2 was a note about enhancements over
the 1984 version 1 VFE (which is what I had). In there it gave the vital clue,
which is that to enable write access, you precede the filename by a #
character! eg

$ VFE #MYFILE.TXT

I would never have guessed !
-- 
Paul Hardy, Chief Programmer, Laser-Scan Ltd, Science Park, Milton Rd, CAMBRIDGE
CB4 4FY, England. Tel (+44) 223 420414; Fax (+44) 223 420044.
Email: paul@lsl.co.uk via JANET, or VAX PSImail DTE 234222300203::PAUL.
Newsgroups: comp.os.vms