Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Messages from the ftexec command

&pagelevel(4)&pagelevel

Several openFT components in the local and remote systems participate in the execution of an ftexec command. Any of these instances can be responsible for the messages issued during execution:

In the local system, these are messages issued locally by the specified ftexec command whose execution is very similar to that of the ncopy command. Consequently, all the ncopy command messages may occur, the only difference being that they start with ftexec.

In the remote system, both the remote command itself and the ftexec server which monitors the execution of the remote command may handle requests. However, messages from the ftexec server are mapped to ncopy command messages wherever possible, i.e.:

  • If the end status for ftexec is not 255, then all stderr output originates from the command executed in the remote system (depending on the remote command involved). An end status other than 255 is also the return code of the remote command (at least its last byte).

    Tip: Avoid return code 255 in the remote command since it is possible that remote command execution may supply an error code 255 which is also passed on. To find out whether a local or remote error has occurred, consult your log files.
  • Messages from the other components involved can only have an end status of 255.

  • Messages from the ftexec command responsible for the transfer of data can have another additional meaning:

    • Request request ID: Remote system: Error in pre-/postprocessing

    • Request request ID: Remote system: Exitcode code from pre-/postprocessing

      Meaning:

      The local preprocessing command could not be executed successfully. The exit code here is the exit code of the ftexec server, i.e. 255.

    • Request request ID: Remote system: Transfer admission invalid

      Other possible meaning:

      The transfer admission does not permit any command execution.

    • Request

      request ID: Remote system: Syntax error in resulting file name.

      Other possible meaning:

      The command string is too long for the remote partner.

    • Request request ID: Remote system: File/directory 'file' not found

      Other possible meaning:

      The file name prefix in the remote admission profile does not start with "|ftexecsv ".

    • ftexec: Invalid parameter 'c'

      Meaning:

      Encryption of user data is not enabled.

  • Messages deriving from ftexec server instance messages (these start with "ftexecsv:"):

    • Request request ID: Remote system: File/directory does not exist

      Meaning:

      The command specified in ftexec does not exist in the remote system - at least not under the explicitly specified or implicitly assumed path. If the partner is a Unix system, this message can also mean that the file exists but cannot be executed as a command or that a resource bottleneck occurred when an attempt was made to start the command.

    • Request request ID: Remote system: Access to ... denied

      Meaning:

      The command specified in ftexec is not an executable command or includes invalid characters (see ftcrep command, -fnp option).

    • Request request ID: Remote system: Resource bottleneck

      Meaning:

      A resource bottleneck occurred when an attempt was made to start the command specified in ftexec.

    • Request request ID: Remote system: File structure error

      Meaning:

    • An error occurred while reading the stdout or stderr data generated when the remote command was executed.

    • A record created by the command specified in ftexec cannot be entered in the ftexec server buffer. An attempt was probably made to read pure binary output as text.

    • The ftexec server received an error flag while forwarding the data from the remote command to the openFT server.

    • Request request ID: Internal error. Error code err_code

      Meaning:

      An internal error occurred in the remote ftexec server.

  • Messages from the ftexec command itself (these start with "ftexec:"):

    • Request request ID: File structure error

      Meaning:

      The data received does not correspond to the ftexec format. It may originate from a remote file or from normal preprocessing. Check whether the appropriate transfer admission has been selected.

    • Internal error. Error code err_code

      Meaning:

      An internal error err_code occurred during the processing of the ftexec command.