Browse Prior Art Database

Automatic Quiescence of Daily Computerized Functions

IP.com Disclosure Number: IPCOM000040983D
Original Publication Date: 1987-Apr-01
Included in the Prior Art Database: 2005-Feb-02
Document File: 2 page(s) / 13K

Publishing Venue

IBM

Related People

Pence, JW: AUTHOR

Abstract

A computer system uses daily automatically instituted program executions. Batch jobs can take a lot of the computer resources and executions easily be interfered with by the automatically instituted program. This contention can be alleviated by the automatically instituted program execution segmenting its execution at a plurality of benchmarks. At each benchmark, the time of day is accessed and compared with the time to run the next segment and the time for certain automatic program starts. The automatic daily execution continues only if sufficient time remains for completing its next not interruptible segment.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Automatic Quiescence of Daily Computerized Functions

A computer system uses daily automatically instituted program executions. Batch jobs can take a lot of the computer resources and executions easily be interfered with by the automatically instituted program. This contention can be alleviated by the automatically instituted program execution segmenting its execution at a plurality of benchmarks. At each benchmark, the time of day is accessed and compared with the time to run the next segment and the time for certain automatic program starts. The automatic daily execution continues only if sufficient time remains for completing its next not interruptible segment.

There are several functions that are run daily in a computing center. Normally they complete in their allotted time. However, when they do not, they can interfere greatly with the functions that are beginning to run. Functional capabilities usually exist to stop the incomplete daily automatic program execution (daily function). However, that requires an operator be available to determine whether or not the daily function needs to be stopped and knows the command to do it. Many times the granularity of the command available to stop the daily function is not that which is desired. For example a CANCEL which immediately abends a job is not desired when you only need to stop within approximately 15 minutes.

The requirement is not to stop all of the daily functions at exactly this instant because the production load normally goes through a gradual building up process as users arrive and sign on the system. The requirement is therefore only a quiescing or phasing down of the daily function's load on the system whi...