iFileAudit Problem Reports

Index:

iFileAudit Release 2 Problem Reports:

• When displaying a file analysis, I use option 5 to display the detail, but sometimes the wrong record is displayed.
  
• I ran the RPTFILD2 command to generate a report for all files in a library but ended up with all registered files.
  
• I am getting an MCH0603 in program ANZDTL when running the analysis process.
  
• When I use option 7 on the "Work With Registered Files" display, I get an error.
  
• The Display File Analysis function fails with an I/O error for some files.
  
• Some date selections for reporting do not appear to be working correctly.
  

iFileAudit Release 1 Problem Reports:

• Some fields appear to be missing from my file when I use the field maintenance option.
  
• For some files, it appears that not all records added to the file are being reported by iFileAudit.
  
• When running the file analysis, the program seems to get hung up and never finishes processing.
  
• I get a CPA0701 error when selecting option 6 from the Display Audit Details screen while trying to run a report.
  
• Some of the reports appear to be out of sequence.
  
• The latest file analysis date showing is sometimes wrong.
  
• Several more minor issue resolved - see details below.
  
• Product does not seem to work with files with the same name that are in different libraries.
  
• Several minor issue resolved - see details below.
  
• I sometimes get a CPF2817 error when running the file analysis process.
  
• When selecting options on registered files, only the first of several selections entered gets processed.
  
• When running the purge process, I get a CPF2817 error.
  
• When viewing audit information for a file, I sometimes see duplicate field update entries.
  
• After installing iFileAudit, I tried to display audit information for a file and I'm getting an error display.
  

When displaying a file analysis, I use option 5 to display the detail, but sometimes the wrong record is displayed.

Also: I ran the RPTFILD2 command to generate a report for all files in a library but ended up with all registered files.

The display file analysis detail screen was mixing field information from different records in the database. The database was correct and this PTF fixes the display program so that the detail screen information is now always correct. The other problem fixed here makes sure that the library parameter is enforced on the RPTFILD2 command when *ALL files have been selected.

The fix for these problems is now available as a PTF. This PTF can only be installed on a Release 2.07 version of iFileAudit. The correction is available in PTF package FAPTF208. E-mail us and request the PTF package.

Also: When I use option 7 on the "Work With Registered Files" display, I get an error.

The first of these two problems was only happening on files with very complex and long file key structures. An incorrect update in the last PTF issued, PTF FAPTF206, introduced the second problem. If you received this version of the software, you should also have received a warning and a patch. This PTF permanently fixes the problem.

The fix for these problems is now available as a PTF. This PTF can only be installed on a Release 2.06 version of iFileAudit. The correction is available in PTF package FAPTF207. E-mail us and request the PTF package.

When working with a file that has a multi-part key where one of the key elements was packed, iFileAudit would abnormally terminate with an I/O error to the display station. This has now been identified and corrected.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 2.05 version of iFileAudit. The correction is available in PTF package FAPTF205. E-mail us and request the PTF package.

When using the report commands or the function to export file information and you entered a specific starting end ending date and time, the results could be incomplete or incorrect in that not all the correct records were selected. This has now been identified and corrected.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 2.04 version of iFileAudit. The correction is available in PTF package FAPTF204. E-mail us and request the PTF package.

iFileAudit Release 1 Problems:

Some fields appear to be missing from my file when I use the field maintenance option.

If you registered your file and then made DDS field changes to the file, iFileAudit was not picking up these new fields. With this release change, whenever you use the field maintenance functions or the key maintenance functions, the field list will be updated automatically and new fields will then be included.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.31 version of iFileAudit. The correction is available in PTF package FAPTF132. E-mail us and request the PTF package.

We discovered a problem with certain file types where record additions to the file were not being picked up in the iFileAudit Analysis process. This has now been corrected.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.30 version of iFileAudit. The correction is available in PTF package FAPTF131. E-mail us and request the PTF package.

When registering and processing files with an unusually high number of fields in the file, we found a bug in the software that would cause the process to loop. This has now been fixed.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.29 version of iFileAudit. The correction is available in PTF package FAPTF128. E-mail us and request the PTF package.

When attempting to run a report using the option 6 from the Display Audit Details screen, we found that some parameters were getting passed incorrectly resulting in the CPA0701 error. In the joblog, you will also find a CPF0134 error that is the root cause of the problem. This has now been fixed.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.25 version of iFileAudit. The correction is available in PTF package FAPTF126. E-mail us and request the PTF package.

We found a problem introduced by a recent change that affected the sequencing of information on some of the reports. This has now been corrected.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.24 version of iFileAudit. The correction is available in PTF package FAPTF125. E-mail us and request the PTF package.

We found that when the file analysis is started just before midnight and runs until after midnight, the analysis date can get recorded incorrectly. This is now fixed.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.22 version of iFileAudit. The correction is available in PTF package WRPTF123. E-mail us and request the PTF package.

Several minor issues with iFileAudit have been reported recently that are now fixed.

1. When you try to display the transaction history for a file that has not yet been analyzed by iFileAudit, you will now no longer get a program dump, just a warning message.
2. If you have PAE installed on your system, the file registration delete functions will now work correctly.
3. Some files were intermittently showing up in the anaysis with blank audit reason codes. This has now been fixed.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.19 version of iFileAudit. The correction is available in PTF package FAPTF118. This PTF also includes several new product enhancements. E-mail us and request the PTF package.

iFileAudit has now been re-engineered to allow customers to work with files that have the same file name but are stored in different libraries.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.15 version of iFileAudit. The correction is available in PTF package FAPTF116. E-mail us and request the PTF package.

Several minor issues with iFileAudit have been reported recently that are now fixed.

1. A CPD0172 error was issued in the CRTIFAREG command due to a parameter conflict.
2. A file could get registered showing that it was only partially supported by iFileAudit when it was, in fact, fully supported.
3. When a customer has journals that only capture "after" update images (partially supported by iFileAudit), sometimes values were being reported in the "before" fields.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.12 version of iFileAudit. The correction is available in PTF package FAPTF113. E-mail us and request the PTF package.

We found that when you run the file analysis process against a file that has had no changes recorded in its associated journal, this error could be issued. It has now been fixed so that no error is issued.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.11 version of iFileAudit. The correction is available in PTF package FAPTF112. E-mail us and request the PTF package.

We found a programming problem that was limiting the actions on selected files to the first selection only. This has now been changed and the processes will occur for all selected files.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.09 version of iFileAudit. The correction is available in PTF package FAPTF110. E-mail us and request the PTF package.

We found that when you run a purge that results in a complete file purge (ie: all records are removed), then this error would happen. This has now been changed so that the purge will complete normally.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.09 version of iFileAudit. The correction is available in PTF package FAPTF110. E-mail us and request the PTF package.

iFileAudit keeps track of the last audit records processed and starts each new analysis run at the next audit entry record. We found a problem in the system where the last entry was sometimes getting picked up and reported more than once. This has now been corrected.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.07 version of iFileAudit. The correction is available in PTF package FAPTF108. E-mail us and request the PTF package.

iFileAudit requires that you perform an anlysis step before you can view the audit information. We have now changed the product to give you a better error message when this happens so that the reason for the error will be clearer.

The fix for this problem is now available as a PTF. This PTF can only be installed on a Release 1.05 version of iFileAudit. The correction is available in PTF package FAPTF106. E-mail us and request the PTF package.

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

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