iFileAudit Problem Reports

Index:

iFileAudit Release 4 Problem Reports:

• Fix three minor issues.
  
• When running an initial analysis for a newly registered file, the analysis is failing with CPF0001.
  
• When doing a read trace on a sequential flat file, no record ID is showing.
  
• I am getting a MCH1202 error during an export process.
  
• I am seeing some differences between the on-line displays and the printed reports.
  
• Some longer fields appear to be truncated in the analysis process.
  
• I am getting an MCH3601 error during file analysis processing.
  
• I am getting an CPF2981 error during file analysis processing.
  
• The purge process on my system is failing with a CEE9901 error.
  
• The transaction files in iFileAudit are taking a very large amount of space on my system.
  

iFileAudit Release 3 Problem Reports:

• My file analysis processing is taking a very long time.
  
• Some transactions are missing for a source physical file I am tracking.
  
• Some field updates are not appearing in the history file.
  
• The file analysis process fails with an MCH0603 error.
  
• The file analysis process is creating very large joblogs on my system.
  
• A sequential file on my system is showing as having a manually defined key in iFileAudit, but no such key exists.
  
• After setting up the web-enabled interface, my HTTP server instance is failing with an internal server error.
  

iFileAudit Release 2 Problem Reports:

• The file analysis fails intermittently with CPF9803.
  
• When registering and activating a file, I get a CPF0001 error.
  
• We are getting a CPF7055 error when running the FILANZ process for *ALL files in a library.
  
• We are running low on disk space, can anything be done in iFileAudit to help?
  
• The FILANZ analysis command is failing with message CPF2817.
  
• The iFileAudit purge is failing with error message CPF0555.
  
• The ANZDTL program is failing with a MCH1202 error code.
  
• When using the CRTIFAREG command to register multiple files at once, I get an error that indicates a wrong journal and journal library combination.
  
• I am getting an MCH0603 error during the file analysis process.
  
• When adding a key structure to a registered file, I sometimes see a message at the top of the screen indicating that a record has been updated by another user.
  
• 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.
  

iFileAudit Release 4 Problems:

Fix three minor issues.

We have now fixed three unrelated minor issues with iFileAudit as follows:

1. When using the CRTIFAREG command to register multiple files in a single run, some default settings were not getting set correctly. This is now fixed.
2. When running the WWWINSTAL program to install browser interface objects, some customers reported a failure due to a local configuration conflict. We have now fixed this so that it will always install correctly.
3. Incorrect results could be shown when setting or clearing read trace settings if the file being worked on is in use. We have now fixed this so that an error will be shown if this happens and the registration information will be recorded correctly.

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

We found that when the default journal process scope was set to *CURRENT and you ran the analysis process for a single file, a CPF0001 would be issued. In the joblog, you will also see a message reporting "*CURRENT must be the only value for parameter RCVRNG". This problem has now been corrected.

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

... and

I am getting a MCH1202 error during an export process.

When doing read tracing on a sequential file that is defined without any record keys, we found that iFileAudit was leaving the record ID field blank. This has now been fixed so that the relative record number is shown (RRN) to match the way other tracking in iFileAudit identifies such records.

We have fixed the issue with the MCH1202 error during an export function when specifying the *LONG output record format.

Both of these problems have now been fixed.

The fixes for these problems are available as a PTF. This PTF can only be installed on a Release 4.09 version of iFileAudit. The correction is available in PTF package FAPTF410. E-mail us and request the PTF package.

On three of the five reports we found that the before and after field contents could sometimes appear with wrong field content. The on-line displays were always showing the correct information, but the "Audit Report by Field, Date & Time", "Audit Report by Key, Date & Time" and "Audit Report by Key, Field, Date & Time" were sometimes showing wrong field content. This has now been corrected.

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

We found that under certain circumstances, this could happen. The field information is stored, but not available to the program.

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

... and

I am getting an CPF2981 error during file analysis processing.

For the MCH3601 error code, we found that under certain circumstances, when running the file analysis process for a single file, it could fail with this error code.

For the CPF2981 error code, we found that when you were running the file analysis process for a group file files (or all registered files) and some of those files had layout changes since the last analysis, this error could sometimes come up.

Both of these problems have now been fixed.

The fixes for these problems are available as a PTF. This PTF can only be installed on a Release 4.05 version of iFileAudit. The correction is available in PTF package FAPTF406. E-mail us and request the PTF package.

