Messages BMCLUI000600 through BMCLUI000699

No log records were selected from dataSetName

Explanation: While discovering log data sets from the indicated RECON data set, Log Analyzer selected the indicated log data set for inclusion. However, no records were included from this data set. The data set was probably an online log data set (OLDS) that IMS reused before Log Analyzer could process it.

User response: No action is required.

Selected logs logCount exceeds maxlog specification maximumLogCount

Explanation: The MAXLOGS keyword limited the number of log data sets that could be processed. The number of log data sets exceeded the indicated MAXLOGS value. Log Analyzer processed only the indicated number of logs.

User response: No action is required.

Selected logs sldsCount exceeds maxlog specification maximumLogCount

Explanation: The MAXLOGS keyword limited the number of log data sets that could be processed, and the keyword specified an abnormal termination action. The number of log data sets exceeded the indicated MAXLOGS value. The ANALYZE task terminated abnormally with the specified abend code or terminated with the specified return code.

User response: Use the INTERVAL keyword to specify a narrower range of logs, or increase the value for the MAXLOGS keyword.

Internal error - errorInformation

Explanation: An internal process failed and the job terminated.

User response: Contact BMC Customer Support.

VSAM function error occurred at location errorlocation RC=returnCode, FDBK=feedbackCode

Explanation: The indicated VSAM service function failed with the indicated return code and feedback code. The client request could not be performed.

User response: Contact BMC Customer Support.

Insufficient storage to process this request, identification

Explanation: The region size for the address space was too small to accommodate the indicated process. The request failed.

User response: Increase the region size for the address space.

Improper API call identification

Explanation: The client (ISPF) made an incorrect call to a Log Analyzer API routine. The request failed.

User response: Contact BMC Customer Support.

Log Record Code x'code' was automatically included because of SELECT keyword specification

Explanation: Although the command syntax did not implicitly include the log record code, the code was automatically included to satisfy other selection criteria.

User response: No action is required.

Processing information

Explanation: This message indicates the progress of the job.

User response: No action is required.

Final analysis phase

Explanation: This message indicates that the final phase of processing is in progress.

User response: No action is required.

ERROR! productName password module not found

Explanation: The module that should contain your BMC password is missing from the STEPLIB concatenation. Because the password is necessary to authorize execution of the Log Analyzer analysis job on this CPU, the analysis job terminated.

User response: If you installed a password that should authorize the execution of Log Analyzer on this CPU, ensure that the library that contains the password module is included in the STEPLIB concatenation. If you have not installed a password, contact BMC Customer Support to obtain the password and create the missing module.

ERROR! productName phase 1 security failed RC=returnCode

Explanation: The procedure to check the CPU authorization password for Log Analyzer failed with the indicated return code. The analysis job terminated.

User response: Contact BMC Customer Support and report the contents of this message.

ERROR! productName phase 2 security failed RC=returnCode

Explanation: The procedure to check the CPU authorization password for Log Analyzer failed with the indicated return code. The analysis job terminated.

User response: Contact BMC Customer Support and report the contents of this message.

WARNING! productName license expires in number days.

Explanation: The procedure to check the CPU authorization password for Log Analyzer detected that your license will expire after the indicated number of days. Processing continues.

User response: Contact BMC Customer Support.

WARNING! productName has number days remaining during the product grace period

Explanation: The procedure to check the CPU authorization password for Log Analyzer detected that your license has expired. After the indicated number of days in the grace period, the product might be disabled. Processing continues.

User response: Contact BMC Customer Support.

ERROR! productName license error, grace period expired, RC=returnCode Reason=reasonCode

Explanation: The procedure to check the CPU authorization password for Log Analyzer failed with the indicated return code. The grace period has expired. The analysis job terminated.

User response: Contact BMC Customer Support and report the contents of this message.

productName has number days remaining during the product trial period

Explanation: The procedure to check the CPU authorization password for Log Analyzer determined that the trial period will expire after the indicated number of days.

User response: No action is required. You can continue to use Log Analyzer until the trial period expires.

ERROR! productName is running on an unauthorized cpu, trial period has expired

Explanation: The procedure to check the CPU authorization password for Log Analyzer failed. The trial period has expired. The analysis job terminated.

User response: Contact BMC Customer Support and report the contents of this message.

WARNING! productName license error, RC=returnCode, Reason=reasonCode, contact BMC Software

