$   Parity Errors? Operator Requests?   The Question is:    E During a scheduled back-up I recieved these errors in my back-up log:    P %BACKUP-W-DENSITY, MKA500:[000000]DATA1.; does not support specified density - d3 %BACKUP-E-FATALERR, fatal error on MKA500:[]DATA1.;  -SYSTEM-F-PARITY, parity error %BACKUP-I-OPERSPEC< %BACKUP-I-OPERASSIST, operator assistance has been requested   M I understand that these are probably caused by a bad tape in the drive. On my   monitor I see:    5 %BACKUP-I-OPERSPEC, specify option (quit or Continue)   _(cursor blinking w/o $(prompt))/ How do I specify an option to quit or continue? J What is the exact syntax to use with /REPLY modifier at the DCL prompt($)?     The Answer is :   A   Parity errors are usually caused by tape errors, or by problems A   with the tape drive or related I/O hardware.  If a new tape and C   (as applicable) a cleaning of the tape drive do not resolve this, B   please contact your hardware services organization for assitanceB   with resolving hardware errors.  (There are other discussions of(   parity errors here in Ask The Wizard.)   G   Your BACKUP is apparently running with the /ASSIST qualifier enabled, "   either explicitly or by default.   E   When running with /ASSIST enabled, you can use REPLY/TO=id CONTINUE :   or REPLY/TO=id QUIT, or such, from an operator terminal.   ?   To enable an operator terminal, use the command REPLY/ENABLE.    C   For further information on this and related topics, please review    the OpenVMS documentation.   0  Answer written or last revised on  19-MAR-2004 