RUN SHEET.- The run sheet contains the pro-gram name or names and the job or task number under which the job (or system) is to be executed or run. In addition, it indicates all of the inputs: magnetic tapes, disks, and diskettes required, depending upon the type of run or possible options the user selected. There could be one or several magnetic tapes and/or disk files needed for the job. You might be required to retrieve them from the media library, or you might just lookup the tape/disk numbers and annotate them on the run sheet.

CONTROL PARAMETERS.- The task folder will also indicate any parameters that are required. These parameters provide application programs with variable information, data elements that change from one run to the next. For example, the type of run requested: 

(D)aily, (W)eekly, (M)onthly, (Y)early, (E)dit input only, and so on, or the entering of a date. You maybe required to key in one or several of these parameters, depending upon the complexity of the system.

OUTPUT REQUIREMENTS.- The task folder and/or the computer run sheet show you all of the output products: magnetic tapes/disks, and special forms that are produced during the running of the job or system. As an I/O control clerk, you maybe tasked to provide the computer operators with the correct number of blank, handwritten, or preprinted output tape/disk labels and ensure a sufficient supply of tapes, disks,

paper, and special forms are on hand before the job or system is scheduled to be run.

Job Monitoring

Although we would like to believe all jobs run without error, there are occasions when a program

prematurely or abnormally terminates. It does not process to normal end of job (EOJ). When this occurs, the operator is expected to take whatever corrective actions are necessary to get the job going again. More often than not, the operator is able to recover a job by recreating a tape/disk file, moving the file to another device, or possibly cleaning the read/write mechanisms of the device prior to rerun. But, there are times when the operator will notify you (the I/O control clerk) to assist in correcting the problem. Such would be the case when the input parameters are in error, the user's input is bad, or the job aborted because of an unrecoverable program error. If this happens, you maybe responsible for collecting all the data, both input and output, along with any memory dumps, and forwarding them all to the programmer.

During the recovery phase of an operation, the operator may need you to provide certain input parameters or tape/disk files before the job can be executed. Because of time constraints, a job that abnormally terminates may have to be rescheduled. If so, you may be responsible for seeing to it that the job gets rescheduled and that the user is notified of any job delay. We could go on and on, but by now you are beginning to get the picture. These examples are just a few of the many things that can get in the way of achieving a normal EOJ. We bring them to your attention to make you aware of the types of problems that can and do arise, and the manner in which you are to respond. Hopefully, you now know and are aware that monitoring a job means more than just calling up the operator to see how the job is progressing. It means you must oversee the job to its completion, doing whatever is necessary to help keep the job (or system) on track.

Output Products

Output from computer processing-The work that has been completed-may take the form of a printed document, magnetic tape, or magnetic disk or diskette. In all cases, both you and the computer operator are responsible for ensuring that all completed jobs run successfully. In addition, you are responsible for identifying and coordinating the various outputs for each job, and for initiating their correct distribution.

To determine whether a job (or system) ran successfully (to a normal EOJ) and that all processing steps were properly performed, you may have to review the computer console printout. This printout indicates such things as the number of input records read, the various input files updated, all error conditions (error messages) that the operator encountered during the run

and the resulting actions taken, the various output files created, and so on.

In the majority of cases, the computer console print-out will provide you with the answers you are looking for when it comes to reconciling processing discrepancies. For example, it will inform you of the reasons certain output products-tapes, diskettes, or report listings- were not produced. Possibly the operator selected an incorrect program option, or the input parameters were incorrect or incomplete before starting the job. In short, you are responsible and also accountable for every job you work on, from the time it is submitted by the user until its delivery back to the user.

When checking the user's output, you should once again refer to the run sheet and/or task folder to verify that all items requested were, in fact, produced. If the output is in the form of magnetic tape, disk, or diskette, be sure it is labeled properly, given the proper classification, and it is on the appropriate media (magnetic media that has been designated for mail-out or distribution only).

When checking reports, make sure they were run on the proper forms (size and type), that no pages are missing and the correct number of copies were printed, and that all print is legible and lined up properly.

Once the output is checked, you then package each completed copy of the report, along with any other out-put products and the original input, place it in the proper pickup area, and log the job out in the job control log. You may need to notify the user when the job is ready.

If, during the course of checking over the user's output, you happen to come across something unusual or you find an error, by all means, pull (reject) the job immediately, bring it to the attention of your superior, and notify the user of the delay. Even at this late stage, it is better to reject a job to correct any problems or discrepancies rather than to release it, only to have it returned for rerun later.