Explanation: The procedure to check the CPU authorization password for Log Analyzer failed with the indicated return code and reason code. Processing continues.

User response: Contact BMC Customer Support and report the contents of this message.

WARNING! productName has number days remaining in the product grace period, RC=returnCode Reason=reasonCode

Explanation: The procedure to check the CPU authorization password for Log Analyzer failed with the indicated return code and reason code. Your license has expired. After the indicated number of days in the grace period, the product might be disabled. Processing continues.

User response: Contact BMC Customer Support and report the contents of this message.

WARNING! productName has number days remaining in the product trial period

Explanation: The procedure to check the CPU authorization password for Log Analyzer determined that the trial period will expire after the indicated number of days. Processing continues.

User response: Contact BMC Customer Support and report the contents of this message.

ERROR! productName password has expired, contact BMC Software

Explanation: The procedure to check the CPU authorization password for Log Analyzer detected that the password has expired. The analysis job terminated.

User response: Contact BMC Customer Support and report the contents of this message.

ERROR! productName license error, RC=returnCode, Reason=reasonCode, contact BMC Software

Explanation: The procedure to check the CPU authorization password for Log Analyzer failed with the indicated return code and reason code. The analysis job terminated.

User response: Contact BMC Customer Support and report the contents of this message.

Storage compression has been entered

Explanation: Storage has been exhausted. Log Analyzer is attempting to reclaim storage and continue processing.

User response: Contact BMC Customer Support.

No storage released - no additional storage available

Explanation: Storage has been exhausted. Log Analyzer attempted to reclaim storage, but no additional storage was available. The job terminated.

User response: Contact BMC Customer Support.

Storage compression has been entered before

Explanation: Storage compression was entered previously and cannot be entered again. The job terminated.

User response: Contact BMC Customer Support.

The program must execute in an authorized state

Explanation: The execution environment required the program to reside in an APF-authorized load library and to be linked with the authorized attribute. Because these requirements were not met, the job terminated.

User response: Add the library to the APF authorization list and check the load module for AC(1) attribute.

Mis-matched quotes found in SELECT

Explanation: An odd number of quotation marks was found on the initial scan of the SELECT keyword. Most likely, the problem is in the CONTENT subkeyword. The job terminated.

User response: Correct the CONTENT subkeyword of the SELECT keyword and resubmit the job.

No data between quotes in CONTENT statement

Explanation: A CONTENT statement in the SELECT clause had a pair of double quotation marks that contained no data. The job terminated.

User response: Correct the CONTENT subkeyword of the SELECT keyword and resubmit the job.

DD Statement for ddname is missing

Explanation: The indicated DD statement was missing. The job terminated.

User response: Correct the JCL and resubmit the job

No log records were selected for processing

Explanation: The system log data set (SLDS) did not contain any records that were candidates for selection. No records were found within a specified interval, no records had the specified log record code, or both. No reports were generated, and the job terminated.

User response: Correct the syntax and resubmit the job.

BMCDBRC0 error during accessType, RC=returnCode, Reason=reasonCode, RECON=dataSetName

Explanation: The BMCDBRC0 RECON API failed. The job terminated.

User response: Contact BMC Customer Support.

messageNumber is an invalid message number

Explanation: An event required that a message be issued, but an internal error occurred while Log Analyzer was generating the message. The job continues if possible.

User response: Contact BMC Customer Support and provide the indicated message number.

DUPLICATE LOG RECORDS ENCOUNTERED

Explanation: Log Analyzer encountered log records that had duplicate key fields. (This condition typically indicates that the same log records are duplicates in the log record source.) The job terminated.

User response: Eliminate the duplicate log records and resubmit the job.

I/O error message: message

Explanation: A READ operation on a PDS failed. The job terminated.

User response: Correct the problem and resubmit the job.

pdsFunction error, RC=returnCode, REAS=reasonCode, dataSetName

Explanation: The indicated function failed for the indicated data set with the indicated return code and reason code. The job terminated.

User response: Contact BMC Customer Support.

PDS not a valid PDS: dataSetName

Explanation: The indicated data set was not a valid PDS. The job terminated.

User response: Correct the data set name and resubmit the job.

The definition of file dataSetName failed

Explanation: The definition process of the indicated file failed. The job terminated.

User response: Correct the file definition name and resubmit the job.

