ASN5000-5999

ASN5101I

MONITOR monitor_qualifier. The Replication Alert Monitor program started successfully.

This message appears after a successful start of the Replication Alert Monitor program.

This message is for your information only, and no action is required.

ASN5102I

MONITOR monitor_qualifier : The Replication Alert Monitor version version_number program initialized successfully and is monitoring number alert conditions.

The Replication Alert Monitor program successfully started.

This message is for your information only, and no action is required.

ASN5103I

MONITOR monitor_qualifier. The Replication Alert Monitor program re-initialized successfully and is monitoring number-of-alert-conditions alert conditions.

The Replication Alert Monitor program successfully re-initialized.

This message is for your information only, and no action is required.

ASN5104W

MONITOR monitor_qualifier. number-of-alert-conditions alert conditions were ignored.

The Replication Alert Monitor program initialized or re-initialized. Some alert conditions that are not valid might be excluded as noted in previously issued messages.

Check the IBMSNAP_CAPTRACE table for messages about excluded alert conditions.

ASN5107I

MONITOR monitor_qualifier. The Replication Alert Monitor program stopped.

The Replication Alert Monitor program terminated.

This message is for your information only, and no action is required.

ASN5108W

MONITOR monitor_qualifier. The EMAIL_SERVER parameter was not set so e-mail notification cannot be sent.

You started the Replication Alert Monitor without specifying a value for the EMAIL_SERVER parameter, and the EMAIL_SERVER column in the IBMSNAP_MONPARMS table is empty. The Replication Alert Monitor will store any alerts in the IBMSNAP_ALERTS table.

If you want to receive e-mail notification for alerts, restart the Replication Alert Monitor with the EMAIL_SERVER value set.

ASN5109W

MONITOR monitor_qualifier. The MONITOR_ERRORS parameter was ignored because the EMAIL_SERVER parameter was not set.

The Replication Alert Monitor started but the MONITOR_ERRORS parameter was ignored because there was no value specified for the EMAIL_SERVER parameter. The MONITOR_ERRORS parameter requires the EMAIL_SERVER parameter. The Replication Alert Monitor will store any alerts in the IBMSNAP_ALERTS table.

If you want to be notified by e-mail when an alert occurs, restart the Replication Alert Monitor with the MONITOR_ERRORS parameter and the EMAIL_SERVER parameter set.

ASN5111I

MONITOR monitor_qualifier. number-of-rows rows were pruned from the table schema.table-name at timestamp timestamp.

The Replication Alert Monitor program pruned rows from the IBMSNAP_ALERTS or the IBMSNAP_MONTRACE table.

This message is for your information only, and no action is required.

ASN5117E

MONITOR monitor_qualifier. There are no valid Alert Conditions for this monitor qualifier on Monitor Server monitor_server.

The Replication Alert Monitor program cannot find any alert conditions for this monitor qualifier.

Verify that the monitor qualifier name used with the monitor_qual parameter is correct, and check that the alert conditions are enabled. Also, check any previously issued messages.

ASN5118E

MONITOR monitor_qualifier. The program cannot connect to the monitor control server server_name. The SQLCODE is sqlcode, and the SQLSTATE is sqlstate.

The Monitor program tried to connect to the monitor control server and failed with the corresponding SQLCODE.

Read the corresponding action for this SQLCODE, and correct the error.

ASN5119E

MONITOR monitor_qualifier. The program cannot connect to the server server_name. The SQLCODE is sqlcode, and the SQLSTATE is sqlstate.

An SQL CONNECT statement failed when the Monitor program tried to connect to the monitored Capture or Apply control server.

Read the corresponding action regarding this SQLCODE, and correct the error.

ASN5121E

MONITOR monitor_qualifier. A contact does not exist for the alert condition with a component of component, a server of server, a schema or qualifier of schema_or_qualifier, and a condition name of condition.

The specified contact does not exist in the IBMSNAP_CONTACTS table for this alert condition.

Verify the contact information, and correct the alert condition.

ASN5122E

MONITOR monitor_qualifier. The contact group group-name does not exist or is empty. The component is component, the server is server, the schema or qualifier is schema_or_qualifier, and the condition name is condition.

The contact group specified in an alert condition does not have corresponding contacts in the IBMSNAP_CONTACTGRP table or does not exist in the IBMSNAP_CONTACTGRP table. A contact group cannot be empty.

Verify the contacts for this group, and correct the alert condition.

ASN5123E

MONITOR monitor_qualifier. The table table_name was not found for program program_name. The server is server_name. The schema is schema. The condition name is condition_name.

The Monitor program could not find a table while attempting to monitor a condition on the server used by the program.

Verify that the table exists on the server, or correct the alert condition.

ASN5124E

MONITOR monitor_qualifier. The table table-name is not found. The Apply control server is apply-control-server. The Apply qualifier is apply-qualifier. The subscription-set name is set-name. The condition name is condition-name.

