TIP: Click on subject to list as thread! ANSI
echo: os2prog
to: Jeffrey White
from: Mike Bilow
date: 1996-06-06 23:07:14
subject: How does one APAR OS/2 ?

Jeffrey White wrote in a message to MIKE BILOW:

 JW>   Subject: Re: Dive APAR Bug List !
 JW>   Date: Mon, 3 Jun 1996 22:29:53 -0400 (EDT)

  >   Please forward a copy to me of all the bugs you have concerning DIVE
  >   and/or DART and the APAR number for each bug (you should have alot
  >   of APAR numbers) that IBM gave you when you reported each bug  !

 JW>   Jeffrey,  The whole list of DIVE bugs was handed to an IBM
 JW> manager.   He recieved a total of (I think) 3 APARS for this
 JW> list of bugs.   IBM just isn't interested. If I find the
 JW> buglist at home I'll mail it to you. 

 JW>   **********

 JW>   How should have the above been handled ?

An APAR is not created for each bug report at the time of reporting. 
Usually, a bug report is assigned a PMR number which identifies it as a
"problem report" and provides for its tracking.  A PMR might look
like "1234X,PSB".

If the PMR is escalated and IBM is able to reproduce the problem, it is
evaluated to see if it is the same problem as one which has previously been
reported and which already has an APAR.  If your PMR proves to be new, then
you get an APAR assigned.
 
-- Mike


--- 
* Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107)
SEEN-BY: 50/99 270/101 620/243 711/401 409 410 413 430 808 809 934 955
SEEN-BY: 712/407 515 517 628 713/888 800/1
@PATH: 323/107 396/1 270/101 712/515 711/808 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.