home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 16 Announce
/
16-Announce.zip
/
defect.zip
/
defect.txt
Wrap
Text File
|
1993-07-21
|
5KB
|
125 lines
Rick & Everyone who might deal with OS/2 Defect Support:
Here is the official response to a list of questions I generated that
outlines the services provided by OS/2 Defect Support. I apologize
for the delay, but I they had managers on vacation, I had to ask for
clarification, etc, and finally came up with this list of questions
that I think will answer everyone's questions about 'What can I expect
from OS/2 Defect Support'. This list has been approved by their
management so it's the official word. I will be more than happy to
forward and followups to this note directly to them for their
information and for their comment. I will also upload this into the
IBM Files section for permanent reference.
Terms:
* They: Compuserve developers (y'all)
* PMR: Problem Management Report - Initial user bug report, no
confirmation of bug by IBM yet.
* APAR: Authorized Program Analysis Report - bug has been confirmed
and problem is sent to development for fix.
* RETAIN: IBM's internal bug tracking system
----------------------------------------------------------------------
1) Should they expect to supply a testcase only when it's reasonable
for the support person to need one? If so, is there a definition of
"reasonable"?
Ans: If the problem can not be recreated using standard system
functions,then a testcase will have to be provided to show the error.
2) Should they expect to get a response back with a PMR number? What
is the timeframe for this?
Ans: a pmr number will be given to the customer when they first call
in. Compuserve users: The user should receive notice of the PMR
number within 24 hours. Usually all Compuserve entries receive either
the PMR number or an answer within 2 days. Difficult problems will
require more time to resolve, so for those,there will be a greater gap
between PMR notification and the actual problem resolution.
3) How can the customer be assured that the PMR will not simply scroll
off RETAIN after 28 days of no activity?
Ans: the customer needs to be sure to instruct the support person to
keep the pmr in an open status. if they agree to close the problem,
it will be purged after the 28 day period. if an apar is assigned,it
should be kept open by default.
4) Should they expect to have to initiate contact to get status on
their PMR? How often should they be expected to do this?
Ans: this should be an agreement between the customer and the support
rep. after an apar has been created,there would be no automatic
status update to the customer until the apar is closed.
5) Should they expect to get notification when the PMR graduates to an
APAR? What is the timeframe for this?
Ans: yes, depends on severity.
6) Should they be able to get a reasonable Severity level for their
APAR? If so, what are the Severity Levels and how are they
prioritized?
Ans: agreement on severity should be reached between the customer and
the support rep.
sev 1 = unable to use, major feature/function not available.
sev 2 = feature/function restricted, workaround may require
considerable effort.
sev 3 = feature/function has minor restrictions, problem can be
avoided. workaround provided.
sev 4 = little or no impact, can be circumvented.
7) Should they expect to get a response back with a workaround if one
is discovered?
Ans: yes
8) Should they expect to get a response back when a private fix is
made available? Under what circumstances will a company be able to
provide a private fix with their product?
Ans: it would depend on the agreement between the customer and the
support rep. a private fix is not usually sent.
9) Should they expect to get a response back when a public fix is made
available? (Not a CSD, but a small fix file like 21WPSF)
Ans: they would get a response when the apar closes.
10) Should they expect to get a response back when a CSD is made
available?
Ans: all customers on the interested parties page of an apar will be
notified.
11) Should they expect to get a response back when a new version of
OS/2 is made available?
Ans: no
12) If the user encounters any problems with the defect reporting
process, who should they contact to get resolution? Such problems may
include unreasonable test case demands, lack of speed handling the
problem report, lack of speed getting from PMR to APAR status, decline
of a problem for APAR status, lack of speed getting the problem fixed,
lack of a reasonable fix strategy, etc.
Ans: call the 800 number and ask for a duty manager.
13) What is the benchmark time in days for getting a fix back to the
developer for each of the Severity levels, and what is Boca's history
in maintaining these times?
Ans: all apars should have a fix associated to them within 30 days.
sev 1's are worked first followed by 2's . depending on volumes this
time period may vary.
----------------------------------------------------------------------
Mike Brown
IBM OS/2 2.1 Developer Technical Support