IBM System/370 Operator's Reference Manual page 196

IBM 1403 Printer (cont'd)
Th~
program should provide an operator message and exit from this error recovery
procedure when the end-of-forms indication is detected. The operator should then
perform a forms runout (as just described) and satisfy the requirements of the appli·
cation program.
5. Sync check. This condition can occur whenever the print chain (or train) is
out of synchronism with the print circuitry in the 2821. Depending upon
when the sync check occurs, one of the following conditions exists:
a. The sync check occurred when no printing was in progress (no line was
printed).
b. The sync check occurred during a print operation and one line was
printed.
c.
The sync check occurred during printing and two lines were printed.
The program should provide an operator message and exit from this error
recovery procedure. The operator should then:
a.
Correct the not·ready condition (press the Check· Reset key and then the
Start key) and allow the application program
to
proceed without further
retries of the command, or
b. Correct the not·ready condition (press the Check Reset key and then
the Start key) and restart the program from a logical point.
If the error persists, a call should be made to the Customer Engineer.
Data check indicates that a code in a data record sent to the printer does not match a
code in the UCS (Universal Character
Set)
feature storage. Printing does not occur in
the print position to which the unmatching code applies. The entire line (except for
me
data
cneck
position) or only a portion oT the iine may be printed. ThereTore, the
last printed line may contain erroneous data
and/or an
incomplete record. Data check
generally indicates that the UCS storage was improperly loaded or that a data record
code (other than blank or null) does not compare
to any code in the UCS storage.
The program should provide an operator message and exit from this error recovery
procedure. The operator should then:
1.
Accept the record and indicate that the application program is to proceed
without further retry of the command, or
2.
Cause the application program to restart from a logicat point.
If the error persists, a call should be made to the Customer Engineer.
Parity Check
This bit indicates that a parity error has been detected in the UCS feature storage.
The parity d-.eck can be reset only if the UCS storage is raloaded.
If the parity check occurs while the UCS storage is being loaded,
retry
the operation
once. If the error persists,
a
call should be made
to
the Customer Engineer.
If the parity check occurs during printing, the last print line may contain erroneous
data. Provide an operator message and exit from this error recovery procedure. At this
time, the operator should:
1.
Accept the record, cause the program to reload the UCS storage and proceed
without further retry of the command, or
2. Cause the program to reload the UCS storage and restart the program at a
logical point.
If the error persists, .. call should be made
to
the Customer Engineer.
Page 5-40