Home » Currently Reading:

AKC13: Troubleshooting Utilities and Programs

Description:

This is a list of any unique programs or jobs used to assist in the support of the application. These are specialty programs that may be written in-house by the support staff for this purpose or supplied by a software vendor. These programs or routines are designed specifically to the application’s database. Documenting these programs is crucial to a smooth rotation of application support staff. Most businesses and almost all programmers have Troubleshooting Utilities or personal utility programs. These help identify problem areas, track a particular function or data and identify probable causes or remediation.  Many of these are in personal programmer libraries and are only known by them. This section documents those used on a reoccurring basis and how to use them to diagnose or fix a specific problem type.

  • Provides understanding of what tools exist to help solve problems when they occur.
  • Provides information such as:
    • Name of the program, routine, job, utility, debugger, etc.
    • Libraries where the Source and executable Components exist
    • Brief description of when and how the Component is used
    • Sample output for specific problem types and a description of how that output is used to “Troubleshoot”  – diagnose and solve – the problem

How is it used?

Most businesses and almost all programmer have Troubleshooting Utilities or personal utility programs. These help identify problem areas, track a particular function or data and identify probable causes or remediation.  Many of these are in personal programmer libraries and are only known by them. This section documents the ones which re used on a regular or reoccurring basis and how to use them to diagnose or fix a specific problem type.

Wht is it important?

(1) Provides the applicaiton support analyst a list and the  location for all troubleshooting untiities and programs used in supporting the applicaiton. In this way any support analyst in the team can locate and use utililities or programs without having to “re-invent the wheel” or waste time trying to figure out how which utilits are available for this application.

(2) Provides understanding of what tools exist to help solve problems when they occur.
(3) Provides information such as:

  • Name of the program, job, utility, debugger, etc.
  • Libraries where the Source and executable Components exist
  • Brief description of when and how the Component is used

Our Sponsors

IT Support Services Comments

  • Bob Anderson: Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the ...
  • Bob Anderson: Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Compute...
  • Bob Anderson: Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you...
  • Bob Anderson: Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on...
  • Bob Anderson: Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, an...

ITIL V3 Application Support Q & A

If you have any question on the blog content or have some specific question on how ITSM & ITIL can dramatically improve performance and reduce the cost of your Application Support service "Ask Bob"
Question :
Answer :
Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Computer World on "How to create Meaningful IT Support SLA's"  use this link...
Question :
Answer :
Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the folks who developed the original CMM  were not really initially inter...
Question :
Answer :
Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you want to be "proactive" in stopping this practice" you must capture bu...
Question :
Answer :
Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, and how many technical support calls from users you get and the average...
Question :
Answer :
Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on their own without any instruction to do so and it affects other user...