Programmatic
FTP FAQS
Programmatic
FTP FAQS
The most powerful feature of PFTP is that it provides a well documented application programming interface (API) to the File Transfer Protocol. It enables your application software to move a file or files between any two network nodes, without having to be concerned with any of the details associated with the transfer.
The application formats a simple record that reflects the basic parameters of the desired file transfer. This includes such information as the to and from nodes, the to and from file names, etc. The formatted record is then written into a queue which the PFTP process monitors.
The PFTP process retrieves the request record, causes the file transfer to happen, and then returns the request record to the application with completion information.
The application retrieves the completion record and takes appropriate action depending upon the completion information.
We mean that the completion status of each and every requested file transfer is known and reported to the application by means of a completion record.
The completion record reflects the outcome of the request. If the file was transferred completely and correctly, the completion record reflects this fact. If the requested file transfer failed for any reason, the completion record reflects not only the failure, but also the reason for the failure.
No. Because PFTP employs what is known as a "proxy FTP", the two end points of the transfer may be any two network nodes. One of them may be the Tandem system, but it need not be.
The only software requirement is that the two network nodes representing the end points of the transfer be running an FTP server. No additional software is required on these nodes.
No. You run it as normal. This software runs in parallel and does not duplicate the functions of the FTP server.
In fact, the product was originally designed to accommodate Pathway servers via its asynchronous interface.
Once a request is queued to PFTP, the server is free to continue other processing (such as responding to a terminal user).
Either this server or another software component may monitor for the corresponding completion record and take appropriate action based upon the file transfer results.
In a variety of manners, depending upon application requirements.
Several customers have integrated their Pathway servers with this product. The Pathway servers interact with terminal users and make decisions about files that must be loaded onto user workstations. Once it is determined that a file be loaded onto a user workstation, the Pathway server effects the transfer via a PFTP request. Similarly, files may be transferred from user workstations to a central repository based upon Pathway server determination.
Other customers have used the product to cause the transfer of data files between the Tandem system and another different type of system. By using PFTP, they have the opportunity to process the data files before or after the transfer.
Possibly, depending upon the application requirements.
However, PFTP offers so many distinct advantages over this simple approach such as the high degree of auditabilty as well as extensive capabilities with respect to application integration (including application specific error recovery schemes) that is is almost an unfair comparison.
In other words, a TACL macro can do the job in the simplest of environments but PFTP can do it better in more complex environments or environments where completion information is considered important.
It should be kept in mind that PFTP was originally developed for a defense contractor who used this product to effect the transfer of true national security data over the network. Knowledge concerning the disposition of this data was an absolute requirement.
A product demonstration at your site can be easily arranged.