WebSTAT - Free Web Statistics

Memorandum

The following is a result of a "urinary tradjectory competition" between three entrenched Computer organizations. The problem was that there was a bad tape produced one week, by job DRW100, to backup files. When it was needed, it was found to be bad, and then all the finger pointing resulted. Our Data Base Management and Administration person spent half a day composing the following. Enjoy!!

September 2, 1977

City Phoenix

Office DBMA

Subject: Verification of Production Runs

Regarding the checking of DRW100 for IMS Library backup, if Production Control are the checkers checking proper run results, then, is it implied that DBMA be checkers checking the checkers' checking? If so, then DBMA would be checker checkers. But if Technical Support is responsible for backup and recovery of these Libraries, shouldn't they be the checker checkers? Alternately, either of us could check the checker checkers' checker checking, in which case the other party would be checker checker checkers. Then, the real question is that if a checker checker checker could check a checker checker's checker checking, then how many checker checker's checker checks could a checker checker checker check if a checker checker checker would check the checker checker's checker checking?

"Any Mouses" Data Base Management & Administration

An alternate parsing of the syntax:

Regarding the checking of DRW100 for IMS Library backup, if Production Control are the checkers checking proper run results, then, is it implied that DBMA be checkers checking the checkers' checking? If so, then DBMA would be checker checkers.

But if Technical Support is responsible for backup and recovery of these Libraries, shouldn't they be the checker checkers?

Alternately, either of us could check the checker checkers' checker checking,
in which case the other party would be checker checker checkers.

Then, the real question is that if a checker checker checker
could check a checker checker's checker checking,
then how many checker checker's checker checks
could a checker checker checker check
if a checker checker checker
would check the checker checker's checker checking?

What started it all

Memorandum

November 21, 1977

City: Phoenix

Office: Technical Support

Subject: Verification of Production Runs

To: B.S.

It was necessary to restore an IMS library this weekend. This library is backed up weekly by DRW100. For the past three weeks, the production run has not completed successfully. The reasons are:

1. STEP010 had a condition code 4 because the IEBCOPY had an I/O error attempting to unload the data set.

2. STEP020 was not run because of condition codes.

These errors occurred on the weekly runs of 11/1/77, 1/8/77 and 11/14/77.

These errors, left undetected, required the libarary to be restored to data of a month ago (10/25/77). A copy of this weekly run is distributed to area 95 (DBMA). It has obviously not been checked properly by either Production Control or DBMA. If we are to ensure the integrity of our libraries, it is imperative that more care be taken in verifying the backups.

J..., Manager

Technical Support

(9-5-2001 webstat)