Required keyword keywordName is missing on the controlStatementCommand statement

Explanation: The indicated keyword was missing from the indicated control statement. This keyword is required on this statement. The job terminated.

User response: Add the required keyword and value and resubmit the job.

Syntax error, Invalid LOGRECORDCODES specification logRecordCode

Explanation: The indicated log record code was invalid. The job terminated, but Log Analyzer continued checking the syntax.

User response: Correct the error and resubmit the job.

Storage compression entered due to shortage

Explanation: Storage has been exhausted. Log Analyzer is attempting to reclaim storage and continue.

User response: Contact BMC Customer Support.

Storage compression entered due to record limits

Explanation: Storage has been exhausted. Log Analyzer is attempting to reclaim storage and continue.

User response: Contact BMC Customer Support.

synadExitIOErrorMessage

Explanation: An I/O error occurred but processing continued.

User response: See message BMCLUI0515I.

Logical EOF detected dsn=dataSetName at sequence number sequenceNumber

Explanation: Log Analyzer detected a logical end-of-file (EOF) condition while reading the indicated data set. The sequence number is the last record that was included in the analysis process from this file. This condition should occur only when Log Analyzer is reading an active online log data set (OLDS). Processing continues.

User response: No action is required.

number Log records encountered for previously discarded LUOWs

Explanation: Log Analyzer encountered the indicated number of log records that should be associated with logical units of work (LUOWs) that were discarded during storage compression. Processing continues.

User response: Check the diagnostics report to identify the affected LUOWs. Contact BMC Customer Support.

Storage compression exited

Explanation: Log Analyzer successfully compressed storage.

User response: No action is required.

SELECT= clause ignored

Explanation: A SELECT clause in an analysis job requested the Analysis Summary report as the only output. Log Analyzer ignored the SELECT filter and continued processing.

User response: No action is required.

LUOW consolidation started

Explanation: Log Analyzer started consolidating the logical units of work (LUOWs).

User response: No action is required.

LUOW consolidation ended

Explanation: Log Analyzer finished consolidating the logical units of work (LUOWs).

User response: No action is required.

Queue defrag in progress

Explanation: Log Analyzer started defragmenting the queue.

User response: No action is required.

Queue defrag complete

Explanation: Log Analyzer finished defragmenting the queue.

User response: No action is required.

DSN dataSetName does not have a valid SLDS format and cannot be processed

Explanation: Log Analyzer opened and read the indicated data set but could not process it. The data set did not conform to the format of a valid system log data set (SLDS). Processing terminated.

User response: Remove the indicated data set from the SLDS list and resubmit the job.

Parse finished with warnings

Explanation: Log Analyzer detected one or more warning conditions while parsing the input control statements. Previously issued messages state the reason for each warning. Processing continues.

User response: Identify the cause of each warning condition. If you did not receive the expected results from the analysis job, correct the cause of the problem and resubmit the job. Otherwise, no action is required.

Log Record Code specification ALL was modified to match the SELECT keyword specification

Explanation: The input control statements contained the LRC=ALL keyword, one or more SELECT keywords, and one or more keywords that requested reports other than the Analysis Summary (SUMMARY) report. In response, Log Analyzer changed the value of the LRC keyword to match the SELECT keyword specifications. The step completion code was elevated to 4, and processing continued.

User response: If you did not receive the expected results from the analysis job, change the keyword specifications and resubmit the job. Otherwise, no action is required.

INDEXFILE level indexVvrmm is not supported by this version of interfaceVrmm

Explanation: The index file that you attempted to access was created by the indicated version, release, and maintenance level (VRMM) of Log Analyzer. This VRMM does not match the VRMM of the Log Analyzer ISPF interface that you are using. The index file cannot be accessed by this level of the interface. The request fails.

User response: If the level of the index file is earlier than the level of the ISPF interface, re-create the index file. Use the matching extract file as input to an analysis job that uses the current level of Log Analyzer. If the level of the index file is later than the level of the interface, upgrade the ISPF interface to the later level.

moduleName abnormally terminated - code=abendCode reason=reasonCode

Explanation: Log Analyzer encountered a severe error in the indicated module and issued the indicated abend code and reason code. The analysis job failed.

User response: Contact BMC Customer Support.

ORPHANS report ignored, data not available

