This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Third-Party software (https://sqlbackupandftp.com/) automates the backups of SQL Server Databases, and the remote storage site can be designated as an FTP server. When attempting to upload the file, the software validates the upload by using the SIZE subcommand. Since the SIZE subcommand is not supported on the IBM i FTP Server, the job fails. I am requesting that the SIZE subcommand be added to the list of supported subcommands.
We will be able to upload and verify database backups from SQL Server instances using the IBM i FTP Server as a backup location. The third-party software is extremely user friendly and helps minimize the overhead in configuring SQL Server database backups. While we use DB2 for i as our database of choice for in-house operations, we also support customers that use other database systems, including SQL Server. See following URL for support case opened on third-party website: http://community.sqlbackupandftp.com/t/ftp-connection-failing-to-ibm-i-as-400/2536
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
IBM Power Systems Development
IBM is still considering this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it. IBM will use RFE votes and comments from others in the community to help prioritize this request.
Implementing the SIZE command for BINARY only transfers should be sufficient. I understand your explanation for size changes in ASCII files after being uploaded or downloaded due to the CCSID conversions, but would this really be an issue? IBM FTP Server could still return the size of the files, and it would be left up to the developer to determine when to use the result of the SIZE command based on the file type.
MDTM (File Modification Time) and REST(Restart of Interrupted Transfer) are not currently used in the business environment.
FTP SIZE command is an optional FTP subcommand which was defined in RFC 3659. IBM i FTP server does not support this command yet.
To add this subcommand to IBM i FTP server, the size is same as the file on IBM i file system when the file is transferred as binary mode. This can be used as the verification of file uploading. The size would be definitely same as it's original size on FTP client side.
It is a little complex when the file is transferred as ASCII mode. IBM i FTP server will do the code convension if the CCSID is different with client side. I do not want to detail how the CCSID is determined here. Let's assume the client side CCSID is Clt-CCSID and server side CCSID is Svr-CCSID. When the file is uploaded to IBM i FTP server, the file is converted to CCSID SvrC. If the file is downloaded to client side, the file is converted to CCSID Clt-CCSID. So, the file would be converted to CCSID Svr-CCSID first and then back to Clt-CCSID. The return of SIZE command would be the file size of after 2 times' conversion. Is the size same to the original file size on FTP client? We have no idea yet.
So, is not acceptable to only support the SIZE for binary transfer type ?
Except for this SIZE subcommand, 3659 also defined some other optional command which can be used to easy the file downloading and verification, such as MDTM (File Modification Time), REST(Restart of Interrupted Transfer) etc. Are these extension used in your business environment ?
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Networking
Operating system - IBM i
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Web Serving
Operating system - IBM i
Source - None