ASN3000-3999

ASN Message ID	Message	Explanation	User Response
ASN3750I	The exception-reporting tool successfully started.	In response to an asnqexrp command, the replication exception-reporting tool successfully started.	This message is for your information only. No action is required.
ASN3751I	The exception-reporting tool will use the most recent start time of the Q Capture program as the start time for generating an exceptions report.	By default, the exception-reporting tool uses the most recent Q Capture start time as the start time for the exceptions report. The tool uses the timestamp when all stranded changes have been delivered and processed at the failover site as the end time of the report. You can change the start and end times by using the exception_report_start and exception_report_end parameters of the asnqexrp command.	This message is for your information only. No action is required.
ASN3752I	The exception-reporting tool will use the timestamp when all stranded changes have been delivered and processed at the failover site as the end time of the exceptions report.	By default, the exception-reporting tool uses the most recent Q Capture start time as the start time for the exceptions report, and the timestamp when all stranded changes have been delivered and processed at the fail-over site as the end time of the report. You can change the start and end times by using the exception_report_start and exception_report_end parameters of the asnqexrp command.	This message is for your information only. No action is required.
ASN3753I	`exception_number` exceptions were detected during the `duration` time between the start of the reporting period `exception_report_start` (`Q_Apply_time_zone`) and the end of the reporting period `exception_report_end` (`Q_Apply_time_zone`).	The exception reporting tool ran to completion and generated a report in the directory from which the asnqexrp command was invoked or in a directory that was specified by the file parameter.	This message is for your information only. Review the generated exception report.
ASN3754I	No exceptions were found during the `duration` time between the start of the report period from `exception_report_start` (`Q_Apply_time_zone`) to the end of the report period `exception_report_end` (`Q_Apply_time_zone`).	The exception reporting tool ran to completion and generated a report in the directory from which the asnqexrp command was invoked or in a directory that was specified by the file parameter. No exceptions were found during the reporting period.	This message is for your information only. No action is required.
ASN3755E	An invalid timestamp `timestamp` was used with the exception_report_start parameter when the exception-reporting tool started. The tool will stop.	The exception_report_start parameter requires a timestamp that uses any of the following formats: YYYY-MM-DD-HH.MM.SS.ssssss, YYYY-MM-DD-HH.MM.SS, YYYY-MM-DD-HH.MM, YYYY-MM-DD-HH, and YYYY-MM-DD.	Restart the tool and specify a timestamp in a valid format.
ASN3756E	An invalid timestamp `timestamp` was used with the exception_report_end parameter when the exception-reporting tool was started. The tool will stop.	The exception_report_end parameter requires a timestamp that uses any of the following formats: YYYY-MM-DD-HH.MM.SS.ssssss, YYYY-MM-DD-HH.MM.SS, YYYY-MM-DD-HH.MM, YYYY-MM-DD-HH, and YYYY-MM-DD.	Restart the tool and specify a timestamp in a valid format.
ASN3757E	An invalid timestamp `timestamp` was used with the exception_report_end parameter when the exception-reporting tool was started. The end time should be larger than the sum of the start time `timestamp` plus the monitor interval `interval_value`. The tool will stop.	When you specify an end point for the exceptions report, the timestamp that you provide for the exception_report_end parameter must be at least as long as one Q Apply monitor interval (specified by the monitor_interval parameter). The default Q Apply monitor interval is 60000 milliseconds or 1 minute on z/OS and 30000 milliseconds or 30 seconds on Linux, UNIX, and Windows. Typically the exception-reporting period would be significantly longer than one monitor interval.	Restart the tool and specify a timestamp with an appropriate value.
ASN3758E	The exception-reporting tool could not determine the timestamp that denotes when Q Capture was started to publish stranded transactions. A report was generated but no exceptions are shown in the report.	The asnqexrp command was issued, but no value was specified for the exception_report_start or exception_report_end parameters. When these parameters are not provided, the exception-reporting tool assumes that you want a report about exceptions that occurred during the delivery of stranded transactions after the most recent Q Capture restart. However, the tool must know when Q Capture was started to provide this type of report. The ASN0572I message that contains the timestamp of the most recent Q Capture start could not be found in the DESCRIPTION column of the IBMQREP_CAPTRACE table at the site of the outage. In this situation, the tool issues a report that does not contain any information about exceptions, but provides timestamps for recent Q Capture starts that you can potentially use as values for the exception_report_start or exception_report_end parameters.	Take one of the following actions, depending on what type of exceptions report you want: To generate a general exceptions report (a report that shows the exceptions whose causes are not limited to stranded transactions after a failover situation), reissue the asnqexrp command and specify the exception_report_start and exception_report_end parameters. These parameters specify the start time and end time of the exception-reporting window. To generate a report of the exceptions that were caused by the delivery of stranded transactions, reissue the asnqexrp command and specify the exception_report_start parameter with the restart time of Q Capture after the failover. If Q Capture was stopped and started multiple times before all stranded transactions were republished, specify the first time that Q Capture was started. All timestamps should be in the time zone of the Q Apply server.
ASN3759E	The exception-reporting tool did not find any records in the IBMQREP_APPLYMON table from the time period `timestamp` to `timestamp`, or could not determine the monitor interval of the Q Apply program. No exception report was generated.	The exception-reporting tool could not find any row in the IBMQREP_APPLYMON table in this exception-reporting window and therefore did not generate a report. The following are possible reasons: Q Apply was not started before the asnqexrp command was issued. The value of the Q Apply monitor_interval parameter is too large. Q Apply had not performed an insert into IBMQREP_APPLYMON before the asnqexrp command was issued and after the exception-reporting start time.	Take one of the following actions before reissuing the asnqexrp command, depending on the reason for the problem: Start the Q Apply program. Reduce the monitor_interval to a value that is less than 60000 milliseconds. Wait for three monitor intervals.
ASN3760W	The exception report that was generated by the asnqexrp command might not be accurate and complete because the Q Apply program was stopped during the exception-reporting window from `timestamp` to `timestamp`. This stoppage might have occurred before Q Apply finished writing all monitor statistics to the IBMQREP_APPLYMON table.	The exceptions reporting tool detected transactions that might have been applied but were not reported in the IBMQREP_APPLYMON table. Two things could have occurred: Q Apply was stopped before transactions or stranded transactions were applied. All transactions or stranded transactions were applied but the statistics in the IBMQREP_APPLYMON table do not reflect all of the transactions.	If you believe that Q Apply was stopped before all transactions or stranded transactions were applied, restart Q Apply and let it run until the value in the ROWS_PUBLISHED column of the IBMQREP_APPLYMON table is 0 for three consecutive monitor intervals. To avoid this problem in the future, take one of the following actions: Shorten the value of the Q Apply monitor_interval parameter so that it is less than 60000 milliseconds. If Q Apply must be stopped, let it run until the value in the ROWS_PUBLISHED column of the IBMQREP_APPLYMON table is 0 for three consecutive monitor intervals.
ASN3761W	The exception-reporting tool detected that the Q Apply program is still processing data. The exception report might not be accurate and complete.	The exception-reporting tool determined that Q Apply is still applying changes. Some of these changes might be stranded transactions that might cause exceptions. Thus the tool cannot provide a full report.	Take one of the following actions: Reissue the asnqexrp command with a timestamp for the exception_report_end parameter. Reissue the asnqexrp command until this warning message is not returned. By doing this, you can verify that Q Apply has finished processing all transactions that were stranded by the outage.
ASN3762W	The exception-reporting tool could not determine when the Q Apply program finished processing stranded transactions. The value of the exception-reporting window end time will appear as "N/A" in the report.	To generate a report of all exceptions that occurred during the processing of stranded transactions, the tool needs information from the Q Apply program. The following problems might have occurred: There is no row in the IBMQREP_APPLYMON table at the failover site where the value of ROWS_NOT_APPLIED or ROWS_APPLIED is greater than zero and MONITOR_TIME is later than the start time of the exception-reporting window. The Q Apply program is still running.	Take one of the following actions, depending on the reason for the problem: Reissue the asnqexrp command and specify an approximate timestamp for the exception_report_start parameter. Wait for three Q Apply monitor intervals and then reissue the asnqexrp command. Reissue the asnqexrp command with the exception_report_start and exception_report_end parameters to specify both the start time and end time of the exception-reporting window.