| Completion, or Termination, Codes |
| Successfull Completion: GETs and PUTs terminate with message number 226. Further more, you should investigate if the server, on PUTs, drops more than one byte. |
| The following example shows a successfull upload (i.e., PUT). Notice that the server states that it dropped one byte. This is most likely the ASCII end of file marker byte. Any higher number must be investigated even if the upload terminates with 226!!!!! 226-Records rcvd : 000000237 Bytes dropped: 000000001 226 Closing data connection. |
| The following example shows a successfull Download (i.e., GET). Notice that the server states that it bytes dropped field is not applicable (n/a). dropped one byte. This is most likely the ASCII end of file marker byte. 226-Records rcvd : 000000237 Bytes dropped: n/a 226 Closing data connection. |
| Failed Completion: GETs and PUTs normally terminate with message number 552. |
| ftp> put test.txt test.test.rrds 200 Command okay. 150 File status okay, about to open data connection. 552-Records rcvd : 000000000 552 Requested action aborted. Error code = 6C |
| Failed Completion: Temporary Error Codes. The following error codes are temporary. The user should retry the operation a while later. |
| 2T 8T |
| Virtual Storage Shortage. User should retry. Assign Macro failed. User should retry. |
| Failed Completion: Permanent Error Codes. The following error codes are permanent. The user should retry the operation after fixing the cause of the problem, if possible. The following list of error codes are explicitly set by the server itself. The server also reports error codes as returned by the appropriate Access Method. For those codes, please consult the appropriate Access Method return codes manual. Some more serious, except 10, errors: |
| View File Problem. Probably the FTPC file is not there! Definition Problem. Probably TYPE = RCV is not coded. Some inconsistency is found in the VIEW. SITE commands might screw (by overriding) file views. Fix the view or turn off the SITE commands, if need be. Sanity check error. IBCVTAM discovered that SIO did not consume data!!!! Data LOSS. End of session but we still have more than one byte to write. Possible causes: connection interruptions. You�ve issued a DIR command, but the Access method (in the File view is invalid. See error code VP. SITE TYPE might cause this error. ASCII record is larger than the TGT record or block size. Increase record and/or block size and try again. |
| FP DF VP CE DL AM 2L |
| 10 11 12 13 14 8A 8B 8C 8D 8F 4P 5P 1X OP WT ZV |
| End of Source File encountered. I/O (SYNAD) exit driven. Internal Abend SIO Abended while doing file I/O. Irrecoverable I/O and EROPT = Q. Invalid Access Method. GetVCE failed. Invalid Extent info. LABEL macro failed. SIO Abend while doing Init Processing. VSAM Acess Method Not Supported. GENCB Failed. End Of Extent while closing file (out of space). Set by OC. Open Failure. Wrong Tape Mounted. Zero-Value found where non-zero value is expected. |