Description of the output

Output is possible in tabular form and in CSV format.

It should be noted that for activities which have not yet been started, the output from the ftshwact command is usually incomplete since the references present in the request have not yet been resolved and it is not therefore possible to enter all the desired output values. In particular, file and directory names in reference specifications are not fixed until runtime since they may be dependent on the operating system.

Output in table format

The processing level of the activities is displayed in four columns:

Id

Unique identification of the activity within the request. This can be converted into an Xpath which mirrors the position of the activity in the tree which is statically predefined by the XML script.

Dynamic information is simply added for the foreach nodes (sequence number in the foreach loop).

For more detailed information, see the description of the XML statements for the openFT-Script interface.

Sta

Status of the statement. The following status identifiers are possible:

W (waiting)	The activity has not yet been started.
R (running)	The activity has been started but has not yet been terminated.
T (terminated)	The activity has been terminated without errors.
F (failure)	The activity has been terminated with an error.
K (killed)	The activity was cancelled by means of a faulthandler or an ftcans command.
D (dead)	The activity no longer starts due to a previous error.

In the case of the ftscript activity (first activity in an openFT-Script request), a distinction is made between the following statuses:

I (interrupted)	The request was interrupted, e.g. due to a system crash.
C (cancelled)	The request was cancelled with ftcans.
X (cancelling)	The request is currently being cancelled due to an ftcans command.
F (failure)	Is only displayed for the ftscript activity if the error was not handled by a faulthandler.

In the case of activities with the status F and faulthandler activities, the cause of the error is output in clear text in an additional line.

Activity

Activity name. The names are based on the openFT-Script language but may be truncated in some cases, e.g. faulthdlr instead of faulthandler.

foreach is designated in accordance with the value of the execute attribute as foreach_P (parallel) or foreach_S (sequential).

TransferFile is designated as sendFile or rcvFile (=receive File) depending on the direction of transfer.

ActivityObject

The content of this column depends on the activity in question, see the table below.

Activity	ActivityObject	Meaning
ftscript	<scriptPath>	Complete path name of the original file with the XML statements.
empty	-
foreach_P	<contextObject>	context object which assumes the value of the current list element
foreach_S	as foreach_P
parallel	-
sequence	-
sendFile	Specifies the remote file in the following form:
	<partner>!<file name>	Partner with file name if both are known.
	*unknown!<file name>	if the partner is not yet known.
	*unknown!*unknown	if both are not yet known.
	<partner>!*ref(<contextId>)	if contextId = foreach contextObject and the resolution is not yet known because it has not yet been passed through.
	<file name>	in the case of requests which have already been started, this is the name specified in the FT request. In the case of requests which have not yet been started, this name is derived from the operating system-specific name specified in the XML file (e.g. unixName) and extended by the directory specifications.
rcvFile	as sendFile
deleteFile	specifies the remote file as in sendFile (with partner), if the file is local, without partner:
	<file name>	like sendFile, is determined from the FT request in the case of requests that have already been started, and from the XML file in the case of requests that have not yet started. A local file name would be output as an absolute file name in the case of a started request and as a relative path name in the case of an as yet unstarted request.
	*unknown!<file name>	if it is not known if the file is local when a file object is referenced.
createDir deleteDir	<partner>!<directory-name>	Partner with directory name if both are known.
	*unknown!<directory-name>	if the partner is not yet known.
	*unknown!*unknown	if both are not yet known.
	<partner>!*ref(<contextID>)	if contexId = foreach contextObject and the resolution is not yet known because it has not yet been passed through.
	<directory-name>	if the directory is local. In this case, as for sendFile, the name for already started requests is determined from the FT request and for requests which have not yet been started, from the specifications in the XML file. A local file name would be output as an absolute file name in the case of a started request and as a relative path name in the case of an as yet unstarted request.
	as createDir.	as createDir.
listDir	as createDir.	as createDir.
execScript	32 characters	Contains the first 32 characters of the command that is to be executed. For security reasons, the user should make sure that the first 32 characters do not contain any confidential parameters.
fault	<faultcode>	Error code specified by the user.
faulthdl	<triggering activity id>: <special faultcode>;<general faultcode>