Home » Currently Reading:

AKC03: Batch Job Flows & Processing Schedules

Description:

Documents the application’s batch jobs and the batch processing schedules. The flow within the batch job is documented for those jobs that are designated as critical or important. Provides the application support analyst a view of the batch processing jobs/flows (if available), dependencies and schedules. This helps the support analyst in fault identification and re-start points. It also provides a good understanding of the batch processing cycles.

Provides understanding of the structure and flow of batch jobs; describes files and databases passed or accessed by each job. Provides information such as:

  • Job JCL/Script Name
  • Brief Job Description
  • Schedule description (i.e.: Daily, Weekly, Monthly, Quarterly, On Request)
  • Jobs that must complete first or any other requirements
  • Jobs depending on the completion of the current job

How is it used?

Provides the application support analyst a view of the batch processing jobs/flows (if available) dependencies and schedules. This helps the support analyst in fault identification, re-start points and a good understanding of the batch processing cycles which are required for production and also batch job/program testing.

Why is it important?

(1) Batch jobs are the application components most prone to failure and most difficult to diagnos if their structure and timing requirements are not known.
(2) Provides understanding of the structure and flow of batch jobs; describes files and databases passed or accessed by each job.
(3) Provides the support analyst a roadmap to each of the critical batch job flows and the indivieual step dependencies and normal EOJ requiremants. Timing for the job, programs, DB/Files used, job fault indicator conditions, restart points.
(4) AKC03: Batch Job Flow content area provides information such as:

  • Job  Name
  • Brief Description of Job
  • Daily, Weekly, Monthly, Quarterly, On Request
  • Jobs that must complete before this one or any other requirements that must occur
  • Jobs depending on the completion of this job
  • Programs, DB/Files used in the job
  • Normal EOJ conditions

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...