The Replication Alert Monitor program cannot find a table when attempting to monitor a condition on the Apply control server.

Verify that the table exists on the Apply control server, or correct the alert condition.

ASN5125E

MONITOR monitor_qualifier. The Apply qualifier apply-qualifier or the subscription set set-name is not found.

The Replication Alert Monitor program cannot find the Apply qualifier or the subscription set when attempting to monitor a condition on the Apply control server.

Verify that the Apply qualifier and the subscription set exist on the Apply control server, or correct the alert condition.

ASN5126E

MONITOR monitor_qualifier. There is an error sending a notification. The return code is rc.

When an alert notification was attempted, the ASNMAIL exit returned an error. The reasons for the error may include:

1

SMPT protocol failed. Verify the address of your e-mail server with your administrator.

2

SMPT socket failed. Verify the configuration of your e-mail server or client.

3

The e-mail address is not valid. Verify the e-mail address.

4

Software error.

99

ASNMAIL exit not found.

For return codes 1 and 2, verify the configuration of your e-mail server and client. For return code 3, check whether the e-mail address is correct. For return code 99, verify that the ASNMAIL exit is properly installed.

ASN5127E

MONITOR monitor_qualifier. An invalid value value exists in the column column-name of the table table-name.

This message indicates that the Replication Alert Monitor program found a column with a value that is not valid during program initialization.

Verify the values of the column definitions in the specified table.

ASN5128W

MONITOR monitor_qualifier. An alert condition was not processed because a row is missing from the table table_name. The condition name is condition_name. The server is server_name. The schema or qualifier is schema_or_qualifier.

Verify that the replication program (Capture, Apply, Q Capture, or Q Apply) is running with the appropriate settings. Also, verify that the alert conditions are specified correctly. Perhaps the schema or server name is wrong.

ASN5129I

MONITOR monitor_qualifier. The Replication Alert Monitor on server server-name reports an e-mail alert.

The Replication Alert Monitor program sent an e-mail alert.

This message is for your information only, and no action is required.

ASN5130I

MONITOR monitor_qualifier. capture_message. The Capture control server is capture-server. The schema is schema. The monitor control server is monitor-server.

The Replication Alert Monitor program retrieved a Capture program message from the IBMSNAP_CAPTRACE table when processing CAPTURE_ERRORS or CAPTURE_WARNINGS conditions.

Read the Capture program message, and take appropriate action. Also, check any errors or warnings from the Capture control server.

ASN5131I

MONITOR monitor_qualifier. apply_message. The Apply control server is apply-server. The Apply qualifier is apply-qualifier. The monitor control server is monitor-server.

The Replication Alert Monitor program retrieved an Apply program message from the IBMSNAP_APPLYTRAIL or the IBMSNAP_APPLYTRACE table when processing APPLY_SUBSFAILING, APPLY_ERRORS, or APPLY_WARNINGS alert conditions.

Read the Apply program message, and take appropriate action. Also, check any errors or warnings from the Apply control server.

ASN5133I

MONITOR monitor_qualifier. The following alert message_number has occurred number_of_times times in the last number_of_minutes minutes. The notification for this alert will be suspended.

This message is issued after an alert has been detected the number of times specified in the MAX_NOTIFICATIONS_PER_ALERT parameter (the default is 3) for the number of minutes specified in the MAX_NOTIFICATIONS_MINUTES parameter (the default is 60 minutes).

This message is for your information only, and no action is required.

ASN5134I

MONITOR monitor_qualifier. Alerts issued.

The text of this message appears in the subject line of the e-mail alerts sent by the Replication Alert Monitor program.

This message is for your information only, and no action is required.

ASN5135W

MONITOR monitor_qualifier. Too many alerts number_of_alerts for server server_name between lower_bound_time and upper_bound_time, schema or qualifier schema_qual_name, condition name condition_name.

The Alert Monitor reached the maximum of alerts allowed for a monitor cycle (1024), or memory can not be allocated for them. The Alert Monitor will send the notifications and will update the Monitor control server and will reconnect to the server starting in the next condition. Some alerts for the specified alert condition might not be sent and inserted in the Monitor control server.

You should verify the specified alert condition directly in the server to check if alerts were lost.

ASN5136W

MONITOR monitor_qualifier. There has been an error calling DAS component. The return code is rc for server server_name for schema or qualifier schema_qual_name and condition name condition_name.

While processing the condition name for the given server, the DAS component returned an error.

Verify that DAS is running properly in both the client and the remote server.

ASN5137E

MONITOR monitor_qualifier. An error occurred while calling the WebSphere MQ API. The condition name is condition_name. The server is server_name. The schema is schema. The queue manager is queue_manager. The queue name is queue_name. The MQI API is mqi_api_name. Reason code: reason_code.

Make sure that WebSphere MQ is running at the specified server and that the necessary objects exist, such as the queue manager and queue names.

