. Kisco Home : Support : iFileUtility .
.
Last Updated: July 1, 2013

Current Release Level: 2.00 - available July 1, 2013. Release is for customers with systems running IBM i/OS V5R2 or higher.


To register your E-mail address and receive automatic notification when this page is updated, CLICK HERE

iFileUtility Problem Reports


The following program reports and resolutions all apply to this product when it was sold under the name Quick File Utility/400 (QFU/400).

Problem Report Dated: June 12, 2013

Affected release levels: All copies of iFileUtility distributed prior to June 12, 2013.

Problem Description:

On a file that contains a key field that is in ISO format with a date format setting of *EUR, the file view could fail with a CPF5097 error if an alternate value for the date field contents was selected
Problem Resolution:
We have made a programming change to recognize the *EUR format ISO field correctly.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF017. You will find an E-mail link to us on this page (see below).

Problem resolved on: June 19, 2013
Problem Report Dated: February 21, 2011

Affected release levels: All copies of iFileUtility distributed prior to February 21, 2011.

Problem Description:

On some systems, when using the F11 option from the file layout display screen, a CPF3201 error code can be issued.
Problem Resolution:
We have made a programming change to circumvent this error when it happens.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF016. You will find an E-mail link to us on this page (see below).

Problem resolved on: February 21, 2011
Problem Report Dated: September 3, 2009

Affected release levels: All copies of iFileUtility distributed prior to September 4, 2009 when used under any level of OS/400.

Problem Description:

Under certain rare conditions, a QFU function to display file information could fail because of bad data in the file that generates a character to the screen that cannot be displayed.
Problem Resolution:
As of this change, iFileUtility does a cleaner and more stable job of checking for non-display characters and treating them correctly without failing.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF015. You will find an E-mail link to us on this page (see below).

Problem resolved on: September 4, 2009
Problem Report Dated: April 29, 2008

Affected release levels: All copies of iFileUtility distributed prior to April 30, 2008 when used under any level of OS/400.

Problem Description:

Even with the recent security enhancement implemented (see following entry details), a user who has been configured with LMTCPB(*YES) (limited command line capabilities), access could be gained by using option 2 from the F13 display prompt.
Problem Resolution:
We have changed iFileUtility so that it checks for user profiles with LMTCPB(*YES). If a user is found with this and the installation is in protect mode (see following entry details), then iFileUtility will disable option 2 from the F13 display prompt. This will prevent unauthorized users from gaining access to unauthorized commands.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF014. You will find an E-mail link to us on this page (see below).

Problem resolved on: May 1, 2008
Problem Report Dated: April 14, 2008

Affected release levels: All copies of iFileUtility distributed prior to April 14, 2008 when used under any level of OS/400.

Problem Description:

When accessing any file, fields at the top of the detail file display allows the user to dynamically switch the display to view another file. Some installations would like to be able to suppress this feature for security purposes so that the user can only work with the file presented by the original invocation.
Problem Resolution:
iFileUtility was modified to establish a system-wide optional setting that, when activated, disables the ability to dynamically switch between files once the software has been started for a specific file.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF013. You will find an E-mail link to us on this page (see below).

Problem resolved on: April 15, 2008
Problem Report Dated: March 30, 2006

Affected release levels: All copies of iFileUtility distributed prior to March 31, 2006 when used under any level of OS/400.

Problem Description:

When attempting to update records in a file (using option 2), the program generation step fails and issues the message "Error creating display file - possible field too long". After reviewing the file, it is apparent that there are no long fields in the file. This only appears to happen on a very intermittent basis.
Problem Resolution:
Upon investigation, we found that when a file has a long filename, is stored in a library that is also long and also contains field names that are long, the combination can lead to an overflow situation when generating the required screen DDS statements. This leads to the observed failure. We have now modified the program that generates the DDS to sense when this overflow happens and generate the necessary continuation statements.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF012. You will find an E-mail link to us on this page (see below).

Problem resolved on: March 31, 2006
Problem Report Dated: March 31, 2005

Affected release levels: All copies of iFileUtility distributed prior to March 31, 2005 when used under any level of OS/400.

Problem Description:

When viewing field details on a file with an unusually long record length, some fields have incorrect field contents displayed.
Problem Resolution:
We found a problem in iFileUtility where fields after records position 2052 were getting displayed incorrectly. This problem has now been fixed.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF011. You will find an E-mail link to us on this page (see below).

Problem resolved on: April 1, 2005
Problem Report Dated: November 10, 2004

Affected release levels: All copies of iFileUtility distributed prior to November 11, 2004 when used under any level of OS/400.

Problem Description:

iFileUtility works fine for all of our files except one. When I try to run iFileUtility against this file, it fails with error code RPG0121 showing an "array index is not valid" message.
Problem Resolution:
iFileUtility had a limitation for working with files with large record lengths. If a file had a record length greater than 2,560 bytes, this message could appear when attempting to display an individual record detail. We have now doubled this limit to 5,120 bytes.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF010. You will find an E-mail link to us on this page (see below).

Problem resolved on: November 11, 2004
Problem Report Dated: November 2, 2004

Affected release levels: All copies of iFileUtility distributed prior to November 2, 2004 when used under any level of OS/400.

Problem Description:

iFileUtility works fine for all of our files except one. When I try to run iFileUtility against this file, it fails with error code RPG0100.
Problem Resolution:
iFileUtility had a built-in limitation for working with numeric data fields. This error would happen if a numeric field longer than 18 digits was present in a file. We have now increased this limit to 21 digits. This applies to both zoned numeric and packed data fields.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF009. You will find an E-mail link to us on this page (see below).