Explanation: The input control statements requested the Analysis Summary report and the Orphans report but did not request any other reports. Consequently, the data to build the Orphans report was unavailable. Log Analyzer ignored the request to build the Orphans report, elevated the step completion code to 4, and continued processing.

User response: No action is required.

ORPHANS report produced, but it may be incomplete

Explanation: Log Analyzer performed storage compression while executing the analysis job. As a result, the data in the Orphans report might be incomplete. Log Analyzer elevated the step completion code to 4 and continued processing.

User response: No action is required.

Syntax error, inconsistent SELECT CICSTRAN

Explanation: An error occurred during resolution of a SELECT CICSTRAN filter. The job terminated, but Log Analyzer continued checking the syntax.

User response: Correct the syntax and resubmit the job.

RECON error, RECON reconDataSetName at level reconLevel requires APF authorization

Explanation: Log Analyzer could not access the indicated DBRC RECON data set because the STEPLIB data set was not APF authorized. The job terminated.

User response: Authorize the STEPLIB data set and resubmit the job.

reconDataSetName used as COPY1 RECON

Explanation: Log Analyzer selected the indicated RECON data set as the COPY1 RECON data set to use for system log data set (SLDS) selections.

User response: No action is required.

Reprocessing SLDS to add discarded log records

Explanation: Log Analyzer discarded a logical unit of work (LUOW) and then found a log record that changed the LUOW filter status to TRUE. Processing continued.

User response: No action is required.

No SLDS were selected for reprocessing

Explanation: Log Analyzer discarded a logical unit of work (LUOW) and then found a log record that changed the LUOW filter status to TRUE. An internal logic error prevented reprocessing he system log data set (SLDS). Processing terminated.

User response: Contact BMC Customer Support.

IMS Release does not match release found on log releaseLevel

Explanation: The SLDS keyword specified an IMS release that did not match the indicated IMS release level, which Log Analyzer found while reading the SLDS. The analysis failed, and processing terminated.

User response: Correct the IMS release value of the SLDS keyword, and resubmit the job. If you cannot resolve the problem, contact BMC Customer Support.

Extract dataset dataSetName was moved and is now unusable

Explanation: Because the extract file was moved from its original location, possibly by SMS, the Log Analyzer ISPF interface can no longer use the file. The function terminates.

User response: Re-create the extract file and index file. To re-create the files, you can use the existing extract file as input to a new analysis job. You can also retrieve control statement syntax for the analysis job from the existing index file.

INDEXFILE dataSetName is not reusable - reason

Explanation: The Log Analyzer index file could not be reused for the indicated reason. The analysis task terminated abnormally.

User response: Delete the index file and resubmit the job.

Locate error dataSetName, RC=returnCode

Explanation: Log Analyzer attempted to find the indicated data set in the catalog, but the attempt failed. The analysis task terminated abnormally.

User response: Correct the data set name and resubmit the job. If you cannot resolve the problem, contact BMC Customer Support.

Recall of dataSetName failed, RC=returnCode, Reason=reasonCode

Explanation: An attempt to recall the indicated data set (which had been migrated) failed. The analysis task terminated normally, and Log Analyzer continued processing other tasks.

User response: Correct the problem and resubmit the job.

Internal error - dataSetName functionType diagnosticInfo1 diagnosticInfo2

Explanation: The indicated function to interrogate a data set failed. This message provides information for problem diagnosis. The analysis task terminated normally.

User response: Contact BMC Customer Support an provide the indicated diagnostic information.

Dataset dataSetName is being reused.

Explanation: Log Analyzer is reusing the indicated data set.

User response: No action is required.

Syntax error, inconsistent SELECT PST

Explanation: An error occurred during resolution of a SELECT PST filter. The job terminated, but Log Analyzer continued checking the syntax.

User response: Correct the syntax and resubmit the job.

Syntax error, inconsistent SELECT MPR

Explanation: An error occurred during resolution of a SELECT MPR filter. The job terminated, but Log Analyzer continued checking the syntax.

User response: Correct the syntax and resubmit the job.

An unexpected EOF encountered processing EXTRACT dsn dataSetName

Explanation: The indicated extract file was empty and could not be used. The function terminated.

User response: Contact BMC Customer Support.

EXTRACT DSN dataSetName cannot be processed by the current version

Explanation: The current version of Log Analyzer could not use the indicated extract file. The function terminated.