ASN5150W

MONITOR monitor_qualifier. The program program_name is not running. The server is server_name, and the schema is schema. The database connection URL is connection_url.

The alert condition STATUS indicates that the program specified in this message is not running.

Verify the status of the program on the specified server.

ASN5151W

MONITOR monitor_qualifier. The elapsed time since the last commit of the Capture program exceeds the threshold value. The Capture control server is capture-server. The schema is schema. The last commit time is time. The threshold is seconds seconds.

The CAPTURE_LASTCOMMIT alert condition detects that the difference between the current timestamp value and the value of the MAX_COMMIT_TIME column in the IBMSNAP_RESTART table is greater than the threshold value of this alert condition as specified by the PARM_INT column value in the IBMSNAP_CONDITIONS table.

Check the Capture control server, and determine the reason for the commit delay.

ASN5152W

MONITOR monitor_qualifier. The current Capture latency exceeds the threshold value. The Capture control server is capture_server. The schema is schema. The Capture latency is latency seconds. The threshold is threshold seconds.

The CAPTURE_CLATENCY alert condition detects that the difference between the CURR_COMMIT_TIME and the MAX_COMMIT_TIME column values in the IBMSNAP_RESTART table is greater than the threshold value of this alert condition as specified by the PARM_INT column value in the IBMSNAP_CONDITIONS table.

Check the Capture control server, and determine the reason for the Capture latency.

ASN5153W

MONITOR monitor_qualifier. The latency exceeds the threshold value for program program_name. The server is server_name. The schema is schema. The latency is latency seconds. The threshold is threshold seconds.

Check the server to determine why the latency threshold is being exceeded.

ASN5154W

MONITOR monitor_qualifier. The memory used by the program program_name exceeds the threshold value. The server is server_name. The schema is schema. The amount of memory used is memory bytes. The threshold is threshold megabytes.

While processing the CAPTURE_MEMORY or the QCAPTURE_MEMORY alert condition, the Monitor program detected that the value of the CURRENT_MEMORY column in the IBMSNAP_CAPMON table or in the IBMQREP_CAPMON table is greater than the threshold. The threshold value of the alert condition is specified in the PARM_INT column in the IBMSNAP_CONDITIONS table.

Check the server to determine the reason for the excessive memory usage. Increase the memory_limit parameter of the program, if necessary.

ASN5155W

MONITOR monitor_qualifier. The memory used by the Q Apply program exceeds the threshold value. The Q Apply server is qapply_server. The Q Apply schema is schema. The receive queue is queue_name. The amount of memory used is memory bytes. The threshold is threshold megabytes.

While processing the QAPPLY_MEMORY alert condition, the Monitor program detected that the value of the CURRENT_MEMORY column in the IBMQREP_APPLYMON table is greater than the threshold value. The threshold value of the alert condition is specified in the PARM_INT column in the IBMSNAP_CONDITIONS table.

Check the Q Apply server to determine the reason for the excessive memory usage. If necessary, increase the value of the memory_limit parameter for the replication queue map that uses the specified receive queue.

ASN5156W

MONITOR monitor_qualifier. The size of a transaction exceeded the threshold for the program program_name. The server is server_name. The schema is schema. The transaction size is transaction_size bytes. The threshold is threshold megabytes.

While processing the CAPTURE_TRANSIZE or the QCAPTURE_TRANSIZE alert condition, the Monitor program detected that the value of the column in the IBMSNAP_CAPMON or IBMQREP_CAPMON table is greater than the threshold value. The threshold value for the alert condition is specified in the PARM_INT column in the IBMSNAP_CONDITIONS table.

Check the server to determine the reason for the excessive transaction size.

ASN5157W

MONITOR monitor_qualifier. The Q subscription subscription_name is inactive. The server is server_name. The schema is schema. State information: stateinfo.

While processing the QCAPTURE_SUBSINACT alert condition, the Monitor program detected an inactive Q subscription in the IBMQREP_SUBS table.

Check the IBMQREP_SUBS table on the server to determine why the Q subscription was put in the INACTIVE state.

ASN5160W

MONITOR monitor_qualifier. The Apply program is not running. The Apply control server is apply_server, and the Apply qualifier is apply-qualifier.

The APPLY_STATUS alert condition detects that the Apply program is not running.

Verify the status of the Apply program at the specified Apply control server.

ASN5161W

MONITOR monitor_qualifier. The subscription set is inactive and is in an error state. The Apply control server is apply-control-server. The Apply qualifier is apply-qualifier. The name of the subscription set is set-name. The WHOS_ON_FIRST value is wof.

The APPLY_SUBSINACT alert condition detects that the subscription set is inactive and that the status is not equal to zero (0).

If the subscription set should be active, check this subscription set on the Apply control server.

ASN5162W

MONITOR monitor_qualifier. A full refresh occurred. The Apply control server is apply-control-server. The Apply qualifier is apply-qualifier. The name of the subscription set is set-name. The WHOS_ON_FIRST value is wof.

