Redwood Documentation

Product Documentation

 

›Command Line Tools

RunMyJobsPlatform Agents

External Platforms

  • Connecting Redwood Server to External Platforms

Credentials

  • Storing Credentials
  • Credential Protocols

Platform Process Servers

  • On-site Platform Process Servers
  • Cloud Platform Agents
  • Using the Wizard to Create Process Servers
  • Configuring Platform Agents
  • Spool Host Agents
  • The Environment of Platform Agent OS Processes
  • Processing Platform Processes
  • Process Server Services
  • Configuring Agentless Process Servers
  • Automatically Updating Platform Agents
  • Enabling TLS
  • Creating Monitoring Checks
  • Configuring Load Balancing on Platform Agents
  • Platform Agent Registry Entries
  • Monitoring Servers with Platform Process Servers

UNIX Agents

  • UNIX Process Servers
  • UNIX Process Server Configuration Data
  • File Events on UNIX
  • Creating UNIX Process Servers (Advanced)
  • Choosing a User Switching Security Mode
  • Controlling Unix Platform Agents
  • Uninstalling Redwood Server Platform Agents from UNIX

Windows Agents

  • Creating a Microsoft Windows Process Server
  • File Events on Microsoft Windows Process Servers
  • Configuration of a Microsoft Windows Process Server
  • Managed Services
  • Configuring Platform Agents on Microsoft Windows
  • Automating Windows tasks that require a desktop window
  • Uninstalling Redwood Server from Microsoft Windows

Agent Definition Types

  • Using the BASH Definition Type
  • Using the KSH Definition Type
  • Using the CSH Definition Type
  • Using the Perl Definition Type
  • Using the Python Definition Type
  • Using the PowerShell Definition Type
  • Using the Visual Basic Script Definition Type
  • Using the CMD Definition Type
  • Using the R Process Definition Type
  • Using the DCL Definition Type
  • Using Platform Definition Types
  • Using the OS Native Definition Type
  • Microsoft Windows Definition Types
  • Using the SQLPLUS Definition Type
  • Using the FTP Definition Type
  • Using the Groovy Definition Type

Command Line Tools

  • Command Line System Tools
  • jtool
  • jcat
  • jdescription
  • jevent
  • jecho
  • jftp
  • JFTP Return Codes
  • jgetcredential
  • jgetfile
  • jgetpar
  • jjoin
  • jlink
  • jlog
  • jmail
  • jmessage
  • jmonitor
  • jputfile
  • jregister
  • jrfc
  • jscp
  • jtool screenshot
  • jscript
  • jsecret
  • jsleep
  • jsplit
  • api-tool.jar

OpenVMS Process Servers

  • Creating HP OpenVMS Process Servers
  • Installing the Platform Agent on HP OpenVMS
  • Configuring HP OpenVMS Process Servers
  • File Events on HP OpenVMS
  • HP OpenVMS Definition Types

AS/400 Connector

  • IBM AS/400 Connector Architecture
  • Setting up the IBM AS/400 Connector
  • Creating an IBM AS/400 Process Server
  • Files on AS/400 Raise Events
  • Using the AS/400 Definition Type
  • Redwood Server OS Support
  • IBM z/OS Definition Types
  • Using the JCL_FTP Definition Type
  • IBM z/OS System Tools

Reference

  • Balancing the Load
  • Credential Protocols
← jftpjgetcredential →

JFTP Return Codes

The JFTP tool tries to reflect as its return code to the OS the last reply code, divided by ten (10). The reason for this is that on some operating systems the return code is limited to a value between 0 and 255, so it cannot reflect all FTP return codes.

Return codes, also referred to as reply codes, give feedback on the status of the previously executed command. RFC's define the standards for protocols to allow tools to inter-operate, however, vendors are not forced to adhere to the RFC's standards and many don't adhere totally. The jftp tool will return standard FTP return codes when the FTP server does, so the Internet is a great resource to look-up the meaning of a specific error.

FTP reply codes are defined in RFC 354 and RFC 414 and according to those RFC's, reply codes are made of the following:.

The first digit specifies the type of error:

  • 4xx Unsuccessful reply. The request is correctly specified but the server is unsuccessful in correctly fulfilling it.
  • 5xx Incorrect or illegal command. The command or its parameters were invalid or incomplete from a syntactic viewpoint, or the command its inconsistent with a previous command. The command in question has been completely ignored.

The second digit specifies the general category to which the response refers:

  • x40 Secondary access. The primary server is commenting on its ability to access a secondary service.
  • x5x FTP results.

The final digit specifies a particular message type. Since the code is designed for an automaton process to interpret, it is not necessary for every variation of a reply to have a unique number. This is why jftp does not return this digit.

The officially assigned reply codes above 400 and relating to FTP are:

  • 400 This service not implemented.
  • 401 This service not accepting users now, goodbye.
  • 430 Log-on time or tries exceeded, goodbye.
  • 431 Log-on unsuccessful. User and/or password invalid.
  • 432 User not valid for this service.
  • 433 Cannot store files without valid account. Enter account.
  • 434 Log-out forced by operator action. Phone site.
  • 435 Log-out forced by system problem.
  • 436 Service shutting down, goodbye.
  • 450 FTP: File not found.
  • 451 FTP: File access denied to you.
  • 452 FTP: File transfer incomplete, data connection closed.
  • 453 FTP: File transfer incomplete, insufficient storage space.
  • 500 Last command line completely unrecognized.
  • 501 Syntax of last command in incorrect.
  • 502 Last command incomplete, parameters missing.
  • 503 Last command invalid (ignored), illegal parameter combination.
  • 504 Last command invalid, action not possible at this time.
  • 505 Last command conflicts illegally with previous command(s).
  • 506 Requested action not implemented by the server.
note

jftp will only return the first two digits of any reply code.

On UNIX and Microsoft Windows, jftp returns:

  • 0 on success.
  • 1 on usage errors and so on
  • the first two digits of the last FTP command result code when this is above 400.

See Also

  • Command Line System Tools
← jftpjgetcredential →
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |