Re: Supported Documentation

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@xxxxxxxxxxx] On
Behalf Of Martin Kline
Sent: Tuesday, April 29, 2008 9:13 AM
To: IBM-MAIN@xxxxxxxxxxx
Subject: Supported Documentation

Does anyone know why IBM refuses to update their documentation any more?

Once documentation is shipped, it is never supported. I have had this
problem several times in the past few years. The software is not working
as documented, but the support center determines the doc is wrong, not
the code. They tell me they will put in an untrackable request to update
the documentation in a future release. Meanwhile, the current
documentation still is incorrect, leading to additional customer
problems. I can't be the only one who runs into this issue. Occasionally
they will open a DOC apar, but that isn't worth the "paper" it's written
on, since it's impractical to search for DOC apars for every topic in
every manual you use. Maybe it sounds like I'm whining, and a couple
beers might help, but it won't fix the production outage that occurred
because of incorrect documentation.
<snip>


Choir -- preaching. Yes, I have the picture, but IBM management somehow
doesn't.

Notice that the PoOP does get new dash numbers. So do certain other
manuals that do not depend on software development cycles. DOC errors
and fixing seem to not be viewed as a defect that must be fixed. So this
means that there is a "Lack of budget" which to me is "Poor planning",
or the ubiquitous PC mentality where the doc is updated on some obscure
site that the users are supposed to know about (something about tech
notes, but some how each group has their own) -- but is not attached to
the Library site that we all seem to go to to down load the latest...

Regards,
Steve Thompson

-- All opinions expressed by me are my own and may not necessarily
reflect those of my employer. --

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

.

Relevant Pages

  • Re: Swing Migration from SBS 2003 to new SBS 2003 box
    ... If a typical migration used to ... You can swing from a plain old NT4 non-Exchange domain to a 2003 ... Microsoft offered nothing like this in the form of documentation, ... they did not want to support the process I had outlined, ...
    (microsoft.public.windows.server.sbs)
  • Re: Swing Migration from SBS 2003 to new SBS 2003 box
    ... If a typical migration used to ... You can swing from a plain old NT4 non-Exchange domain to a 2003 ... Microsoft offered nothing like this in the form of documentation, ... did not want to support the process I had outlined, ...
    (microsoft.public.windows.server.sbs)
  • Re: Umove to Migrate SBS to new hardware
    ... Anyone interested can ask around to get opinions on Swing Migration from ... In my documentation, I cite background KBs and whitepapers constantly to ... support, even if I was walking them through the ADMT paper or something else ... provided a proper tool to migrate SBS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: ASP .NET 2.0 Unanswered questions...
    ... can you provide any documentation to support your results? ... upset towards me when all I've done is present more evidence and logic to support my case. ... I think it's a matter of deductive reasoning and facts. ... I've told you that for five years now, I've used the code-behind model ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Migrating from SBS 2000 to SBS 2003 onto new hardware
    ... First, you posted a request for Swing Migration, but perhaps you didn't know ... Microsoft offered nothing like this in the form of documentation, ... they then or will they now provide you support in doing a "Swing Migration". ... "Microsoft Small Business Server 2003 Advanced Best Practices" ...
    (microsoft.public.windows.server.sbs)