The APPLY_FULLREFRESH alert condition detects that the target table was refreshed during the past monitor cycle.

If the full refresh was in error, verify the cause of the full refresh for this specified target table.

ASN5163W

MONITOR monitor_qualifier. The subscription is delayed beyond the threshold. The Apply control server is apply-control-server. The Apply qualifier is apply-qualifier. The name of the subscription set is set-name. The WHOS_ON_FIRST value is wof. The time delayed is time, and the threshold is threshold seconds.

The APPLY_SUBSDELAYED alert condition detected a subscription set that complies with the following conditions: CURRENT TIMESTAMP minus LASTRUN is greater than the threshold.

Check any previous messages to see if this subscription set has an error and to verify that the Apply program is running.

ASN5164W

MONITOR monitor_qualifier. The number of rows that were reworked in a subscription set exceeded the threshold. The Apply control server is apply-control-server. The Apply qualifier is apply-qualifier. The name of the subscription set is set-name. The WHOS_ON_FIRST value is whos-on-first. The number of reworked rows is rows, and the threshold is threshold rows.

The APPLY_REWORKED alert condition detects a subscription set with a value in the SET_REWORKED column of the IBMSNAP_APPLYTRAIL table that exceeds the specified threshold. The Apply program reworks changes under the following conditions:

• If an insert fails because the row already exists in the target table, the Apply program converts the insert to an update of the existing row.
• If the update fails because the row does not exist in the target table, the Apply program converts the update to an insert.

Look for other messages to determine the reason that this many rows were reworked.

ASN5165W

MONITOR monitor_qualifier. Transactions have been rejected in the subscription set. The Apply control server is apply-control-server. The Apply qualifier is apply-qualifier. The name of the subscription set is set-name. The WHOS_ON_FIRST value is wof. The number of rejected transactions is transactions.

The APPLY_TRANSREJECT alert condition detects rejected transactions for this subscription set.

Verify the reason why these transactions were rejected.

ASN5166W

MONITOR monitor_qualifier. A manual full refresh is required. The Apply control server is apply-control-server. The Apply qualifier is apply-qualifier. The name of the subscription set is set-name.

A full refresh is needed for the specified subscription set.

Verify the reason why a full refresh is required.

ASN5167W

MONITOR monitor_qualifier. End-to-end latency exceeded the threshold. The Apply control server is apply-control-server. The Apply qualifier is apply-qualifier. The name of the subscription set is set-name End-to-End latency is latency seconds, and the threshold is threshold seconds.

The APPLY_LATENCY alert condition detects that the end-to-end latency of this subscription set is greater than the threshold value of this alert condition as specified by the PARM_INT column value in the IBMSNAP_CONDITIONS table.

Check the Apply control server to determine the reason for this excessive end-to-end latency value.

ASN5168W

MONITOR apply_control_server. The processing of a subscription set finished in error. The Apply control server is control_server_name, and the Apply qualifier is apply_qualifier. The database connection URL is connection_url.

Examine the data in the IBMSNAP_APPLYTRAIL table at the Apply control server. If the row for the specified Apply qualifier does not contain information that indicates the source of the problem, contact IBM Software Support.

ASN5169W

Monitor monitor_qualifier : The Q apply processing message is error_message. The server is server_name, and the schema is schema_name. The database connection URL is connection_url.

This message is issued after a warning or error alert has been detected for the Q apply server.

The Replication Alert Monitor detected the warning or error information in the IBMQREP_APPLYTRACE table.

ASN5171W

MONITOR monitor_qualifier. The Q Apply latency exceeds the threshold value. The server is server_name. The Q Apply schema is schema. The MCGNAME or replication set name is mcg_name. The receive queue name is queue_name. The latency is latency milliseconds. The threshold is threshold seconds. The database connection URL is connection_url.

While processing the QAPPLY_LATENCY alert condition, the Monitor program detected that the value of the APPLY_LATENCY column in the IBMQREP_APPLYMON table is greater than the threshold value. The threshold value of the alert condition is specified in the PARM_INT column in the IBMSNAP_CONDITIONS table.

Check the Q Apply server to determine why the latency threshold is being exceeded.

ASN5172W

MONITOR monitor_qualifier. The end-to-end latency exceeds the threshold value for the Q Apply program. The server is server_name. The schema is schema. The MCGNAME or replication set name is mcg_name. The receive queue name is queue_name. The end-to-end latency is eelatency milliseconds. The threshold is threshold seconds. The database connection URL is connection_url.

While processing the QAPPLY_EELATENCY alert condition, the Monitor program detected that the value of the END2END_LATENCY column in the IBMQREP_APPLYMON table is greater than the threshold value of this alert condition. The threshold value is specified in the PARM_INT column value in the IBMSNAP_CONDITIONS table.

Check the Q Apply server to determine why the end-to-end latency is exceeding the threshold.

ASN5173W

MONITOR monitor_qualifier. An exception was found for the Q Apply program. The server is server_name. The schema is schema. The receive queue is queue_name. The reason code is reason_code. The SQLCODE is sqlcode. The SQLSTATE is sqlstate. The SQLERRMC is sql_tokens. The database connection URL is connection_url.

While processing the QAPPLY_EXCEPTIONS alert condition, the Monitor program detected a row in the IBMQREP_EXCEPTIONS table. The SQLCODE or SQLSTATE explains the reason for the exception.

Check the QAPPLY_EXCEPTIONS table on the server to determine the reason for the exception.

ASN5174W

MONITOR monitor_qualifier. The depth of the spill queue spill_queue_name for Q subscription subscription_name and receive queue receive_queue_name exceeds the threshold value. The server is server_name. The schema is schema. The current queue depth is current_depth%. The threshold is threshold%.

While processing the QAPPLY_SPILLQDEPTH alert condition, the Monitor program detected that the depth of the spill queue for the associated receive queue exceeds the threshold value. The threshold value of the alert condition is in the PARM_INT column in the IBMSNAP_CONDITIONS table.

Check the IBMQREP_APPLYTRACE table for additional information. Also, check the data in the IBMQREP_SPILLQS table, if available.

ASN5175W

MONITOR monitor_qualifier. The depth of the queue queue_name exceeds the threshold value for the program program_name. The server is server_name. The schema is schema. The current queue depth is current_depth%. The threshold is threshold%.

While processing the QAPPLY_QDEPTH alert condition, the Monitor program detected that the depth of the queue exceeded the threshold value. The threshold value, specified as a percent, is in the PARM_INT column in the IBMSNAP_CONDITIONS table. The value is obtained by dividing the current depth by the maximum depth attribute of the queue, and then multiplying it by 100 .

Verify that the program is processing the transactions for the queue as expected. Also, verify that the queue is large enough for the volume of transactions being processed.

ASN5176I

MONITOR : monitor_qualifier : Monitoring of server monitored_server was suspended at timestamp. The monitor suspension is suspension_name, and the suspension template is template_name.

All monitoring activities for the specified server are suspended because the monitor cycle is within the time, day, and duration for the specified suspension and template.

This message is for your information. No action is required.

ASN5177I

MONITOR : monitor_qualifier : Monitoring activities for server monitored_server were resumed at timestamp.

All previously suspended monitoring activities for the specified server are resumed because the monitor cycle is later than the time, day or duration for any suspensions defined for the specified server.

This message is for your information. No action is required.

ASN5178W

Monitor monitor_qualifier : The send queue send_queue_name is inactive. The server is server_name. The Q Capture schema is schema_name. State information: information.

While processing the QCAPTURE_SENDQSINACT alert condition, the monitor program detected an inactive send queue in the STATE column of the IBMQREP_SENDQUEUES table.

Use the replication administration tools or the state information that is provided in the message text to determine why the send queue was put in the INACTIVE state by Q Capture.

ASN5179W

Monitor monitor_qualifier : The receive queue receive_queue_name is inactive. The server is server_name. The Q Apply schema is schema_name. State information: information. State Time: timestamp.

While processing the QAPPLY_RECVQSINACT alert condition, the monitor program detected an inactive receive queue in the STATE column of the IBMQREP_RECVQUEUES table.

Use the replication administration tools or the state information that is provided in the message text to determine why the receive queue was put in the INACTIVE state by Q Apply.

ASN5180W

Monitor monitor_qualifier : The number of deadlock retries for transactions on Q Apply receive queue receive_queue_name exceeded the threshold value. The server is server_name. The Q Apply schema is schema_name. The current number of deadlock retries is number. The alert threshold for deadlock retries is threshold.

While processing the QAPPLY_DEADLOCKRETRIES alert condition, the Monitor program detected that the number of deadlock retries for transactions on the receive queue exceeded the alert threshold.

Check the environment. If a z/OS batch job is running, update the MAXAGENT_CORRELID value for the replication queue map that contains the receive queue to half the value of NUM_APPLY_AGENTS for the queue map. Both of these values are specified in the IBMQREP_RECVQUEUES table. For other OLTP transactions, check the environment to reduce the number of deadlocks.

ASN5181W

Monitor monitor_qualifier : The Q Capture program did not send data for large object (LOB) columns because the transaction size exceeds the maximum message size for the send queue that was specified in the replication queue map or publishing queue map. The server is server_name. The schema is schema_name. The send queue is queue_name. The number of rejected LOB columns that could not be applied because they were too big to fit in the maximum message size is number.

The Q Capture program processed the row that contains LOB values but rejected the LOB data because it exceeded the value that was specified for max_message_size for the replication queue map or publishing queue map that contains the send queue. The data was too large for the transaction message.

