[Info-vax] : AUTHORIZE Enhancement

[IanD]

On Friday, November 25, 2016 at 12:31:39 AM UTC+11, Baldrick wrote:
> On Sunday, 20 November 2016 06:28:49 UTC, IanD  wrote:
> > On Sunday, November 20, 2016 at 4:37:54 AM UTC+11, Art wrote:
> > > While we're asking for shiny new things from VMS, could I ask for a simple (?) change whereby the output from e.g. MCR AUTHORIZE LIST * /FULL could be "enhanced" with /OUTPUT=SOMEWHERE_OTHER_THAN____SYSUAF.LIS ?
> > > 
> > > I know I can do DEFINE SYS$OUTPUT etc. but c'mon, /OUT= please.
> > > 
> > > Thanks in advance,
> > > Art
> > 
> > Can we also add support for input/output in other formats also?
> > 
> > I'm thinking not just UAF but every utility in VMS (in your spare time of course!)
> > 
> > i.e.
> > 
> > mc authorize list */out=x.x/format=CSV
> 
> I write DCL to "process" the output of various utilities into CSV files, or even COM files to make bulk but controlled changes, everything from UAF to SH DEV D and with a number of the utilities i want to interact with not even having a /OUTPUT I just redefine SYS$OUTPUT. Search (don't forget /MATCH=NOR), sort, f$element and the myriad of other lexicals make light work of text processing. But there's TPU too. I haven't bothered learning it, i stick to EDT (and TECO sometimes) for my editing.
> 
> baldrick

If VMS moves to an object based system with deep seated class structure then we could move towards universally accepted forms of data information interchange too, like csv, XML and lately json

Linux get away with things because pretty well everything is a stream file, including devices so redirection is dead easy. VMs is painful compared to this because it's recorded orientated 

it then become even more painful when you move around workplaces because unless you develop tools in your own time, they are not transportable so you end up on the endless treadmill of DCl command procedure writing wherever you go instead of the environment supporting the easy information interchange