Problem resolved on: November 2, 2004
Problem Report Dated: January 26, 2004

Affected release levels: All copies of iFileUtility distributed prior to January 26, 2004 when used under any level of OS/400.

Problem Description:

Our files sometime get corrupted with bad numeric data in fields that are defined as numeric. I'd like to be able to use iFileUtility to fix this data, but it terminates with a decimal data error.
Problem Resolution:
iFileUtility creates simple RPG program to perform file update operations. The compile instructions for these programs is now changed to allow the programs to work with invalid data. The data may be displayed incorrectly, but customers should be able to enter corrected information when this happens. Prior to this change, the update programs would just end incorrectly without allowing for field updates.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF008. You will find an E-mail link to us on this page (see below).

Problem resolved on: January 26, 2004
Problem Report Dated: April 27, 2001

Affected release levels: All copies of iFileUtility distributed prior to April 27, 2001 when used under any level of OS/400.

Problem Description:

Occasionally, when browsing a file, the viewing program abnormally terminates due to a decimal data error.
Problem Resolution:
iFileUtility has now been sensitized to check for decimal data errors and continue operating when they are found. Some information displayed may be incorrect, but we felt it was better to have the program run rather than terminate abnormally. This will also permit users to correct bad data that is discovered.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF007. You will find an E-mail link to us on this page (see below).

Problem resolved on: April 27, 2001
Problem Report Dated: September 23, 1998

Affected release levels: All copies of iFileUtility distributed prior to September 22, 1998 when used under any level of OS/400.

Problem Description:

When using iFileUtility to work with a file with a highly fragmented key, iFileUtility fails with error message MCH0603.
Problem Resolution:
iFileUtility only permitted 35 key fragments on any single file. We have now increased this limit to 45 key fragments.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF005. You will find an E-mail link to us on this page (see below).

Problem resolved on: September 22, 1998
Problem Report Dated: September 3, 1998

Affected release levels: All copies of iFileUtility distributed prior to September 12, 1998 when used under any level of OS/400.

Problem Description:

When using iFileUtility to work with a file with a highly fragmented key, iFileUtility fails with error message MCH0603.
Problem Resolution:
iFileUtility only permitted 20 key fragments on any single file. We have now increased this limit to 35 key fragments.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF005. You will find an E-mail link to us on this page (see below).

Problem resolved on: September 11, 1998
Problem Report Dated: April 24, 1998

Affected release levels: All copies of iFileUtility distributed prior to April 25, 1998 when used under any level of OS/400.

Problem Description:

A customer added the iFileUtility application library name (QFULIB) to his library list to simplify use of the product. This was fine for the first use of iFileUtility during a signon session but the library was removed from the library list following the initial use. Subsequent attempts to use the product without a library reference failed.
Problem Resolution:
iFileUtility was forcing the library name into the library list if not already there. It was also forcibly removing the name from the library list when done with each use. Since the product has now been modified to work from a standard IBM command call, this is no longer needed in the program and it has now been removed.

If you have iFileUtility Release 1.0 with this problem and you would like to receive a PTF to correct it, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF004. You will find an E-mail link to us on this page (see below).

Problem resolved on: April 24, 1998
Problem Report Dated: January 13, 1998

Affected release levels: All copies of iFileUtility distributed prior to January 13, 1998 when used under any level of OS/400.

Problem Description:

When using the WRKDDS function from the file structure display, iFileUtility fails with error CPF2130.
Problem Resolution:
The problem is due to two missing objects in the QFULIB library. A PTF is now available to address this situation. If you have iFileUtility Release 1.0 with this problem and you would like to receive this PTF, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF003. You will find an E-mail link to us on this page (see below).
Problem resolved on: January 13, 1998
Problem Report Dated: January 12, 1998

Affected release levels: All copies of iFileUtility distributed prior to January 12, 1998 when used under OS/400 V3R2.

Problem Description:

When using the View Tree function, iFileUtility fails with error message CPF4131 followed by reporting of error message RPG1217 in program VIEWT.
Problem Resolution:
Found the problem, which was due to a change in a system provided file layout, and corrected the program to handle this situation correctly. A PTF is now available to address this situation. If you have iFileUtility Release 1.0 with this problem and you would like to receive this PTF, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF002. You will find an E-mail link to us on this page (see below).
Problem resolved on: January 12, 1998
Problem Report Dated: September 22, 1997

Affected release levels: All copies of iFileUtility distributed prior to September 23, 1997 when used under OS/400 V3R2.

Problem Description:

When attempting to use the Search and Replace function, iFileUtility fails and issues error message CPF4131.
Problem Resolution:
Found the problem, which was due to a change in a system provided file layout, and corrected the program to handle this situation correctly. A PTF is now available to address this situation. If you have iFileUtility Release 1.0 with this problem and you would like to receive this PTF, just send us an E-mail request and we'll return the PTF file to you by return E-mail. When ordering the PTF, specify PTF package name QFPTF001. You will find an E-mail link to us on this page (see below).
Problem resolved on: September 23, 1997

Contact Information

Kisco Information Systems
89 Church Street
Saranac Lake, New York 12983

Phone: (518) 897-5002 Fax: (518) 897-5003

E-mail your questions or suggestions: Support@Kisco.com


.
.
Kisco Information Systems 89 Church Street Saranac Lake, NY 12983
phone: 518.897.5002 | fax: 518.897.5003
sales@kisco.com about kisco kisco
products product
support kisco
consulting services useful
links