An error may have occurred during a request sent to the Transfer CFT. The &str message
label specifies the possible type
of error:
- Unknown protocol
request:
Internal error of the Transfer CFT, which receives an unexpected
protocol event
The operator command received is unknown
The transfer is not possible (status other than "D"
(Available)
- Transfer for
myself rejected:
The target of the transfer is the local site (CFTPARM PART field) The Transfer CFT
therefore refuses
to activate a transfer to itself
- Logger currently
unreachable:
A SWITCH command, switching
log files, was attempted while the LOG task (CFT log) was not (or no longer)
active
The catalog was 100% full and so the last SEND (or RECV) command
could not be processed; if it was submitted via the Transfer CFT communication
file, it is stored in the file and the associated communication process
stops (for more information, refer to the CFTC01W message)
There is a syntax error in the request; inform Product Support
The request is invalid
An internal Transfer CFT error was detected; inform Product Support
An internal Transfer CFT error was detected; inform Product Support
- Transfer
already in progress:
An attempt was made to restart a transfer in progress; the
transfer was not restarted
- File already
transferred:
An attempt was made to restart a terminated transfer; the
transfer was not restarted
A read error was detected on the authorizations file (&file);
inform Product Support
- Access Exit Task
unreachable: &diagp:
The directory exit task cannot be accessed (DIAGP specifies
the cause); inform Product Support
- Request Ignored
: time-out:
The request was not processed by the Transfer CFT (end time limit
exceeded)
- Unable to attach
Client mailbox:
Attachment to the client application was rejected
- Unable to send
data to Client mailbox:
Data cannot be sent to the client application
|