User response: Using the existing extract file as input to a new analysis job, create a new extract file. You can retrieve control statement syntax for the analysis job from the existing index file. Then, retry the function with the new extract file.

EXTRACT DSN dataSetName is multi-volume and cannot be used by ISPF

Explanation: The Log Analyzer ISPF interface could not use the indicated extract file because the file was created as a multiple-volume data set. The function terminated.

User response: Using the existing extract file as input to a new analysis job, create a new index file and single-volume extract file. You can retrieve control statement syntax for the analysis job from the existing index file. Then, retry the function with the new extract file.

The selected record cannot be read

Explanation: Log Analyzer could not read the selected record from the extract file because the TTR was invalid. The function did not return the record.

User response: Contact BMC Customer Support.

DB2 LOG DSN dataSetName contains a bad block - last good RBA is relativeByteAddress

Explanation: The indicated DB2 log contains at least one bad log record at the indicated last good relative byte address (RBA). Processing continues.

User response: No action is required.

DB2 LOG DSN dataSetName contains invalid segment code at RBA relativeByteAddress

Explanation: The indicated DB2 log contains an invalid segment code at the indicated relative byte address (RBA).  Processing continues.

User response: No action is required.

DB2 LOG DSN dataSetName contains invalid seg length at RBA relativeByteAddress

Explanation: The indicated DB2 log contains an invalid segment length at the indicated relative byte address (RBA). Processing continues.

User response: No action is required.

DB2 LOG DSN dataSetName contains invalid LCIDLAST at RBA relativeByteAddress

Explanation: The indicated DB2 log contains an invalid LCIDLAST value at the indicated relative byte address (RBA). Processing continues.

User response: No action is required.

DB2 LOG DSN dataSetName contains invalid last seg at RBA relativeByteAddress

Explanation: The indicated DB2 log contains an invalid last segment value at the indicated relative byte address (RBA). Processing continues.

User response: No action is required.

DB2 LOG DSN dataSetName contains invalid mid seg at RBA relativeByteAddress

Explanation:The indicated DB2 log contains an invalid middle segment value at the indicated relative byte address (RBA). Processing continues.

User response: No action is required.

Results from CONTENT search may be incomplete due to non-recoverable messages

Explanation: You requested a CONTENT search, and Log Analyzer encountered nonrecoverable log records. Because nonrecoverable log records contain no terminal data, Log Analyzer cannot process them during a CONTENT search. Therefore, results might be incomplete.

User response: No action is required.

Syntax error, FILTER keywords are not allowed with the REPORT selections

Explanation: The control statements for the analysis job requested a specialty report (such as the Deadlocks report or the Application Checkpoint report) and specified one or more filters. To prevent inconsistent or misleading results, Log Analyzer does not allow specified filters with specialty reports. Processing terminated.

User response: Remove the FILTER control statement, or remove the keyword that requests a specialty report from the REPORTS control statement. Resubmit the job.

Invalid report filter syntax for reportName

Explanation: The control statements for the analysis job requested a report and specified one or more filters. The specified filters were incorrect for the requested report. Processing terminated.

User response: Correct the FILTER control statement, and resubmit the job.

Syntax error, keyword value not numeric

Explanation: Log Analyzer requires a numeric value for the indicated keyword, but the specified value was nonnumeric. The job terminated, but Log Analyzer continued checking control statement syntax.

User response: Correct the keyword's value, and resubmit the job.

Syntax error, keyword value not correct

Explanation: The value of the indicated keyword is not a valid value. The job terminated, but Log Analyzer continued checking control statement syntax.

User response: Correct the keyword's value, and resubmit the job.

Module moduleName could not be loaded, RC=returnCode, reason=reasonCode

Explanation: A load operation for the indicated module failed. Log Analyzer received the indicated return code and reason code from the operating system. The job terminated.

User response: Use the return and reason codes to determine the cause of the failure. Correct the problem, and resubmit the job. If you need assistance, contact BMC Customer Support.

Catalog error: Module ID=moduleId, RC=returnCode, reason=reasonCode

Explanation: Log Analyzer requested a catalog lookup operation. The operation failed, and Log Analyzer received the indicated module ID, return code, and reason code from the operating system. The job terminated.

User response: Contact BMC Customer Support, and report the contents of this message.

Log record timezone offset does not match the source offset