The QCAPTURE_LOBSTOOBIG alert condition detects the number of LOB columns that were not sent because they did not fit within the max_message_size value.

Use the replication administration tools to increase the max_message_size value for the replication queue map or publishing queue map. You might also need to increase the size of the MAXMSGL parameter for the WebSphere MQ send queue. Ensure that the value for the max_message_size parameter is at least 4KB smaller than value for the MAXMSGL parameter. If you cannot increase the max_message_size parameter, you can set the LOB_SEND_OPTION value in the IBMQREP_CAPPARMS table to S to send the LOB values in a LOB message after the transaction message. You need to issue the reinit command in either case. To synchronize the source and target tables, run the asntdiff and asntrep utilities.

ASN5182W

Monitor monitor_qualifier : The Q Capture program did not send data for XML columns because the transaction size exceeds the maximum message size of the send queue that was specified in the replication queue map or publishing queue map. The server is server_name. The schema is schema_name. The send queue is queue_name. The number of rejected XML columns that could not be applied because they were too big to fit in the maximum message size is number.

The Q Capture program processed the row that contained XML values but rejected the XML data because it exceeded the value that was specified for max_message_size for the replication queue map or publishing queue map that contains the send queue. The data was too large for the transaction message.

The QCAPTURE_XMLDOCSTOOBIG alert condition detects the number of XML columns that were not sent because they did not fit within the max_message_size value.

Use the replication administration tools to increase the max_message_size value for the replication queue map or publishing queue map. You might also need to increase the size of the MAXMSGL parameter for the WebSphere MQ send queue. Ensure that the value for the max_message_size parameter is at least 4KB smaller than value for the MAXMSGL parameter. Run the reinitq command to prompt the Q Capture program to read the changes to the queue map. To synchronize the source and target tables, run the asntdiff and asntrep utilities.

ASN5183W

Monitor monitor_qualifier : The Q Capture program exceeded the threshold for the number of retries to put messages on the send queue. The Q Capture server is server_name. The schema is schema_name. The WebSphere MQ send queue is queue_name. The number of retries is full_queue_retries and the monitor alert threshold for retries is threshold.

The Q Capture program could not put a message on the send queue using the MQPUT command. This condition can occur for several reasons:

• The Q Apply program is not processing messages on the receive queue.
• The Q Apply program is stopped.
• The Q Capture program is putting messages on the queue faster than WebSphere MQ can process them.
• Many changes accumulated at the source table while the Q Capture program was stopped.

This error is more likely to happen in a queue-sharing environment.

The QCAPTURE_QFULLNUMRETRIES alert condition detects a send queue with a QFULL_NUM_RETRIES column value in the IBMSNAP_SENDQUEUES table that exceeds the specified threshold.

Check for the possible causes listed in the "Explanation" section of this message. Also, check the WebSphere MQ reason code that the Q Capture program issued in its diagnostic log and take the appropriate action.

ASN5184E

MONITOR monitor_qualifier : An SQL error occurred when the monitor program was querying a monitor control table to determine status for program program_name. The monitor table name is table_name, the server name is server_name, the SQLCODE is sqlcode, the SQLSTATE is sqlstate.

An error occurred while the monitor program was trying to access the specified program's monitor table to check program status. The monitor could not determine the status.

Use the SQLCODE and SQLSTATE information to correct the problem. The monitor will continue running.

ASN5185E

MONITOR monitor_qualifier : An SQL error occurred when the monitor program queried the table_name table to determine status for the Apply program with Apply qualifier apply_qualifier. The server name is server_name, the SQLCODE is sqlcode, and the SQLSTATE is sqlstate. The monitor could not determine the program status.

An SQL error occurred that prevented the monitor program from accessing the control table to check Apply program status. The monitor continues running.

Use the SQLCODE and SQLSTATE information to correct the problem. After the problem is corrected, the monitor program will issue an alert if the program status meets the specified alert condition.

ASN5190E

MONITOR monitor_qualifier. An error occurred running the stored procedure stored_proc_name. The condition name is condition_name. The server is server_name. The schema is schema. The reason code is reason_code. The SQLCODE is sqlcode. The SQLSTATE is sqlstate. The SQLERRMC is sql_tokens.

The Monitor program was not able to run the specified stored procedure. The SQLCODE and SQLSTATE explain the reason.

Check the SQLCODE and SQLSTATE. At the server, verify that the definition of the stored procedure is correctly specified.

ASN5191W

MONITOR monitor_qualifier. message

This message appears when a user-defined alert condition issues a warning message.

Read the issued message, and take appropriate action.

ASN5192E

MONITOR monitor_qualifier. message

This message appears when a user-defined alert condition issues an error message.

Read the issued message, and take appropriate action.

ASN5193E

MONITOR monitor_qualifier. The stored procedure stored_proc_name was not found at server server_name. The condition name is condition_name. The schema is schema.

