Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!gryphon!cadovax!gregn
From: gregn@cadovax.UUCP (Greg Noel)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: IBM bug notification/update policy
Message-ID: <2408@cadovax.UUCP>
Date: 21 Aug 89 17:44:55 GMT
References: <550@pan.UUCP> <6473@stiatl.UUCP>
Reply-To: gregn@cadovax.UUCP (PUT YOUR NAME HERE)
Organization: Contel Business Systems, Torrance, CA
Lines: 21

In article <6473@stiatl.UUCP> tom@stiatl.UUCP (Tom Wiencko) writes:

>This is not the best one.  Back in the days when I used to submit a lot of
>APARs (Authorized Program Analysis Reports, aka bug reports) IBM had a classic
>way of closing a report they did not want to fix.  You ready for this?  Better
>sit down.
>
>"We are closing your APAR as an undocumented restriction."
>

There is a problem with AIX (2.2.x), when you make an open call to open
the parallel printer port you get back a file identifier, no matter the 
state of the printer (let's say Nebraska).  The open call will NOT fail.
After talking to support and four weeks I got a call back:

"We are closing your APAR as an permanent undocumented restriction."

The write to that file identifier creates a whole other set of problems...
--
Greg Noel [Gn] 	Versyss, inc., Torrance, Ca.
Nothing Works, and Nobody Cares.  -W Allen