Skip to main content
Version: OpCon 21.0 (On-Prem)

File Transfer Jobs

The SMA File Transfer (SMAFT) system reliably transfers files across multiple platforms via an OpCon job. The receiving and sending SMAFT Components (SMAFTAgent and SMAFTServer) are installed with FT-enabled LSAMs: Microsoft, IBM i, MCP, OS 2200 and BIS, UNIX, and z/OS. The source and destination machines must have these components for a file transfer.

note

SMAFT for Windows needs a .NET version installed to work.

File Transfer Job

File Transfer Job

After receiving instructions from the resident LSAM, the SMAFT Component on the machine determines the best method for transporting the file with the SMAFT Component on the other machine. After negotiating the file transfer settings between the SMAFT Components, the file is transferred.

note

No matter which machine the job starts on, the file transfer port for that machine must be open on the firewall. For more information, refer to File Transfer Settings.

Configuration​

Before attempting a transfer, configure the machine definitions in OpCon plus the source and destination machines' LSAMs.

In the source and destination machines' LSAM configuration files, define the parameters for file transfers. Normally, these settings are commingled with the LSAM's Job Output Retrieval System (JORS) parameters.

In the job definition, adjust the Settings for the destination machine to correspond with the source machine's LSAM file transfer settings (or vice versa). Under the category File Transfer Settings, define the "File Transfer" type and the "File Transfer Port Number". Once configuration is complete (and verified), a File Transfer Job can be defined. For additional information on File Transfer, refer to File Transfer Job Details.

Logging​

Each LSAM logs file transfer information differently.

  • For the IBM i LSAM, the SMAFT Agent writes all processing information to the SMAFT Agent logging system, and the SMAFT Server writes all processing information to the SMAFT Server logging system. Logging behavior is defined in the SMA File Transfer Menu. For information on these settings, refer to SMA File Transfer Menu in the IBM i LSAM online help.
  • For the MCP LSAM, the SMAFTAgent logs general information messages to the PRT_FTAGENT print file when SW2 is set for the LSAM. For information on setting debug switches, refer to Problem Resolution and Debugging in the MCP LSAM online help.
  • For the Microsoft LSAM, the SMAFTAgent writes all processing information to the SMAFTAgent.log file in the <Output Directory>\MSLSAM\Log\ directory. Logging behavior is defined in the LSAM's Debug Settings. For information on these settings, refer to Debug Options in the Microsoft LSAM online help.
  • For the UNIX LSAM, the SMAFTAgent logs general information messages to the UNIX LSAM logfile and logs error messages to the UNIX LSAM errfile. The UNIX LSAM itself controls the maintenance of logs. For information on these logs, refer to JORS and SMAFT Parameters in the UNIX LSAM online help.
  • For the OS 2200 LSAM, the SMAFT Agent writes all processing information to the SMAFT log file, and the SMAFT Server (JORS) writes all processing information to the SMAJOR log file. Logging behavior is defined in the under the Debug Mode in the Advanced Options of the LSAM's configuration. For information on these settings, refer to Configuration Settings -- Advanced Options in the OS 2200 LSAM online help.
  • For the z/OS LSAM, file transfer is run as a job; therefore, the log for the job contains the logging information.