7502
Bad tape format (Bad length for a DP1 tape file label).
Cause.
An attempt was made to restore a tape, but a BACKUP tape in the proper format could not
be found. There are three possible reasons:
•
BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP
tape. The "Bad Tape Format" was detected when unwanted or meaningless information was
encountered at the interruption point on the tape.
•
The BACKUP tape was corrupted in some way.
•
Either BACKUP produced an invalid tape or RESTORE is not checking correctly due to a
software error.
Effect.
RESTORE terminates.
Recovery.
If the invalid format is the result of one of the first two causes, the files cannot be restored.
If you suspect the problem is a result of the third cause, contact your service provider and provide
all relevant information:
•
The information in this message
•
Description of the problem and accompanying symptoms
•
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a
processor dump, if applicable
If your local operation procedures require contacting the GCSC, supply your system number and
the numbers and versions of all related products as well.
7503
Bad tape format (Bad section length in DP2 tape file label).
Cause.
An attempt was made to restore a tape, but a BACKUP tape in the proper format could not
be found. There are three possible reasons:
•
BACKUP was stopped in the middle of a backup operation, resulting in an incomplete BACKUP
tape. The "Bad Tape Format" was detected when unwanted or meaningless information was
encountered at the interruption point on the tape.
•
The BACKUP tape was corrupted in some way.
•
Either BACKUP produced an invalid tape or RESTORE is not checking correctly due to a
software error.
Effect.
RESTORE terminates.
Recovery.
If the invalid format is the result of one of the first two causes, the files cannot be restored.
If you suspect the problem is a result of the third cause, contact your service provider and provide
all relevant information:
•
The information in this message
•
Description of the problem and accompanying symptoms
•
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a
processor dump, if applicable
If your local operation procedures require contacting the GCSC, supply your system number and
the numbers and versions of all related products as well.
7502 209
Содержание BACKCOPY
Страница 113: ...Format of the Permanent Work File 1 13 ...
Страница 114: ...1 14 Disk Space Analysis Program DSAP ...