Explanation: Log Analyzer compared the time zone offset from the log records to the offset from the indicated source (either the current operating system image or the value of the TIMEZONE keyword). The offsets did not match. Processing continued.

User response: Verify the time intervals that were either specified in the control statements or used by default. If the intervals are correct, no action is required. If the intervales are incorrect, correct the control statements and resubmit the job.

Log record timezone offsets are not consistent across all input log records

Explanation: Log Analyzer tracks time zone offsets from all input log records. Log Analyzer detected a mismatch and could not reconcile a single local time zone from the multiple input time zones. Processing terminated.

User response: Verify the time intervals that were either specified in the control statements or used by default. If the intervals are correct, specify the TIMEZONE=GMT keyword on the ANALYZE control statement and resubmit the job. If the intervals are incorrect, correct the intervals and resubmit the job.

No datasets were selected for prefix prefix

Explanation: In the control statements to run the analysis job, the IPRPREFIX keyword specified the indicated prefix. This prefix should match the data set name prefix of one or more journal data sets that the BMC Energizer for IMS Connect product created. Log Analyzer did not select any Energizer journals for one of the following reasons:

• No journal data sets match the specified prefix.

• No journal data sets that match the specified prefix also match the specified time interval.

User response: If one or more Energizer journals should have been included in the analysis, verify that the value of the IPRPREFIX keyword matches the journal data set name prefix that was specified in the Energizer options. If no Energizer jounals match the specified time intervals, no action is required.

Specified LRC value is insufficient for complete LUOWs

Explanation: The FILTER control statement specified the SELECT keyword and a value other than ALL for the LOGRECORDCODES (LRC) keyword. The specified set of log record codes did not contain all of the codes that Log Analyzer would have selected automatically, based on the specified SELECT filters. Log Analyzer used the specified set instead of the automatically selected set. Logical units of work (LUOWs) might be missing or incomplete. Log Analyzer set condition code 4, and processing continued.

User response: To ensure that all LUOWs are created and complete, remove the LRC keyword from the FILTER control statement and rerun the analysis job. If you want the batch reports to show only selected log record types, specify the LRC keyword in the REPORTS control statement.

The analysis found no log data that meets the filter/report criteria

Explanation: Given your specified parameters for selecting and filtering log records, Log Analyzer did not find IMS log data for producing one or more requested reports. For example, if you requested the Deadlocks report and Log Analyzer did not find any deadlock records within the selected time frame, Log Analyzer issued this message to indicate that it did not produce the Deadlocks report.

User response: Check the results to ensure that correct processing occurred. You might need to adjust the parameter values in the control statement data set. If the values are correct, no action is required.

Unsupported MQ header encountered - see trace dataset

Explanation: An unknown IBM WebSphere MQ header has been encountered in the IMS system log data set (SLDS). The job continued but did not process WebSphere MQ assets.

User response: Contact BMC Customer Support and provide the trace data set.

Dataset bootstrapDataSetName contains no active logs

Explanation: The indicated bootstrap data set does not have an archive log chain. BMC Log Analyzer for IMS cannot select any log data sets from this bootstrap data set.The job continued processing without logs from this subsystem.

User response: Correct the bootstrap specification to include only bootstrap data sets with archived logs, or ignore this condition.

No subsystemName logs have been selected for processing

Explanation: BMC Log Analyzer for IMS did not find any logs or journals for the indicated subsystem. The job continued processing without logs from this subsystem.

User response: Check the specified time interval, or ignore this condition.

Low private limit numberK, Ext private limit numberK, ATB number

Explanation: This informational message reports the maximum size limits for the region in the low private area, the extended private area, and above the bar.

User response: No action is required.

RECON data set dataSetName is defined as RLS in use

Explanation: Record-level sharing is defined for the indicated RECON data set. To process this data set, BMC Log Analyzer for IMS requires the STEPLIB data setto be APF-authorized and the XICOnnn to be included in the STEPLIB concatenation. Processing terminated abnormally.

User response: Correct the STEPLIB specifications, and resubmit the job.

Syntax warning, Mutually exclusive reports selected. reportKeyword is ignored.

Explanation: BMC Log Analyzer for IMS cannot produce the indicated report at the same time as it produces the other reports that you selected. Log Analyzer ignored this report request and continued producing the other selected reports.

User response: Run a separate analysis that requests the ignored report and omits the other report keywords.