|
|
- Message
Invalid file name.
- Cause
The file name that you entered does not meet the MPE syntax
requirements for file names. Note that you cannot use HFS syntax (such
as /SYS/PUB/tapefile) for file names supplied to SLTCOPY.
- Action
Enter a different file name that meets MPE syntax requirements.
- Message
Undefined system file.
- Cause
File name entered is undefined to the system. Note that you cannot
use HFS syntax (such as /SYS/PUB/tapefile) for file names supplied to
SLTCOPY.
- Action
Enter a different file name that meets MPE syntax requirements.
- Message
Copy# on LDEV # is bad. The tape may be too short or an I/O error
occurred.
- Cause
Most often, this means that the tape onto you tried to make the copy
was shorter than the master tape.
- Action
Rerun SLTCOPY using a longer tape onto which to make the copy, or
recreate the master on a shorter tape.
- Message
Purge failed on old file
- Cause
Unable to purge the disk file with the same name as the file name
you entered. Occurs only with Option 1 (Copy tape to disk).
- Action
Purge the disk file and restart SLTCOPY.
- Message
Open failed for LDEV #
- Cause
SLTCOPY couldn't access the tape drive.
- Action
Check the tape drive cable connections, its configuration, and
whether or not it's available to this process.
- Message
Open failed for COPY1 Operation inconsistent with access type
(FSERR40)
- Cause
You attempted to copy to more than one remote tape,
when NOWAITIO was in effect.
- Action
If you need to copy to multiple remote tapes, make sure the
appropriate file equations are set (see Chapter 5
"Modifying Your System"), and reinvoke SLTCOPY using the WAITIO
option:
:SLTCOPY; INFO="WAITIO"
- Message
Failed to read tape! No records processed.
- Cause
Error occurred while reading the master tape. This message only
occurs after the tape drive has been open for reading.
- Action
Check the tape drive cable connections, its configuration, and
whether or not the availability of the tape drive changed after
the tape reply. When the error is found, restart SLTCOPY from the
beginning.
- Message
Failed to read tape! The expected total number of
the tape's EOF marks were encountered before the data.
- Cause
The format of the master tape is unknown to SLTCOPY. SLTCOPY
expects three end of file (EOF) marks to indicate the end of data.
Three EOF marks were encountered before any data was read.
- Action
SLTCOPY cannot copy this tape.
- Message
File already exists. Purge old?
- Cause
The disk file that you specified for the tape copy
already exists on the system.
- Action
Reply "yes" if it is all right
to overwrite the existing file.
- Message
That's not a multi-file type disk file.
- Cause
The disk file that you want SLTCOPY to copy to tape
is not the correct file type.
- Action
To get the correct disk file format for SLTCOPY, first use SLTCOPY
to copy a master tape to a disk file (using Option 1).
- Message
Can't handle file with # size records.
- Cause
The disk file that you want SLTCOPY to copy to tape has records that
are too large for SLTCOPY to copy.
- Action
To get the correct disk file format for SLTCOPY, first use SLTCOPY
to copy a master tape to a disk file (using Option 1).
- Message
Open failed on CATALOG.PUB.SYS.
- Cause
CATALOG.PUB.SYS is inaccessible to SLTCOPY.
- Action
Use the command "LISTFILE CATALOG.PUB.SYS,3" to verify
that the file exists and that it's accessible as shared; also check
its security (R,W,A,L,X:ANY). Also check that there is no file equation
for CATALOG.PUB.SYS which is redirecting access to an inappropriate
file. Then rerun SLTCOPY.
- Message
Error occurred while attempting to close the file.
If you choose the "Copy tape to disk" mode again,
you will get the opportunity to enter a different file name.
- Cause
After you entered the disk file name for Option 1 (Copy tape to
disk), the test closing of the file failed. The reason it failed is
shown in a File Information Display.
- Action
You will see the main menu after receiving this message. You can
then choose to exit the program (so you can adjust your capabilities),
or choose Option 1 again and specify a different file that will not
cause the same error.
|