The stored procedure that is required by the Monitor program was not found at the server while processing the alert condition.

Verify that the CREATE PROCEDURE statement was issued at the correct server for the stored procedure name specified in the message.

ASN5194I

MONITOR monitor_qualifier : The monitor program will monitor alert conditions within the following time range time_range for monitored server server_name.

The monitor program looks for alert conditions that fall within the specified time range.

This message is for your information only. No action is required.

ASN5200E

ASNSCRT: The replication process type is a required parameter and must be specified when invoking the asnscrt command.

The asnscrt command was invoked without a specified replication process type.

Enter the command again with a replication process type of -C, -A, or -M.

ASN5201E

ASNSCRT: The database instance is a required parameter and must be specified when invoking the asnscrt command.

The asnscrt command was invoked without a specified database instance.

Enter the command again with a database instance name.

ASN5202E

ASNSCRT: A replication process path is a required parameter and must be specified when invoking the asnscrt command.

The asnscrt command was invoked without a specified replication process path.

Enter the command again with a path to the asncap, asnapply, or asnmon command.

ASN5203E

ASNSCRT: The Capture server is a required parameter and must be specified when invoking this asnscrt command.

The asnscrt command was invoked without a specified Capture control server.

Enter the command again with a Capture control server name.

ASN5204E

ASNSCRT: The Apply control server is a required parameter and must be specified when invoking this asnscrt command.

The asnscrt command was invoked without a specified Apply control server.

Enter the command again with an Apply control server name.

ASN5205E

ASNSCRT: The Apply qualifier is a required parameter and must be specified when invoking this asnscrt command.

The asnscrt command was invoked without a specified Apply qualifier.

Enter the command again with an Apply qualifier.

ASN5206E

ASNSCRT: The monitor control server is a required parameter and must be specified when invoking this asnscrt command.

The asnscrt command was invoked without a specified monitor control server.

Enter the command again with a monitor control server name.

ASN5207E

ASNSCRT: The monitor qualifier is a required parameter and must be specified when invoking this asnscrt command.

The asnscrt command was invoked without a specified monitor qualifier.

Enter the command again with a monitor qualifier.

ASN5208I

ASNSCRT: The replication service service_name was created successfully.

The asnscrt command successfully created the specified service.

This message is for your information only, and no action is required.

ASN5209I

ASNSCRT: The replication service service_name started successfully.

The asnscrt command successfully started the specified service.

This message is for your information only, and no action is required.

ASN5210E

ASNSCRT: The replication service service_name was not created, because the display name already exists (either as a service name or as another display name) in the service control manager database.

The asnscrt command cannot create the specified service, because the display name already exists as another service name or display name in the service control manager database.

Go to service control manager database, and remove the service with the duplicate service or display name. Then re-enter the command.

ASN5211E

ASNSCRT: The replication service service_name was not created, because the specified service name is not valid.

The asnscrt command cannot create the specified service, because the system API returned an error code indicating that the service name is incorrect. The specified service might contain special characters in the instance name, database name, or schema name. Special characters are not allowed in the service name.

Change the instance name, database name, or schema name if possible. Then re-enter the command.

ASN5212E

ASNSCRT: The replication service service_name was not created, because the specified service name already exists.

The asnscrt command cannot create the specified service, because another service with the same service name already exists in the service control manager.

Remove the existing service with the same service name. Then re-enter the command.

ASN5213E

ASNSCRT: The replication service service_name was not started, because the service binary file could not be found.

The asnscrt command cannot start the specified service, because the corresponding asncap, asnapply, or asnmon command cannot be invoked using the system path specified by the PATH environment variable. If the fully qualified path is provided, the asnscrt command cannot find the asncap, asnapply or asnmon command in that path.

Make sure the specified path is correct. Then re-enter the command.

ASN5214E

ASNSCRT: The replication service service_name did not start, because an instance of the service is already running.

The asnscrt command cannot start the specified service, because the service is already running.

This message is for your information only, and no action is required.

ASN5215E

ASNSCRT: The replication service service_name did not start, because the service depends on a database manager instance service that does not exist or has been marked for deletion.

The ASNSCRT command cannot start the specified service, because the corresponding database manager instance service does not exist or has been deleted.

Verify that the corresponding database manager instance service exists in the service control manager. Then reissue the command.

ASN5216E

ASNSCRT: The replication service service_name did not start, because this service depends on another service that failed to start.

The ASNSCRT command cannot start the specified service, because the corresponding database manager instance service failed to start.

Verify that the corresponding database manager instance service started in the service control manager. Then reissue the command.

ASN5217E

ASNSCRT: The replication service service_name did not start, because the service is disabled.

The asnscrt command cannot start the specified service, because the service has been disabled in the service control manager.

Verify that the service startup type is set to either automatic or manual in the service control manager. Then re-enter the command.

ASN5218E

ASNSCRT: The replication service service_name did not start, because the service cannot log on. This error occurs if the service starts from an account that does not have the proper "Log on as a service" access right.