We found that under certain circumstances, the purge process could fail with this error. The problem has now been identified and corrected.

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

Several customers have contacted us about this problem. We have now re-engineered the transaction storage files so that they now take up less than half the space used by earlier releases of the software.

The fix for this problem is available only via a version upgrade. No PTF is available. Go to our download page and follow the instructions there to download the new version and install it. E-mail us if you have any questions about this process.

iFileAudit Release 3 Problems:

My file analysis processing is taking a very long time.

After implementing the previous round of changes to support the requirements for tracking source physical files (see next entry below), we found that some customers experienced a much longer file analysis time. Since tracking information for source physical files is rarely a requirement for most customers, we made that level of analysis option with a new setting in the IFASET command. The default value will result in much quicker analysis processing for most customers.

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

A customer reported that when they tracked updates to a source physical file, some member operations were not being picked up by iFileAudit. We have not identified why this was happening and have updated the software to include these transactions. Note that we specifically do not recommend iFileAudit for tracking source physical file changes, especially when the source members are maintained using IBM's PDM utility. Please see the FAQ page for more information.

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

We discovered a problem with the file analysis that could cause certain character fields to not be reported. This problem was introduced with release level 3.05.

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

Based on customer feedback, we discovered two situations that could cause this to happen. Both have now been fixed.

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

Based on a customer inquiry about this, we have now tweaked the file analysis process to significantly reduce the amount of information being logged in the joblog. This will improve performance and reduce disk storage during analysis processing.

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

A sequential file on my system is showing as having a manually defined key in iFileAudit, but no such key exists.

We found that if you start to create a key structure for a sequential file, but then end up not actually entering any key information, the system was still flagging the file as having a manually defined key. This is now fixed.

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

After setting up the web-enabled interface, my HTTP server instance is failing with an internal server error.

When an HTTP server reports a failure, you will find a detailed joblog for the failure in the output queue named QEZJOBLOG. Checking on this error, you will find that program QZSRCGI is failing with an MCH0802 error on a mismatch on the number of parameters in a program call.

We have traced this problem to an IBM problem. According to the IBM support website, this problem is fixed with a PTF. The specific PTF that you will need from IBM depends on the OS level that you have installed. For systems running V5R4, the PTF is SI35104. For systems running V6R1, the PTF is SI35112. Order the correct PTF from IBM and install it. If the PTF has been superceded, get the most recent PTF available. This should correct this error on these systems.

The file analysis fails intermittently with CPF9803.

A customer who was running the file analysis almost continually during prime shift reported that every once in a while the process would fail with a CPF9803 error. We have now modified the product to look for this situation and deal with it gracefully without issuing an error message.

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

A customer reported this problem to us and we identified it as happening when you register a file with the default journal name (*DFTN) and when the filename being registered has a period ('.') as a part of the name. We have now corrected this problem.

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

This can happen when you have a very large number of files being journaled on a common journal. The form of the DSPJRN command being used by iFileAudit up to this point could error out with this problem.

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

We have heard this from several customers, so we reviewed the specifications within iFileAudit and found one place where we could clear files from their temporary content when the analysis process completes successfully. This will make that disk space available when the analysis process is not in use. For customers with a lot of files or very active files, this disk savings can be helpful.

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

When using the FILANZ command, either from option #3 on the MASTER menu, from the command line or within your own CL program, was failing when the purge option was used. This was due to unrelated system changes introduced in a recent PTF. The problem is now corrected.

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

An error in a date calculation routine was causing this error. It is fixed now with the new PTF.

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

We found a problem under certain rare circumstances when this can happen. It only happens on files that have pre-existing journals attached which are set to only capture *AFTER images of the data. On certain types of updates, the IBM OS does not report full record information in this situation, most notably on record delete transactions. Our program had a problem under this situation when a portion of the record key contained a 1 character packed decimal data element. This has now been corrected by the following PTF.

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

When using this command with the default command parameters for the journal and journal library, an edit routine was incorrect causing an erroneous error message to be issued. 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 2.11 version of iFileAudit. The correction is available in PTF package FAPTF212. E-mail us and request the PTF package.

We found a problem in the file analysis process that could cause this when the file being analyzed contained a binary numeric field and the field contents were for a very large number. 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 2.09 version of iFileAudit. The correction is available in PTF package FAPTF210. E-mail us and request the PTF package.

This message is being issued in error. You can get around it by just replying 'Y' to the message where it asks you if you want to post the update anyway. We have also now fixed this problem with a program update.

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

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