Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!emory!dtscp1!scott
From: scott@dtscp1.UUCP (Scott Barman)
Newsgroups: comp.unix.questions
Subject: Re: Unix deficiencies/problems
Message-ID: <676@dtscp1.UUCP>
Date: 7 May 89 06:45:39 GMT
References: <810038@hpsemc.HP.COM> <810046@hpsemc.HP.COM> <159@dg.dg.com> <424@algor2.UUCP>
Reply-To: scott@dtscp1.UUCP (Scott Barman)
Organization: Digital Transmission Systems (a subsidiary of DCA), Duluth, GA
Lines: 23

In article <424@algor2.UUCP> jeffrey@algor2.UUCP (Jeffrey Kegler) writes:
 >In article <810046@hpsemc.HP.COM> gph@hpsemc.HP.COM (Paul Houtz) writes:
 >>gph@hpsemc.HP.COM (Paul Houtz) / 10:37 am  Apr 18, 1989 /
 >>
 >>I wrote:
 >>   I am interested in peoples opinions of deficiencies or problems with 
 >>unix.  . . .  
 >
 >I miss very little from the IBM world, but the availability of formal file
 >names is one of them.  Once UNIX starts getting into commercial
 >environments they will become more useful.  Briefly, a formal file name is
 >a name by which the program interfaces with a  JCL (or shell) language and
 >which can be redefined.  UNIX has 3 usable ones, stdin, stdout and stderr,
 >and that covers a remarkable variety of situations.  But an application

Is this anything like trying to remember which utilities wants their
input from ddname SYSUT1 or SYSIN?  Or ourput to SYSOUT or SYSPRINT
or even SYSUT2?

I do not miss anything from that world!!!!
-- 
scott barman
{gatech, emory}!dtscp1!scott