Operations File Transfer Messages
In addition to displaying the completion percentage and the interim transfer operations (e.g., compressing, decompressing, etc.), the EM displays specific file transfer codes from the LSAM's participating in the file transfer job. The Origination column identifies the error location: the FTAgent (Destination) and/or the FTServer (Source).
MCP SMA File Transfer Messages
The following error messages may be encountered in the *SMA/FTAGENT.
| Condition | Result |
|---|---|
| *SMA/CONFIG/FILE\</unique identifier> cannot be located | Log error: Configuration file is missingFTAGENT aborts. |
| CFG_SMAFT_IN_USE = N | Log error: SMAFT is not enabled for this LSAMFTAGENT aborts. |
| CFG_SMAFT_IN_USE = O | Log error: SMAFT is permitted for outbound file transfers onlyFTAGENT aborts. |
| CFG_SMAFT_IN_USE is not any of the following: N, O, I, B | Log error: Invalid value for SMAFT_IN_USE flag. Flag is: xFTAGENT aborts. |
| Disposition is "Do Not Overwrite" and Destination file exists. | Log error: File xxxxxxx exists and overwrite is not permittedFTAGENT aborts. |
| CFG_FTAGENT_PORT is outside the range 1024 - 65535 | Log error: Invalid value for FTAGENT port: nnnnnFTAGENT aborts. |
| Unable to establish a dialog with the File Transfer Server | Log error: FT Server OPEN error: \<reason> for IP: \<server IP> port: \<server port> |
| Warning encountered while attempting to establish a dialog with the File Transfer Server | Log error: FT Server OPEN warning: \<reason> for IP: \<server IP> port: \<server port> |
| Compression is required | Log error: Compression not supportedFTAGENT aborts |
| Encryption is required | Log error: Encryption not supportedFTAGENT aborts |
| Additional error conditions | Error messages that are received by *SMA/FTAGENT from the File Transfer server will be logged. Refer to the platform-specific Administration manual for a discussion of the messages generated by the SMA File Transfer server. |
| CRC received on incoming message does not match calculated CRC | Log error: ** Bad CRC ***FTAGENT aborts. |
| Message packets arrived out of sequence | Log error: Packet number error. Previous: \<previous packet number> Received: \<received packet number>FTAGENT aborts. |
| The data type specified for the destination file does not match the data type for the existing file. | Log error: Data type mismatch for appended file. Spec: \<specified data type> File: \<File data type>FTAGENT aborts. |
| A message type other than 020, 022, 023, 024, 028, or 029 was received by the *SMA/FTAGENT program from the File Transfer server | Log error: File: Undefined msg type \<msg header>FTAGENT aborts. |
| The *SMA/FTAGENT program attempted to place a job status message in the *SMA/OUTBOUND/FILE, but was unable to do so. | Log error: Can't write to SAM. \<first 132 characters of the status message>FTAGENT aborts. |
| An unsupported Common Character Set designation was received. | Log error: Invalid CommonCharSet \<CommonCharSet>FTAGENT aborts. |
OS 2200 File Transfer Server Messages
The OS 2200 File Transfer Server messages are sent to File Transfer Agents, which may be displayed in OpCon Schedule Operations.
| Message | Description |
|---|---|
| SECURITY VIOLATION | An attempt has been made to violate the security settings of the File Transfer configuration. Most often this results from disallowing File Transfers, and an attempt to perform a transfer was initiated. |
| File Name Missing | The name of the source file was not provided by the FTAgent. This situation should be reported to SMA Technologies Support. |
| Unsupported SOURCE Data Type | The selected Data Type for the source file is not supported. The Data Type must be ASCII or Default Text. |
| Unsupported file type: file name | The source file type is not supported. Refer to the OS 2200 Source Files section to review the unsupported types. |
| File does NOT exist: file name | The requested source file does not exist on the source system. |
| file name returned MFD error error text | The inquiry to the Master File Directory (MFD) for the source file details resulted in the error text error. |
| File Unloaded | The requested source file is in an unloaded status. Unloaded files are not supported. |
| File to be Catalogued | The requested source file is in a "to be catalogued" status. "To be" files are not supported. |
| File is a Tape File | The requested source file is a tape file. Tape files are not supported. |
| File is to be WRITE ONLY | The requested source file is in a "to be write only" status. "To be" files are not supported. |
| File is to be Dropped | The requested source file is in a "to be dropped" status. "To be" files are not supported. |
| File is WRITE ONLY | The requested source file is "write only" and cannot be read for the transfer. |
| Encryption not supported | The FTAgent has requested an encrypted file transfer; file encryption is not supported. |
| Compression not supported | The FTAgent has requested a compressed file transfer; file compression is not supported. |
| ASCII Transfer ONLY supported | The FTAgent has requested a transfer character set other than ASCII. |
| FILE ASSIGNMENT FAILED | The attempt to assign the source file failed. The SMAJORS Log file will contain specific error information. |
| file-name requires READ key | The source file requires a READ key to be accessed. |
| file-name File not found (SDFI CST: xx ) | An attempt to open the file for reading failed due to a file assignment error; the xx CST number provides the error identifier. The SMAJORS Log file will contain specific error information. |
| File Open Error xx: error message text | An attempt to open the file for reading failed. The xx contains the error identifier; the error message text contains a brief description of the error. The SMAJORS Log file will contain additional error information. |
| FILE READ ERROR (CST: xx, CSST: xx ) error message text | An error occurred while reading the source file. The CST and CSST contain error identifiers; error message text contains a brief description of the error. The SMAJORS Log file will contain additional error information. |
| 1 - POINTER AT END OF STRING 2 - START DELIMITER NOT FOUND 3 - RETURNED STRING TRUNCATED 4 - END DELIMITER NOT FOUND Invalid Request: Not \<DATA> Invalid Request: request data | These messages are the result of internal processing discrepancies between the FTServer and FTAgent. These should be reported to SMA Technologies Support. |
OS 2200 File Transfer Job Messages
| Message | Description |
|---|---|
| 1 (01) First card image not Tip File parameters | The SMAJOR/ECL does not contain the TIPFILE statement after the \@XQT SMAFT statement. Indicates a corrupt SMAFTA/ECL element. |
| 2 (02) Missing OpCon Job-ID parameter | The OpCon Job Name parameter is missing. Indicates a corrupt SMAFT/ECL element. |
| 3 (03) Missing Source Machine parameter | The identification of the machine to transfer the file from is missing. Indicates a corrupt SMAFT/ECL element. |
| 4 (04) Missing Source socket parameter | The communications socket parameter for the source machine is missing. Indicates a corrupt SMAFT/ECL element. |
| 5 (05) Missing Source file name parameter | The name of the source file is missing. Indicates a corrupt SMAFT/ECL element. |
| 6 (06) Missing Destination file name parameter | - The name of the destination file is missing. - Indicates a corrupt SMAFT/ECL element. |
| 7 (07) Invalid transfer mode (must be ASCII) | - The file character set for the job is not supported. - The character set must be either "ASCII" or "Default Text". |
| 8 (10) Invalid Compression mode (must be NONE) | Compression Required has been specified for the file transfer job. Compression is not supported. |
| 9 (11) Invalid Encryption mode (must be NONE) | Encryption Required has been specified for the file transfer job. Encryption is not supported. |
| 10 (12) Invalid Overwrite parameter (cannot be APPEND) | Destination File Handling has been identified as either "Append" or "Backup and Append". The OS 2200 FTAgent does not support file appends. |
| 13 (15) Common Bank slot not available | The number of File Transfer jobs is greater than twelve (12), OR the Common Bank has become corrupted (possibly from many FTAgent job aborts.) To correct, stop and restart XFRTCP and SMAJOR runs. |
| 14 (16) FPRC Request (020) message received in error | A communications error between an FTServer and FTAgent has occurred. Report this condition to SMA Technologies Support. |
| 15 (17) SEND Request (022) message received in error | A communications error between an FTServer and FTAgent has occurred. Report this condition to SMA Technologies Support. |
| 16 (20) TIP read error: XFR READ FAILURE | An error occurred while attempting to read the XFER Status record from the TIP file. Most likely the TIP file is corrupted; use the XFRINI/ECL and LPARMRES/ECL procedures to re-initialize the file. This situation should be reported to SMA Technologies Support. |
| 17 (21) TIP read error: INIT and Parameters failure | An error occurred while attempting to initialize the TIP interface and red the LSAM Parameters record from the TIP file. Most likely the TIP file is corrupted; use the XFRINI/ECL and LPARMRES/ECL procedures to re-initialize the file. This situation should be reported to SMA Technologies Support. |
| 18 (22) COMM Failure: OPEN connection failed | The attempt to open a connection to the FTServer failed. The job's log file contains detailed error information. |
| 19 (23) Invalid CAPABILITIES message | The FTAgent has received an invalid message from the FTServer. This situation should be reported to SMA Technologies Support. |
| 20 (24) Required CAPABILITY not present: ASCII | The FTServer does not have the required capability of transferring the file in ASCII format. This situation should be reported to SMA Technologies Support. |
| 21 (25) Destination File Name invalid | The name provided for the destination file does not meet the FTAgent requirements. Review the OS 2200 Destination Files section for acceptable file names. |
| 22 (26) FACILITIES STATUS error (\@FAC) | A Facilities Error occurred while attempting to manage the destination file. The job's log file will contain detailed error information. |
| 23 (27) Open OUTPUT file failed | An error occurred when the FTAgent attempted to open the destination file. The job's log file will contain detailed error information. |
| 24 (30) Received error from server | The FTAgent received an error message from the FTServer; the received message is included. Review the FTServer documentation for additional information pertaining to the message. |
| 25 (31) File WRITE error (SDFIO) | The FTAgent encountered an error when attempting to write data to the destination file. The job's log will contain detailed error information. |
| 26 (32) Job Record not found in TIP FILE | The necessary job data could not be found in the TIP file. This may be the result of a corrupted file, or a combination of multiple occurrences of the job processing simultaneously. This situation should be reported to SMA Technologies Support. |
| 27 (33) COMM Failure: Connection Rejected | The FTServer rejected the FTAgent's attempt to open a communications session. |
| 28 (34) COMM Failure: Connection Aborted | The communications connection between the FTServer and FTAgent aborted. |
| 29 (35) COMM Failure: Connection Closed before EOF | The communications connection between the FTServer and FTAgent was closed before the end-of-file was received. This situation should be reported to SMA Technologies Support. |
| 30 (36) FIXED length records w/zero RecordLength | The FTServer has identified the source file as containing FIXED length records but has reported a zero record length. This situation should be reported to SMA Technologies Support. |
| 31 (37) Required RECORD parameters not present | The FTServer has failed to provide file parameters required to create the output file. This situation should be reported to SMA Technologies Support. |
| 32 (40) Unsupported File Format (not FIXED or VARIABLE) | The format of the source file is not supported bu the OS 2200 FTAgent. |
| 33 (41) Preferred Compression FAILED | The File Transfer job is defined with "Compression Preferred" and "Failed if Preferred not met". The file has been transferred successfully. |
| 34 (42) Preferred Encryption FAILED | The File Transfer job is defined with "Encryption Preferred" and "Failed if Preferred not met". The file has been transferred successfully. |
| 35 (43) Invalid Destination File key(s) | The Read and/or Write keys provided for the destination file are invalid. |
| 36 (44) File Transfer Server not responding | The FTServer is no longer communication with the FTAgent. |
| 37 (45) Invalid Packet Number received on Resend | An out-of-sequence data message has been received by the FTAgent. This situation should be reported to SMA Technologies Support. |
UNIX File Transfer Error Codes
File transfer errors received by STDOUT/STDERR may be viewed in the EM's Job Output Retrieval System (JORS).
The messages in this section are output by the UNIX Agent and Server; messages output by a non-UNIX Agent or Server will be different, and the user is referred to the documentation for the appropriate LSAM. When the destination machine is UNIX and an error originates in the Server, the Agent will prepend "FTServer:" to the message to indicate that it originated with the Server.
Example
FTServer: Error reading Temp File [/usr/local/lsam/tmp/FT_AHhs5/daily.txt.asc.10203]
STDOUT
| Message | Origination | Explanation |
|---|---|---|
| Original Destination File [desf] backed up to [backup] | FTAgent | Per the job's "Overwrite" option. the FTAgent backed up the Destination File prior to starting the file transfer. |
| Original Destination File [file] did not exist to backup | FTAgent | At the job's startup, no Destination File exists to backup. |
| Could not change default access permissions for Destination File [desf] | FTAgent | Following the transfer of a new Destination File, the new file's access privileges could not be changed from the system-dependent default to: - full access by owner - read access by group - no access by others NOTE: If the Destination file existed before the file transfer, the file transfer does not modify its access permissions. |
| [src_machine]src_file --> [dest_mach]dest_file | FTAgent | - Displays the results of the file transfer. - The Destination File was created or overwritten. - Shown if the job's "Overwrite" option specified appending, but the Destination File did not exist prior to the file transfer. |
| [src_machine]src_file appended --> [dest_machine]dest_file | FTAgent | - Displays the results of the file transfer. - The Source File was appended to the Destination File. |
| File transfer successfully completed | FTAgent | The job ran to completion. |
| File transfer did not complete! | FTAgent | The job did not run to completion. The file may or may not have been transferred. Refer to the job's STDERR output for details of what went wrong. |
STDERR
Written to a job's STDERR file when the job requirements could not be met. The following messages are Pre-Processing Errors.
| Message | Origination | Explanation |
|---|---|---|
| User does not have required access to Source File [file] | FTServer | The file transfer was aborted because the user did no have READ access to the Source File. |
| User does not have required access to Destination File [file] | FTAgent | The file transfer was aborted because the user did not have WRITE access to the Destination File OR CREATE access to the Destination directory. |
| Invalid path component in Destination File [file] | FTAgent | The file transfer was aborted because the user specified a non-existent directory within the path portion of the Destination File, i.e., that portion of the Destination File prior to the final '/' in the filename. |
| Destination File [file] already exists and overwrite not allowed. | FTAgent | The file transfer was aborted because the Destination File already existed, and the user specified "Do Not Overwrite" for the job's "Overwrite" option. |
| Could not back-up Destination File [file] (indicator) | FTAgent | - The file transfer was aborted becuase the Destination File could not be backed up as the user specified for the job's "Overwrite" option. - The indicator field provides the specific reason. |
| Compression REQUIRED but not supported by both machines | FTAgent | The file transfer was aborted because compatible forms of file compression were not available on both the Source and Destination machine. |
| Compresssion is FAIL-PREFERRED but not supported by both machines. Continuing without compression - job status will be FAILED... | FTAgent | - The file transfer was initiated without file compression. - If it was successful, OpCon reported the job as Failed because the user checked the "Send fail..." box under Failure Criteria in the Job Details screen. |
| Compression is not supported by both machines. Continuing without compression... | FTAgent | The file transfer was initiated without file compression. |
| Encryption REQUIRED but not supported by both machines | FTAgent | The file transfer was aborted because compatible forms of file encryption were not available on both the Source and Destination machines. |
| Encryption is FAIL-PREFERRED but not supported by both machines. Continuing without encryption - job stat us will be FAILED... | FTAgent | - The file transfer was initiated without file encryption. - If it was successful, OpCon reported the job as Failed because the user checked the "Send fail..." box under Failure Criteria in the Job Details screen. |
| Encryption is not supported by both machines. Continuing without encryption... | FTAgent | The file transfer was initiated without file encryption. |
| Unsupported Data Type [type] | FTAgent FTServer | The file transfer was aborted because the indicated data type is not supported. |
| Cannot Process <CommonCharSet> of [charset] | FTAgent | FTAgent is unable to translate the intermediate character set chosen but the FTServer to affect the transfer when the Source and Destination's data types differ. |
Processing Errors
note
Occurrence of an error does not necessarily (but usually does) mean that a job is aborted. If the job does complete successfully, it may indicate some marginal operating conditions in need of attention.
| Message | Origination | Explanation |
|---|---|---|
| Source file [file] does not exist | FTServer | The Source File does not exist. |
| Source file [file] is empty | FTServer | The Source Files contains no data. (i.e., its length is zero.) |
| Could not open Temp File [file] (indicators) Could not open FT Directory lock [file] (indicators) | FTServer FTAgent | - The indicated file could not be opened for processing. - The indicator field provides the specific reason. |
| Could not open OLD Destination File [file] (indicator) | FTAgent | - The indicated file could not be opened for processing. - The indicator field provides the specific reason. |
| Could not create FT Directory [directory] (indicator) Could not create Temp Directory [directory] (indicator) Could not create /tmp [directory] (indicator) | FTserver FTAgent | - The indicated directory could not be created for processing. - The indicator files provides the specific reason. |
| Could not fseek Temp File [file] (indicator) | FTServer FTAgent | the indicated object could not be positioned for processing. The indicator field provides the specific reason. |
| Could not rename Temp. FT Directory [file] to [to] (indicator) | FTServer FTAgent | - The indicated object could not be positioned for processing. - The indicator field provides the specific reason. |
| Could not rename Source File [from] to [to] (indicator) | FTServer | - The indicated file could not be renamed for processing. - The indicator field provides the specific reason. |
| Could not rename [from] to [to] (indicator) Could not rename unTAR'd [un-TAR] to Temp [temp] (indicator) | FTAgent | - The indicated file could not be renames for processing. - The indicator field provides the specific reason. |
| Could not get size of Temp File [file] (indicator) | FTServer | The size of the indicated file could not be determined. The indicator field provides the specific reason. |
| Could not get size of Partial File [file] (indicator) Could not get size of APPEND-TO Destination File [file | (indicator) | FTAgent |
| Could not get file info for Source File [file] (indicator) | FTServer | The statistics (e.g., size, date, etc.) for the Source File could not be obtained. The indicator field provides the specific reason. |
| Tag [tag] is not specified | FTServer FTAgent | The indicated XML tag was missing. |
| End tag [tag] is not specified | FTServer FTAgent | The associated ending tag for the indicated XML tag was missing. |
| Value for Tag [tag] is not specified | FTServer FTAgent | No value was supplied for the indicated XML tag. |
| Could not fork() for [operation] (indicator) | FTServer FTAgent | - The indicated operation could not be performed due to inability to execute a fork() call. - The indicator field provides the specific reason. |
| Could not wait() for [operation] (indicator) | FTServer FTAgent | - The indicated operation could not be performed due to inability to execute a wait() call. - The indicator field provides the specific reason. |
| Processing error in [operation] (inidicator) | FTServer FTAgent | The indicated operation could not be performed due to the reason pointed to by the indicator field. |
| Max attempts at sending message exceeded | FTServer FTAgent | The maximum number of attempts to sned a message was reached. |
| Max Wait Time to receive message has elapsed | FTServer FTAgent | The maximum time allowed for reception of a message was reached. |
| Receive was not successful (indicator) | FTServer FTAgent | Reception of a message failed. The indicator field provides the specific reason. |
| Send unsuccessful (indicatior) | FTServer FTAgent | A message fould not be sent. The indicator field provides the specific reason. |
| Could not set bugger size Could not set buffer size for sending | FTServer FTAgent | The communications channel could not be initialized. |
| Send failed for ACK | FTServer FTAgent | An attempt to ACK (i.e., acknowledge) a message failed. |
| Mismatch bewteen received & expected CRC | FTServer FTAgent | The received messafe was incomprehensible. |
| Reveived invalid message | FTServer FTAgent | The received message was not expected. |
| RCV Queue full | FTServer FTAgent | The queue is full because a processing error occurred. |
| Error in FT Directory format | FTServer FTAgent | The file which maps Source and Destination files to temporary files for processing is corrupted. |
| Could not lock FT Directory [directory] (indicator) | FTServer FTAgent | - The file which maps Source and Destination files to temporary files for processing could not be locked for exclusive use. - The indicator field provides the specific reason. |
| Incorrect number of parameters | FTAgent | FTAgent received the wrong number of startup parameters from the LSAM. |
| Unknown host name [computer] | FTAgent | FTAgent was unable to locate the indicated computer on the network while trying to connect to the FTServer. |
| Error connecting to [computer] (indicator) | FTAgent | FTAgent was unable to connect to the FTServer located on the indicated computer. The indicator field provides the specific reason. |
| Could not get host name (indicator) | FTAgent | FTAgent was unable to retrieve its own host name to send to FTServer. The indicator field provides the specific reason. |
| FTServer process prematurely terminated | FTAgent | FTAgent has lost communication with FTServer. |
| Could not set GID to [groupID] to check file access Could not set UID to [userID] to check file access | FTServer | FTServer could not set GID/UID as indicated to determined if the user has access to the Source File. |
| Error reading Temp File [file] Error writing Temp File [file] | FTServer FTAgent | The temporary file could not be read or written. |
| Error writing file data, (indicator) | FTAgent | FTAgent could not save data as packets arrived from FTServer. The indicator field provides the specific reason. |
| Could not move Temp File [temp] to Destination File [dest] (indicator) | FTAgent | FTAgent could not make a temporary file into a permanent Destination File. The indicator field provides the specific reason. |
| Unable to get environment variable [SMA_JOBNAME] Unable to send message (indicator) | FTAgent | FTAgent could not send job status information to SAM. The indicator field provides the specific reason. |
| Could not process zero-length Source File [machine] (indicator) | FTAgent | FTAgent could not create a zero-length destination file to match the zero-length source file, or could not update the timestamp of the destination file when "append" was specified. |
| Invalid length of file for FIXED-length records | FTAgent | The length of the received file was as expected, when the user specified that the file be saved in a record-oriented format (by pre-pending a '=' to the destination file name). |
| Invalid RECORD-LENGTH indicator | FTAgent | the data format from the FTServer was not as expected, when the user specified that the file be saved in a record-oriented format (by pre-pending a '=' to the destination file name). |
| Missing/Invalid <RecordFormat> in XML-header | FTAgent | The data format from the FTServer was not expected, when the user specified that the file be saved in a record-oriented format (by pre-pending a '=' to the destination file name). |
| Invalid <RecordSep> [RS] in XML-header | FTAgent | The data format from the FTServer was not as expected, when the user specified that the file be saved in a record-oriented format (by pre-pending a '=' to the destination file name). RS indicates the erroneous data. |
| XFER RECORDS and bad/missing Index File [%s] | FTServer | The user specified that the file be sent in a record-oriented format (by pre-pending a '=' to the source file name), and the associated index file (which contains the record structure) could not be found or was corrupted. The most likely cause for a missing index file is either that the source file was not previously saved by the FTAgent as a record-oriented destination file, or that the index file was accidentally deleted. A native, stream format, file cannot be sent as a record-oriented file unless it is first transferred to itself/another file/another UNIX system as a record-oriented destination file. |
JORS / FTServer Errors
The UNIXLSAM.log file contains these errors.
| Message | Origination | Explanation |
|---|---|---|
| - Unable to open master socket (return : return errno: errno) - Select on master socket failed (errno : errno) - Accept on master socket failed (errno : errno) - Could not set buffer size | FTServer | - The communications channel could not be initialzed. - The return and errno field provide the specific reason. |
| fork() failed (errno : errno) | FTServer | - A child process to handle the JORS/FTServer durites fould not be spawned. - The errno field provides the specific reason. |
Windows File Transfer Error Codes
| MSLSAM Exit Condition Number | Origination | Description |
|---|---|---|
| 14001 | FTAgent FTServer | CRC Error |
| 14002 | FTAgent FTServer | Invalid file Transfer Mode (Value other than ASCII or Bianry) |
| 14003 | FTAgent FTServer | Unsupported file Compression mode |
| 14004 | FTAgent FTServer | Unsupported file encryption mode |
| 14005 | FTAgent FTServer | File exists (when File disposition is Do Not Overwrite) |
| 14006 | FTAgent FTServer | Fail Preferred Settings |
| 14007 | FTAgent FTServer | Socket Errors |
| 14008 | FTAgent FTServer | - Destination folder doesn't exist - No access to Destination folder - Destination file not specified - Invalid characters requested for the Destination file name |
| 14009 | FTAgent FTServer | Invalid Data Source type |
| 14010 | FTAgent FTServer | Not enough disk space on destination machine |
| 14011 | FTAgent FTServer | - Invalid source path - No access to source file - Source file is missing |
| 14012 | FTAgent FTServer | "Delete Source File" is required, and the user does not have permission to delete file. |
| 14013 | FTAgent FTServer | Compression is not supported for files 2GB and larger. |
| 14014 | FTAgent FTServer | During a Windows to Windows file transfer where the transfer Starts on the Destination machine, this error will occur if the user specified for the Source Machine doesn't have the required privileges on that machine. |
| 14099 | FTAgent FTServer | - View the SMAFT log on the machine where the transfer was started. - In the Enterprise Manager, (in Operations - List, Matrix or PERT views) right-click on the job and select Job Information > Configuration > Job Information. |