Skip to main content

SMAFT File Transfer job

In briefA SMAFT File Transfer job moves a file between two legacy LSAM machines, Windows, UNIX or z/OS. You name a source machine and a destination machine. Start Transfer On then decides which of the two runs the job: the destination pulls (the default), or the source pushes. The job's machine follows from those fields, so Agent Assignment is read-only.

WhereIn Design › Workflows, open a workflow and open the job in the Job Editor (open its context menu on the canvas › Edit Job). On the Job Definition tab, choose SMAFT File Transfer as the job type and set the fields under Job Parameters. A read-only Runs on: line shows which machine will run it. Each machine's FT Role and file-transfer endpoint are set by an administrator on the agent, in Agents › Agents.

WhenUse a SMAFT File Transfer job when:

  • a file has to move from one LSAM machine to another;
  • the two machines are on different platforms, and line endings should be translated on the way;
  • one job should move several files that match a wildcard.

To move files between endpoints on an OpCon MFT agent, use OpCon MFT Transfer. The two job types are unrelated.

How

  1. Make sure both machines have an FT Role that lets them take part. The default is None.
  2. Choose the Source Machine and Source File, then the Destination Machine and Destination File.
  3. Attach a batch user for each end. A UNIX end must have one.
  4. Set Start Transfer On and the transfer options, then save the job.

For the full steps, see Transfer a file between two LSAM machines.

Notes
  • Text and ASCII translate line endings, so the byte count can change between platforms. Use Binary for an exact copy, and set it on both ends.
  • A push needs full file-transfer support on both machines.
  • With a z/OS machine at either end, Start Transfer On must be Destination, TLS Required is refused, and EBCDIC is valid on the z/OS end only. A z/OS end takes no batch user.
  • The job has no exit-criteria setting. The agent's verdict is the outcome.
Watch out
  • A machine with no FT Role set is missing from both machine lists, and a saved job that uses it fails at dispatch.
  • If the other machine is unavailable, the job holds, and force-start does not move it.
  • A wildcard transfer that involves a UNIX machine needs If File Exists set to Overwrite, and Compression and Encryption set to None.
  • Delete Source File other than No needs both machines to be Windows.