The following is a list of problems reported for i-2-S3 along with the solutions that we have developed for them. If you have a problem that is not covered here, ask us via E-mail and we'll address your problem.

Register your E-mail address to receive an automatic notification whenever there are changes to i-2-S3.

i-2-S3 Problem Reports

Index:

• Two fixes in release 1.17
• Several save commands fail on bad parameters.
• A large save from the IFS is failing with I2S0001.
• A restore is failing with MCH3601.
• It seems like very large saves to Amazon S3 are failing.
• I am unable to create a new bucket using i-2-S3.

i-2-S3 Release 1 Problem Reports:

1. A problem with the S3SAVOBJ and S3SAVCHGOB commands could result in a MCH1210 error being issued. This has been corrected.
2. The S3SAV command was posting the save activity with an incorrect object size. This has been corrected.

These fixes are available with Release 1.17 version of i-2-S3. If you have the previous release installed, we can send you a PTF update. Otherwise, you can install this new release from the download page for i-2-S3. Contact Kisco for details.

We have now tightened up the parameter editing on the S3SAVxxx commands so that required parameters cannot be left blank. We have also added parameter editting to the Destination Object Name field for all saves to make sure that the name conforms to Amazon S3 naming requirements.

The fix for this problem is available with Release 1.16 version of i-2-S3. If you have the previous release installed, we can send you a PTF update. Otherwise, you can install this new release from the download page for i-2-S3. Contact Kisco for details.

A large save from the IFS is failing with I2S0001.

We found a problem with the multipart upload to S3 when saving a large IFS backup set. It has now been corrected.

The fix for this problem is available with Release 1.14 version of i-2-S3. You can install this new release from the download page for i-2-S3.

A restore is failing with MCH3601.

This issue was traced back to a user error when an incorrect bucket name was specified for the restore. To avoid this issue in the future, we have now strengthened the parameter editting on all save and restore processes.

The fix for this problem is available with Release 1.13 version of i-2-S3.

It seems like very large saves to Amazon S3 are failing.

To address this issue, we have implemented the Amazon S3 API Multi-part save process for very large data transfers to S3 storage.

The fix for this problem is available with Release 1.09 version of i-2-S3.

I am unable to create a new bucket using i-2-S3.

Amazon S3 made some changes to their API interface that we needed to adjust for.

The fix for this problem is available with Release 1.08 version of i-2-S3.