The ASNSCRT command cannot start the specified service, because the corresponding database manager instance service cannot log on.

Go to service control manager, and locate the specified service. Verify that the provided account name and passwords are correct. Then reissue the command.

ASN5219E

ASNSCRT: The replication service service_name was not created, because the service is marked for deletion.

The asnscrt command cannot create the specified service, because the service was deleted.

Close the service control manager window. Then re-enter the command.

ASN5220E

ASNSDROP: The service name is a required parameter and must be specified when invoking the asnsdrop command.

The asnsdrop command was invoked without a specified service name.

Re-enter the command with a service name.

ASN5221I

ASNSDROP: The service service_name has been successfully removed.

The asnsdrop command was invoked with a specified service name.

This message is for your information only, and no action is required.

ASN5222E

ASNSDROP: The replication service service_name cannot be removed, because the requested access is denied.

The ASNSDROP command cannot remove the specified service name, because the user does not have the appropriate permission to remove it.

Verify that the current user has permission to log on to the corresponding database manager instance. Then reissue the command.

ASN5223E

ASNSDROP: The replication service service_name cannot be removed, because the specified service name is not valid.

The asnsdrop command cannot remove the specified service name, because the service name contains illegal special characters.

Go to service control manager, and locate the specified service. Verify that the service name is valid, and re-enter the command.

ASN5224E

ASNSDROP: The replication service service_name cannot be removed, because the specified service does not exist.

The asnsdrop command cannot remove the specified service name, because the service name does not exist in the service control manager.

Go to service control manager, and locate the specified service. Verify that the service name is correct, and re-enter the command.

ASN5225E

ASNSDROP: The replication service service_name cannot be stopped, because other running services are dependent on it. The service_name is not removed.

The asnsdrop command cannot remove the specified service, because other services that are dependent on this specified service are currently running.

Go to service control manager, and stop all services that are dependent on this specified service. Then re-enter the command.

ASN5226E

ASNSDROP: The replication service service_name cannot be removed, because the system is shutting down.

The asnsdrop command cannot remove the specified service, because the operating system is shutting down.

Enter the command again after system restarts.

ASN5227I

ASNSDROP: The replication service service_name cannot be removed, because it has already been marked for deletion.

The asnsdrop command cannot remove the specified service, because the specified service has already been deleted.

This message is for your information only, and no action is required.

ASN5228E

pgmname : The command cannot command_action the replication service service_name, because the system call API_func_name returned an unexpected error code error_code.

The asnscrt and asndrop commands make system calls in order to work with the services. The specified system call returned an unexpected error code that prevents the given command from completing the requested action.

Enter the command again. This error code might indicate only a temporary system condition. For further information about the error code, check your operating system documentation.

ASN5229E

ASNSCRT: The account is a required parameter and must be specified when invoking the asnscrt command.

The ASNSCRT command was invoked without a specified account name for the corresponding database manager instance.

Reissue the command with an account name for the corresponding database manager instance.

ASN5230E

ASNSCRT: The password is a required parameter and must be specified when invoking the asnscrt command.

The ASNSCRT command was invoked without a specified password for the corresponding database manager instance.

Reissue the command with the password for the corresponding database manager instance.

ASN5231E

ASNSCRT: The replication service service_name was not created, because the account name specified on the account parameter does not exist.

The ASNSCRT command was invoked with an unknown account name for the corresponding database manager instance.

Verify that the provided account name and passwords are correct. Then reissue the command.

ASN5232E

ASNSCRT: The required parameter path was not specified.

When started as a service, a replication command must contain a path specified by the path keyword that is specific to the command (capture_path for asncap, apply_path for asnapply, and monitor_path for asnmon). If the path keyword is specified, the service is registered if no errors occur.

If the path keyword is not specified, the asnscrt command retrieves the DB2 global registry profile variable DB2PATH. If this variable contains a non-null value, the asnscrt command adds the appropriate path keyword to the command using the value of DB2PATH. If this variable is not set, the asnscrt command cannot register the service.

Enter the command again after you specify the appropriate path keyword or after you define the DB2 global registry profile variable DB2PATH.

ASN5233E

ASNSCRT: The replication service service_name was not created, because the specified database instance database_instance does not exist.

The asnscrt command cannot create the specified service because the specified database instance does not exist in the system.

Verify that the specified database instance exists in the system. Then reissue the command.

ASN5234E

ASNSCRT: The capture_server parameter is not specified.

The asnscrt command was entered without a Q Capture server name. The capture_server parameter is required.

Enter the asnscrt command again, with the capture_server parameter set to the Q Capture server name.

ASN5235E

ASNSCRT: The apply_server parameter is not specified.

The asnscrt command was entered without a Q Apply server name. The apply_server parameter is required.

Enter the asnscrt command again, with the apply_server parameter set to the Q Apply server name.