ASN0000-0999

ASN0000I

ASN0004E

An error occurred when the START TRACE DB2 command was issued, or when the Capture program read the database log.

See the DB2 Codes section in the messages and codes documentation of the database manager on your operating system to find the appropriate reason code. For more information, see either of the following administration documentation: the Call Attachment Facility (CAF) for START TRACE DB2 errors, or the Instrumentation Facility Interface (IFI) for database log read errors, or contact your DBA. If the CAF or the IFI returned a message, it is also printed on the system display console.

ASN0005E

An error occurred when the Capture program read the database log. There might be an SQL error.

• For DB2 Replication, the sqlcode value is for the Asynchronous Read Log API.
• For Capture for VSE, the sqlcode is for the VSE/VSAM GET macro.
• For Capture for VM, the sqlcode is for Diagnose X'A4'.

See the DB2 Codes section in the messages and codes documentation of the database manager on your operating system for the appropriate reason code, as suggested in the following list:

• For Capture program for z/OS, see the Instrumentation Facility Interface (IFI) section in the administration documentation of the database manager on your operating system, or contact your DBA.
• For Capture for VSE, see the VSE/VSAM Commands and Macros, VSE/ESA System Macro Reference, and VSE/ESA V2R3 Messages and Codes manuals for more information.
• For VM/ESA, see the VM/ESA Programming Services for more information.
• For Capture on Linux, Windows, and UNIX, see the active and archived database logs administration documentation for DB2, or contact IBM Software Support.

ASN0006E

Contact IBM Software Support.

ASN0008I

The Capture program has stopped.

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

ASN0009E

When attempting to initialize a registration, the Capture program encountered a source table that is incorrectly defined. The Capture program cannot process the log records associated with a source table if the DATA CAPTURE CHANGES attribute of the source table is not set. This message is issued during a Capture program warm start or when the first CAPSTART signal is received for a subscription set against this registration. If this error occurs during the processing of a CAPSTART signal, the Capture program does not activate the registration. If this error occurs during a reinitialization (from a warm start or a reinit capture command), the Capture program places the registration in the "stopped" state, indicating that you must repair the registration before the Apply program can resynchronize the associated subscription sets.

ASN0011E

The Capture program received an error from the database log read interface. The reason code is from the database manager and indicates that the data on a log record cannot be processed because the compression dictionary for the corresponding DB2 table or table space is permanently unavailable. The compressed table or table space that contains this source table was probably reorganized by the REORG utility that ran without the KEEPDICTIONARY option. The Capture program cannot read the remaining compressed log records from source changes that occurred before the reorganization. The Capture program follows the option that was specified for Stop Capture on Error (Replication Center) or STOP ON ERROR (ASNCLP command-line program) for this registration.

Take one of the following actions, depending on whether the registration specifies that Capture stops on error:

No

No action is required. The Capture program deactivates the registration. The Apply program reactivates the registration and performs a full refresh of the target table.

Yes

Deactivate the registration and restart the Capture program. The Apply program reactivates the registration and performs a full refresh of the target table.

ASN0013E

A required column in the CD table is not defined.

Ensure that the CD table definition is correct.

ASN0019E

The Capture program must be APF authorized.

Authorize the Capture link library for APF, and restart the program.

ASN0020I

The Network Major Vector Transport (NMVT) could not be sent to Netview by the program because the program interface failed. This is a secondary informational message.

See the Netview programming documentation for a description of the return code to determine the interface error. The Capture program alerts are not received by the System Services Control Point (SSCP) until the error is corrected.

ASN0021I

Netview is unavailable. This is a secondary informational message.

See the Netview programming documentation for a description of the return code to determine the Netview problem. For example, the subsystem might not have been started.

ASN0023I

A REINIT command was issued to the Capture program. The Capture program then tried to refresh all the internal control information for all the registrations.

If the Capture program is capturing changes for all the registrations, no action is required. Otherwise, examine the preceding error messages to determine the cause of the failure, and follow the suggested user response to repair the failing registration definition. After you repair the registration, re-issue the REINIT command to the Capture program.

ASN0028I

An operator command has suspended the Capture program, and the program has entered a wait state.

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

ASN0029I

An operator command has resumed the Capture program from a suspended state, and the Capture program has continued running.

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

ASN0031E

The Capture program parameters table was not defined correctly or has been updated with rows that are not valid.

Make sure that there is only one row in the IBMSNAP_CAPPARMS table. Refer to the Table structures documentation in the SQL Replication Guide and Reference for additional information.

ASN0035E

The Capture program tried to initialize a registration and found that the registration definition contains an architecture level that is not valid. The Capture program can use only registrations that are at the compatible architecture level. This message is issued during Capture warm start or when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate.

Verify that the value in the ARCH_LEVEL column in the IBMSNAP_REGISTER table at the source server is correct. If the architecture level is at a lower level than what is expected by the Capture program, migrate the Capture control tables to a level compatible with the Capture program.

ASN0049I

The Capture program received a signal to stop capturing data. The Capture program commits current work in progress and terminates.

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

ASN0055E

The Capture program tried to initialize a registration and found that the registration definition contains an unsupported SQL type such as an abstract type. This message is issued during Capture warm start or when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate.

Use the replication administration tools to change the registration so that it does not contain the unsupported SQL type, or drop the registration.

ASN0057E

An error occurred when the Capture program was handling files. The Capture program terminates.

Ensure that the Capture program has correct access and security permissions for all required paths and files. Also, ensure that adequate space is available on your system. If you believe that this message was issued because of product failure, contact IBM Software Support for assistance.

ASN0058W

The value for the MAP_ID that is specified by the CAPSTART signal does not match any current value in the MAP_ID column of the IBMSNAP_PRUNCNTL table. The subscription set might have been deleted, or a user might have inserted the CAPSTART signal incorrectly.

If this CAPSTART was issued by a user, check that the MAP_ID for the Signal table insert is correct, and try again. If this CAPSTART signal was issued by the Apply program, verify that the subscription set still exists.

ASN0059W

When the Apply program signals a full refresh to the Capture program, the Apply program inserts a row for the CAPSTART signal in the IBMSNAP_SIGNAL table. At the same time, the SYNCHPOINT column of the IBMSNAP_PRUNCNTL table is set to hex zeroes. The Capture program then responds to the Apply program to confirm that the Capture program received the CAPSTART signal, as follows: the Capture program sets the value for the SYNCHPOINT column in the IBMSNAP_PRUNCNTL table to the number of the log sequence that corresponds to the CAPSTART log record. Because the Apply program set the value in the SYNCHPOINT column to hex zeroes, the Apply program checks if a nonzero value has been inserted by the Capture program. The Capture program updates the value for SYNCHPOINT, even if the value was not hex zeroes. However, if the value for SYNCHPOINT is not hex zeroes, the Capture program issues this warning that the value it found was not expected.

This warning can occur if you issue the APPLY CAPSTART signal yourself and do not completely simulate the actions of the Apply program.

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

ASN0060E

An unexpected error occurred in the Capture program. The Capture program terminates.

Contact IBM Software Support for assistance.

ASN0061E

The Capture program tried to initialize a registration and found that the source table specified in the registration was not in the source system catalog. This message is issued during Capture warm start or when the Apply program issues the first CAPSTART signal for a subscription set that contains a registration that is not valid. This error does not cause the Capture program to terminate. The values for the columns source_owner and source_table in the Capture control table IBMSNAP_REGISTER might have been incorrectly specified, or the source table was dropped and no longer exists.

If the registration is in error, correct the values for the columns source_owner and source_table. If the source table no longer exists, then the registration is no longer valid and can be removed.

ASN0062E

The Capture program tried to initialize a registration and found that the CD table specified in the registration was not in the source system catalog tables. This message is issued during Capture warm start or when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate. The values for the columns phys_change_owner and phys_change_table in the Capture control table IBMSNAP_REGISTER might have been incorrectly specified, or the CD table was dropped and no longer exists.

If the registration is in error, correct the values in the columns phys_change_owner and phys_change_table. If the CD table no longer exists, then the registration is no longer valid and can be removed.

ASN0063E

The Capture program tried to respond to a CAPSTART signal for a subscription and found that the source table which corresponds to the subscription was not in the source system catalog tables. This error message is issued when the first CAPSTART signal is received for a subscription that is not valid. This error does not cause the Capture program to terminate. The values for the columns source_owner and source_table in the Capture control table IBMSNAP_PRUNCNTL might have been incorrectly specified, or the source table was dropped and no longer exists.

If the subscription is in error, correct the values for the columns source_owner and source_table. If the source table no longer exists, then the subscription is no longer valid and can be removed.

ASN0064E

The Capture program tried to initialize a registration associated with a particular subscription and found that the registration contains one or more column values that are not valid. This message is issued when the first CAPSTART signal for a subscription is received against this registration. This error does not cause the Capture program to terminate. The values for the columns phys_change_owner and phys_change_table in the Capture control table IBMSNAP_REGISTER might have been incorrectly specified, or the CD table was dropped and no longer exists.

If the registration is in error, correct the values for the columns phys_change_owner and phys_change_table. If the registration is no longer needed, you can remove it.

ASN0065E

The Capture program tried to initialize a registration and found that the source table for the registration is a not a local physical table, but is instead on a non-DB2 relational server that is used as a source and called by a nickname. When a non-DB2 relational server is used as a source, data from each server is captured through a trigger program. Each source table must be in its own register table built on the non-DB2 relational server. This message is issued during a Capture warm start or when the first CAPSTART signal against this registration is received for a subscription. This error does not cause the Capture program to terminate. The registration has been created incorrectly in an IBMSNAP_REGISTER table in a database.

This registration must be rebuilt and made valid at the correct non-DB2 relational server.

ASN0066E

The Capture program tried to initialize a registration and found that the CD table for the registration that corresponds to the subscription is a nickname for a non-DB2 relational database used as a source. This message is issued when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate.

Non-DB2 relational sources are captured through trigger programs, and must be in their own register table in the non DB2 relational source system. CCD tables for such sources are also created in the non DB2 relational source system. Somehow the non-DB2 relational source table registration has been incorrectly registered in an IBMSNAP_REGISTER control table. This registration must be rebuilt at the correct non-DB2 relational server.

ASN0067E

The Capture program tried to initialize a registration and found that the view registration that corresponds to the subscription does not exist. This message is issued during Capture warm start or when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate. The values of the columns source_owner, source_table, and source_view_qual in the IBMSNAP_REGISTER or IBMSNAP_PRUNCNTL Capture control table could have been incorrectly specified. Therefore, either no match was found or the registration was dropped and no longer exists.

If the subscription or the registration is in error, correct the values in the columns source_owner, source_table, and source_view_qual. If the registration no longer exists, then the subscription is no longer valid and can be removed.

ASN0068E

The number of columns in the CD table is too large; the SQL INSERT statement exceeds the 32K Capture coding limit.

If all of the table columns are defined in the registration but only a subset of these columns are needed at the target, reduce the number of columns for that registration. Alternatively, split the table over two registrations so that each registration has a different subset of the table columns.

ASN0069E

The Capture program tried to insert a row into a CD table, and DB2 returned a SQLCODE indicating that the CD table no longer exists. The CD table could inadvertently have been dropped, or the whole registration could have been dropped. If there are still rows in the IBMSNAP_REGISTER table that refer to this CD table, the Capture program deactivates these registrations by setting the value of the CD_OLD_SYNCHPOINT column to NULL and no longer attempts to capture changes for this CD table. This error does not cause the Capture program to terminate.

If the CD table no longer exists and is no longer required, the registration is no longer valid and should be removed. It is recommended that you deactivate the registration before you remove it. Any subscription sets associated with registrations that use this CD table should also be deactivated. Additionally, the associated subscription-set members should be removed so that these subscription sets can be activated and can run successfully.

ASN0070E

The Capture program tried to initialize a registration and found that a column within the CD table for the registration is ambiguous. The column could refer to either a before image for one source column or to an after image for another source column. This message is issued during Capture warm start or when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate.

In the IBMSNAP_REGISTER table, change the current value in the BEFORE_IMG_PREFIX column to a character value that does not produce this ambiguity.

ASN0071E

The Capture program tried to initialize a registration and found that a column within the CD table for the registration is not compatible with the corresponding source column. This message is issued during Capture warm start or when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate.

Correct the CD table for this registration.

ASN0072E

The Capture program tried to initialize a registration and found that the before-image column within the CD table for the registration was not defined to accept null values. This message is issued during Capture warm start or when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate.

Correct the CD table for this registration.

ASN0073E

The Capture program found that the INPUT_IN value specified on the CAPSTOP signal is not in a valid format of phys_change_owner.phys_change_table. This error does not cause the Capture program to terminate, and no action is taken for this signal.

Ensure that the value of INPUT_IN matches the name of the CD table associated with the registration that you want to deactivate. Insert a new row into the IBMSNAP_SIGNAL table.

ASN0074E

The Capture program found that the INPUT_IN value specified on the CAPSTOP signal is in a valid format, and there is no match for the value of source_owner.source_table in the registration table. This error does not cause the Capture program to terminate.

Correct the value of INPUT_IN, and insert the signal again.

ASN0075W

The Capture program found that the INPUT_IN value specified on the CAPSTOP signal is in a valid format and matches the value of a source_owner.source_table in the registration table, but this registration is already inactive. This error does not cause the Capture program to terminate, and the Capture program takes no action for the signal.

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

ASN0076I

The Capture program successfully deactivated a registration that was specified in a CAPSTOP signal.

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

ASN0077E

The Capture program tried to initialize a registration and found that the column values of PHYS_CHANGE_OWNER and PHYS_CHANGE_TABLE within the IBMSNAP_PRUNCNTL table for the subscription do not match a registration row in the IBMSNAP_REGISTER table. The message was issued during Capture warm start or when the first CAPSTART signal was received for a subscription against this registration. This error does not cause the Capture program to terminate.

Correct the values in the IBMSNAP_PRUNCNTL table for this subscription. If this subscription was built using the Replication Center, contact IBM Software Support to report a potential administration problem.

ASN0078E

The Capture program tried to initialize a registration and found a before-image column within the CD table of the registration that has no corresponding after-image column. This message is issued during a Capture program warm start or when the first CAPSTART signal is received for a subscription against this registration. This error does not cause the Capture program to terminate.

Correct the CD table for this registration by ensuring that before-image columns are included in the CD table only when the corresponding after-image column is also included.

ASN0079E

The Capture program tried to update the IBMSNAP_REGISTER table to indicate that data has been captured for the named CD table, and DB2 returned a SQLCODE indicating that the rows no longer exist. The registrations could have been dropped. This error does not cause the Capture program to terminate.

If the registration has been dropped, no further action is required for the registrations. When dropping registrations, it is recommended that you deactivate the registrations first. If the rows in the IBMSNAP_REGISTER table were inadvertently deleted, drop the associated CD table and rebuild the registrations. Deactivate any subscription sets that are associated with the registrations. If a registrations must be dropped, remove the associated subscription-set members so that these subscription sets can be activated and can run successfully. If the registrations are rebuilt, a signal is sent to the Apply program indicating that a full refresh should be performed for the associated subscription sets.

ASN0080E

The Capture program tried to process an insert into the named CD table but was unable to process the insert due to a table space full condition. Typically this condition results from insufficient space allocation for CD table spaces, infrequent pruning, or ineffective pruning. This error causes the Capture program to terminate.

Take the following steps to determine the cause of the table space full condition:

1. Ensure that sufficient space has been allocated to the table space for this CD table in order to accommodate normal processing conditions.
2. Ensure that pruning is performed often enough to reduce the storage requirements for the Capture control tables.
3. Ensure that the Apply programs are running often enough to accommodate normal pruning processing.
4. Verify that no subscription sets have been deactivated for a long period of time without taking the additional steps necessary for normal pruning.

ASN0082W

During the initialization of a registration, the Capture program found that the registration definition contains a column in the CD table with a column length that is shorter than the corresponding column length in the source table. The registration definition is allowed, but a warning message is issued to inform you that the captured source table data might not fit within the defined CD table column. This message is issued during a Capture program warm start or when the first CAPSTART signal is received for a subscription against this registration. The registration initializes successfully.

Unless there is a specific reason why you need to define the registration in this manner (for example, if you are certain that the length of the changed data will never be larger than the length of the CD table column), you should define the registration so that the source table and the CD table data definitions match exactly.

ASN0083E

The Capture program tried to process an insert into a CD table and encountered a SQLCODE from DB2 that indicates that the CD table contains a column that is shorter than the length of the corresponding column in the source table. This error does not cause the Capture program to terminate, but the registration is placed in the stopped state.

Re-evaluate this registration definition. Either alter the registration so that the lengths of the source table column and the CD table column match or add a trigger to the CD table to truncate the data.

ASN0084E

This error message is issued any time that a registration is placed in the stopped state (with the STATE column set to a value of 'S' in the IBMSNAP_REGISTER table) by the Capture program. The reason for this action is described in one or more of the preceding messages.

Examine the preceding error messages to determine the cause of the failure, and follow the suggested user response to repair the failing registration definition. After you repair the registration definition, you must manually set the value of the STATE column to 'I' in the IBMSNAP_REGISTER table to indicate that the registration can be used again by the Apply program.

ASN0100I

This message informs you that the Capture program started, and the version of the Capture program.

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

ASN0101W

The data in the change data tables is too old. A cold start is performed.

No response is required.

ASN0102W

A problem occurred during the retrieval of the restart information. The restart table data is not valid. A cold start is performed.

• For DB2, an Asynchronous Read Log API error occurred during warm start while the database manager was reading the log.
• For z/OS, an Instrumentation Facility Information (IFI) error occurred during warm start while the database manager was reading the log.

Review diagnostic and monitoring information to determine why the warm start failed, then resolve the underlying error.

ASN0104I

The Capture program successfully processed a CAPSTART signal. If this is the first CAPSTART signal associated with a particular source table, this message indicates that the Capture program is now capturing updates to the source table. If this is a CAPSTART signal for a table for which changes are already being captured, this message indicates that the Capture program received the signal and performed the required processing to allow the Apply program to start receiving changes for the subscription set that is associated with the input MAP_ID value.

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

ASN0105I

The Capture program pruned records from a CD, UOW, TRACE, MONITOR, or SIGNAL table.

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

ASN0109I

This message is issued when the Capture program completes the reinitialization of registration entries. The reinitialization can occur during a warm start, during the processing of a CAPSTART signal, or in response to a Capture REINIT command.

If the Capture program is capturing the changes for all the registrations, no action is required. Otherwise, examine the preceding error messages to determine the cause of the failure, and follow the suggested user responses to repair the failing registration definition. After you have repaired the registration definition, issue the asnccmd command with the reinit parameter.

ASN0111I

This message is issued at the beginning of each pruning cycle.

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

ASN0112I

This message is issued at the termination of each pruning cycle.

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

ASN0113W

This warning message is issued when the values in the IBMSNAP_UOW table indicate that retention limit pruning could occur in the next day.

Check to see why regular pruning is not occurring. Usually this is because one or more Apply programs have not been run for a period of many days, and therefore the CD and UOW tables cannot be effectively pruned. Another potential hazard is the removal or deactivation of a subscription set, without the removal or reset of the corresponding synchpoint value in the table IBMSNAP_PRUNE_SET. The Replication Analyzer tool can be used to provide a detailed analysis of the situation.

ASN0114E

This error message is issued when pruning fails with an unexpected SQL error code. Pruning terminates and tries again at the next interval or command invocation. This error does not cause the Capture program to terminate.

Refer to the details of the given sqlcode.

ASN0121E

The lag_limit parameter represents the number of minutes that the Capture program can lag in processing records from the database log. Capture cannot warm start because it will process transactions older than is allowed by the user specified lag_limit.

Determine why the Capture program is behind in reading the log. If you are in a test environment, where you have no practical use for the lag limit parameter, you might want to set the lag limit higher and try starting the Capture program again. Alternatively, if you have very little data in the source table in your test environment, you might want to cold start the Capture program and fully refresh the data in all the target tables.

ASN0122E

A problem occurred while retrieving the restart information. The restart table data was not valid or for z/OS, an Instrumentation Facility Interface (IFI) error occurred while reading the log during a restart. When the error is resolved, you can restart using the warm start option.

Determine why the restart information could not be retrieved by Capture from IBMSNAP_RESTART. Look at previous messages for clues as to what may have gone wrong. Correct the problem, if possible and restart Capture warm. If the problem cannot be corrected, restart Capture cold.

ASN0123I

The Capture program terminates and records the values of the restart table at that time for auditing purposes.

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

ASN0133I

The Capture program terminated when it reached the end of the active log as requested by the user option of AUTOSTOP.

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

ASN0142E

This error message is issued when the monitoring thread has failed with an unexpected SQL code. Monitor functions for this interval are skipped, and the program tries again at the next interval. This error does not cause the Capture program to terminate.

Refer to the details of the given sqlcode.

ASN0143W

The Capture program started with a startmode of warmsa or warmsi. When the Capture program attempted to warm start, it received a return code from the database log read API that indicates that the source database has been restored or rolled forward and that log sequence numbers have been reused; the state of the source database and the state of the captured data are no longer consistent. The Capture program switched to a cold start.

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

ASN0144E

The Capture program started with a startmode of warmns or warmsi. When the Capture program attempted to warm start, it received a return code from the database log read API that indicates that the source database has been restored or rolled forward and that log sequence numbers have been reused; the state of the source database and the state of the captured data are no longer consistent. The Capture program terminates and does not automatically switch to a cold start.

If you are certain that it is safe to perform a Capture program warm start, restart the Capture program; it will not terminate on a second attempt. If you are not certain whether the captured data will be in a consistent state after a Capture program warm start, it is recommended that you perform a Capture program cold start.

ASN0180W

The Capture program detected that the IBMSNAP_SIGNAL table is not defined as an EBCDIC table. Additional processing is required to translate signals to EBCDIC to process them properly. The additional processing requires a small performance degradation.

ASN0181W

The Capture program processed the request from the signal but could not update the SIGNAL_STATE and SIGNAL_LSN. Therefore, the issuer of the signal cannot determine that the Capture program received the signal.

Determine if another process is expecting the update for the signal from the Capture program, and if necessary, re-send the signal.

ASN0182W

An initialization failure occurred, because the Capture program received a signal that was not encoded in EBCDIC. The Capture program could not translate the signal to EBCDIC, because the row in the IBMSNAP_SIGNAL table no longer exists. The Capture program cannot determine what signal was sent and so ignores it.

Determine what signal was sent, and re-send the signal.

ASN0183E

If a new partition was added, restart the Capture program with the add_partition=Y option.

If the IBMSNAP_PARTITIONINFO control table is corrupted, cold start the Capture program or call IBM Software Support.

ASN0184I

A new partition was added using the ADD_PARTITION option. The Capture program started processing for that partition.

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

ASN0185I

The Capture program requires the specified control table. If the Capture program does not find the control table, it creates the control table and its associated index on the appropriate Capture control server.

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

ASN0186W

This partition is not known to the source database. The Capture program captures data only from the partitions that are known to the source database.

Add the partition to the database and restart the Capture program using the ADD_PARTITION=Y option. If the partition is not needed, remove it.

ASN0187W

The Capture program cannot find a previously known partition in DB2. The partition is no longer part of the multipartition source server.

Verify that the missing partition was properly removed. No further action is required.

ASN0188I

The Capture program pruned records from a CD, UOW, TRACE, MONITOR, or SIGNAL table due to retention limit pruning.

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

ASN0189I

The registration has STOP_ON_ERROR = Y. The Capture program is terminating due to an error that is identified in a previous message.

ASN0190I

The Capture program deactivated the registration for the specified source table due to an error that is identified in a previous message. The Capture program did not terminate; it is still running because the registration has STOP_ON_ERROR = N.

Correct the error for this source table that is identified in the STATE column of the register (IBMSNAP_REGISTER) table and then reactivate the registration. When you reactive the registration, a full-refresh is performed.

To avoid a full-refresh in the future, set STOP_ON_ERROR to Y so that the Capture program terminates if it encounters the error.

ASN0191E

The Capture program could not process a log record because the log record has an unknown log variation type.

If Capture stopped because of this error, you will need to disable the registration or subscription with the matching DBID and OBID so that Capture can ignore this log record. If Capture did not stop because of this error, make sure this log record does not have data that you need replicated.

ASN0192E

The Capture program encountered a different version of the table because the table was altered. The Capture program was not able to determine the correct version by reading from the IBMQREP_COLVERSION and IBMQREP_TABVERSION tables. The tables might have been dropped.

Ensure that the IBMQREP_COLVERSION and IBMQREP_TABVERSION tables have not been dropped. If they are missing, restore these tables and restart the Capture program.

ASN0193W

During initialization, the Q Capture or Capture program tries to read from a restart point (either a specific Log Sequence Number when the Q Capture or Capture program is started in warm mode, or the current active LSN for cold starts). The initialization might take excessive time if the recovery log or the database is unavailable. In a DB2 multiple-partitioned environment or Oracle RAC environment, the log reader thread also takes longer to initialize.

Continue waiting for the log reader to initialize.

ASN0194W

When capture activates a registration for a table, it gathers table information from the system catalogs. If a partition was attached to the table before Capture activates the registration, the system catalog information might not correctly reflect where capture is in the log. For a newly attached partition, capture might incorrectly capture rows from the table before it was attached as a partition.

Stop capturing for the registration and perform a full refresh for the subscription set.

ASN0195I

The Capture program did not capture the transaction because the transaction ID was specified in the IGNORE_TRANSID parameter when Capture was started, or information for ignoring the transaction was inserted into the IBMQREP_IGNTRAN table.

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

ASN0196W

The source table was altered by one of the following DB2 online utility programs:

• LOAD SHRLEVEL NONE RESUME YES
• LOAD SHRLEVEL NONE REPLACE
• REORG TABLESPACE DISCARD
• CHECK DATA DELETE YES LOG NO
• RECOVER PIT
• EXCHANGE DATA ON CLONE TABLESPACE

The changes to the source table are not automatically replicated to the target table, and the two tables could be out of synch.

To maintain synchronization between the source and target, take one of the following actions:

• Perform a full refresh of the target table.
• Use the asntdiff program to identify any differences between the source and target tables, and then use the asntrep program to repair the differences.

ASN0197W

ASN0198E

The Capture program supports up to 16 partitions in a multiple-partitioned environment.

Reduce the number of partitions to 16 or fewer and start the Capture program.

ASN0199E

When a table is altered, it must be reorganized before the Capture program can begin processing log records for it. For the specified table, one of the following situations is likely:

• The table was altered but never reorganized.
• The table was altered after its most recent reorganization.

Reorganize the table and activate the registration.

ASN0200E

The Capture program received an error from the database log read. The error indicates that the data on a log record cannot be processed because the compression dictionary for the corresponding DB2 table or table space is temporarily unavailable. For z/OS, the reason code is a z/OS diagnostic code. For Linux, UNIX, and Windows, the reason code is an SQL code. One cause for the problem could be that the compressed table space is in the STOPPED state when the database log Read Interface attempts to read the compression dictionary. DB2 takes a latch on the source compressed table space to access the dictionary and the latch does not work if the table space is stopped. This error prompts the Capture program to stop.

The problem will be resolved when the compression dictionary becomes available. Restart the Capture program.

ASN0201W

When Capture activates a registration for a table, it gathers table information from the system catalogs. If a partition was detached from the table before Capture activates the registration, the system catalog information might not correctly reflect where Capture is in the log. For a newly detached partition, capture might incorrectly miss rows from the partition before it was detached.

Stop capturing for the registration and perform a full refresh on the subscription set.

ASN0202W

The Capture program detected that a column in a registered source table was altered. Capture automatically altered the CD table column to match the new data type.

If you want to replicate data from the altered column, you must alter the matching column in the target table.

ASN0203E

A DB2 pureScale system at Version 10 with two or more members requires a value of 1001 or higher in the COMPATIBILITY column of the IBMSNAP_CAPPARMS table.

Before upgrading the compatibility setting for the Capture program, review the effect of that change on any Apply programs or Apply control servers that Capture works with. You might need to migrate the Apply control tables to Version 10. If required, update the COMPATIBILITY column to 1001 or higher and restart the Capture program.

ASN0204E

The LSN value that Capture uses to find the correct restart point in the recovery log is not in the correct format. This problem can occur when you upgrade the database product to Version 10 but the IBMSNAP_RESTART table still contains LSN values from a previous version. The LSN values that replication uses changed for DB2 for Linux, UNIX, and Windows V10 and are not compatible with earlier saved LSN values.

Restart the Capture program with the migrate=y parameter, which updates the restart information to the correct format.

ASN0205E

The Capture program connection with the database manager terminated while the Capture program was reading the database log.

Look up the reason code from the DB2 for z/OS instrumentation facility interface (IFI) to verify why the connection was terminated. Fix any problems and restart the Capture program if necessary.

ASN0206E

The Capture program detected an ALTER TABLE RENAME COLUMN operation for the source table, but was unable to rename the corresponding before-image and after-image columns in the CD table. The program stopped.

Manually ALTER the CD table to rename the before-image and the after image-columns that correspond to the renamed source column and start the capture program.

ASN0207I

The Capture program detected an ALTER TABLE RENAME COLUMN operation for the source table, and renamed the corresponding before-image or after-image column in the CD table.

No action is required.

ASN0500E

The program or a command program has been invoked with a specified input parameter that is not valid. The message indicates the name of the program that is reporting the error, along with the parameter name and the parameter value.

Check the documentation on valid invocation parameters, correct the input, and resubmit the task or command.

ASN0501E

The program or a command program was invoked with an input value with an associated data type that is not valid. The message indicates the name of the program that is reporting the error, the incorrect input value, and the name of the parameter for which this input value was specified.

Correct the invocation to include the correct data type for the parameter input and resubmit it.

ASN0502E

The program or a command program has been invoked using an input value with a string length that is not valid. The message indicates the name of the program that is reporting the error, what input value is incorrect, and for which parameter this input value was specified.

Correct the invocation to include the correct string length for the parameter input and resubmit it.

ASN0503E

The program or a command program was invoked with an input value specified which is outside the supported range. The message indicates the name of the program that is reporting the error, which input value is incorrect, and for which parameter this input value was specified.

Correct the invocation to include the correct range value for the parameter input and resubmit it.

ASN0504E

The program or a command program has been invoked with a specified parameter or command that is not valid. The message indicates which program issued this message, and the invocation input that is unrecognized.

Check the documentation on valid input parameters, correct the input and resubmit the task or command.

ASN0505E

The program or a command program was unable to initialize the inter-process communications needed to process commands. This error causes the failing program to terminate.

Retry the failing program or command. Contact IBM Software Support if the problem persists.

ASN0506E

This problem could also have occurred because of an issue with the IPC message queue that the program uses to receive commands.

Verify that the parameter values are correct and that they identify a running replication program. Retry the command.

ASN0507E

The program or a command program encountered an internal error while trying to process a user command.

Retry the failing command. See "Troubleshooting problems with IPC message queues" for more information.

ASN0508E

The program or a command program encountered an internal error while trying to process a user command. The program did not terminate for this failure, but the command did not get executed.

Retry the failing command. Contact IBM Software Support if the problem persists.

ASN0509E

The program or a command program encountered an internal error while trying to process a user command. The program did not terminate for this failure, but the command did not get executed.

Retry the failing command. Contact IBM Software Support if the problem persists.

ASN0510E

The command program encountered an internal error while trying to process a user command. The program did not terminate for this failure, but the command did not get executed.

Retry the failing command. Contact IBM Software Support if the problem persists.

ASN0511E

The program encountered an internal error while trying to process a user command. The program did not terminate for this failure, but the command did not get executed.

Retry the failing command. Contact IBM Software Support if the problem persists.

ASN0512E

The program encountered an internal error while trying to process a user command. The program did not terminate for this failure, but the command did not get executed.

Retry the failing command. Contact IBM Software Support if the problem persists.

ASN0513E

This message file used by the program has been installed incorrectly, or the language environment variables are not set correctly.

Refer to the documentation for information about installation and configuration.

ASN0514E

The program encountered an internal error while trying to open a file for its own program message log, and terminates abnormally because of this failure. This problem might have occurred because the file was inadvertently deleted, or because the userid associated with this process does not have the sufficient authority to open the file.

Verify that sufficient authority is provided to the processing userid. If the file was inadvertently deleted, restart the program to create a new log file.

ASN0515E

The program encountered an internal error while trying to close the file used for its own program message log. The file might have been deleted inadvertently before the program tried to terminate. Final termination messages might not be issued.

If the file was inadvertently deleted, restart the program to create a new log file.

ASN0516E

The program encountered an internal error while trying to close the message catalog file. The file might have been deleted inadvertently before the program tried to terminate. Final termination messages might not be issued.

If the message file has been deleted, it needs to be reinstalled.

ASN0517E

The program was able to reinitialize its read capability from the message queue needed to process commands after a previous failure.

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

ASN0518E

The command program was invoked with multiple commands specified. Each command invocation must be performed with a single input command, along with any other required command input. Note: The CHGPARMS command allows multiple parameters to be changed with one invocation of the CHGPARMS command.

Correct the command input, and resubmit the command.

ASN0519E

The CHGPARMS command was invoked with incorrect parameter input.

Correct the command input and resubmit the command.

ASN0520I

In response to the status command, one of these messages will be issued for each of the threads associated with the program that received the command, in each case providing the current state of that thread.

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

ASN0521I

In response to the QRYPARMS command, a message will be issued for each of the program parameters. For each parameter, the message provides the name of the parameter, the current setting of the parameter, and the method (by default, by changing the IBMSNAP_CAPPARMS table, by the startup option, or by the use of the CHGPARMS command) that was employed by the user to set the value of the parameter.

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

ASN0522I

The program received a command to be processed.

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

ASN0523I

In response to the CHGPARMS command, one of these messages will be issued for each of the program parameters that was changed. For each parameter, the message provides the new value for the parameter.

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

ASN0524E

The program or a command program was invoked without one of the required parameters specified. If the parameter missing is the capture_server or control_server, the program or command also tried accessing the database name implicitly through the DB2DBDFT environment variable setting, where applicable, and this also was not successful.

Correct the invocation to include the appropriate parameter and its corresponding input value.

ASN0525E

The program or a command program was unable to initialize its read capability from the external communications message queue needed to process commands.

Retry the failing command, and if the problem persists, contact IBM Software Support.

ASN0526E

The command program was invoked without a command to process. No command processing is performed.

Resubmit the command with all the required input.

ASN0527E

The commands program was invoked with the CHGPARMS command but without any command input to process. No command processing is performed.

Resubmit the command with all the required input.

ASN0528E

The Capture or the Apply program tried to execute an SQL operation against a required Capture control table. The program received a not found return code from DB2. The return code occurs either if the migration has not been completed or if a required Capture control table has been accidentally dropped from the environment.

See the message text for the name of the missing control table. Corrective action for this problem depends on which table is missing. For example, if the table is IBMSNAP_PRUNE_LOCK, then the table can simply be re-created, and the Capture program can be restarted. However, if the table is IBMSNAP_RESTART, and if the correct table contents cannot be restored, then the table needs to be re-created, and the Capture program requires a cold start.

ASN0529I

The program started, and the program parameters were initialized based on the combination of startup options that are specified and the existing contents of the parameters table. The parameters were set by one of the methods: by default, by changing the parameters table, or by the startup option.

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

ASN0530E

An error occurred when the program issued one of the following functions:

• A CONNECT function to DB2 for VSE and VM
• A CONNECT function to DB2 Call Attachment Facility (CAF)
• An implicit connect to DB2

See the DB2 codes in the messages and codes publication of the database manager on your operating system for the appropriate reason code.

For DB2 for z/OS errors, see the section in the administration guide that describes the Call Attachment Facility. Contact your DBA for questions and diagnosis.

If you are running the program under DB2 for Linux or UNIX, ensure that the LIBPATH environment variable is set to the same environment in which the program starts.

ASN0531E

An error occurred when the program tried to open the plan, ASNLPLAN.

See the DB2 Codes section in the messages and codes publication of the database manager on your operating system to find the appropriate reason code. See the section in the administration guide that describes the Call Attachment Facility.

ASN0532E

The program does not support this release of DB2.

Run the program with the appropriate release of DB2.

ASN0533E

The database manager was terminated while the program was still active.

For z/OS, VSE/ESA, or VM/ESA, the database manager was terminated while the program was active and the user did not specify the NOTERM invocation parameter.

Start the database manager and start the program.

ASN0534E

The database was terminated while the program was still active. The database is in one of the following states: UNDETERMINED, TERMINATED, QUIESCED, ROLLFORWARD, or ACTIVE.

Start the database, and then start the program.

ASN0535E

While terminating the connection to DB2, the program received an error code from the Call Attachment Facility (CAF).

Restart the program.

ASN0536E

The SQLEGINS API of DB2 returned an error.

See the DB2 API Reference for information about the SQLEGINS API to determine the error, or contact IBM Software Support.

ASN0537E

An error occurred when the program issued one of the following functions:

• A CONNECT function to DB2 for VSE and VM
• A CONNECT function to DB2 Call Attachment Facility (CAF)
• An implicit connect to DB2

See the DB2 codes in the messages and codes publication of the database manager on your operating system for the appropriate reason code.

For DB2 for z/OS errors, see the section in the administration guide that describes the Call Attachment Facility. Contact your DBA for questions and diagnosis.

If you are running the program under DB2 for Linux or UNIX, ensure that the LIBPATH environment variable is set to the same environment in which the program starts.

ASN0538I

When the program is initially started, if the database manager is stopped the program waits until the database manager starts. After the database manager starts, the Capture program makes the connection and begins to capture changes.

If the TERM=N option is specified in the Capture invocation parameters and the database manager stops smoothly, the Capture program waits for the database manager to start.

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

ASN0539E

The Capture program tried to start but the source database was not configured properly for Capture to use the log read interface.

Take the following steps:

1. Review the settings for the logarchmeth1 and logarchmeth2 database configuration parameters. If both parameters are set to OFF, enable recoverable logging by setting the logarchmeth1 or logarchmeth2 database configuration parameter to a value other than OFF.
2. Use the backup command to back up the database before using it with any application.

ASN0540E

The program discovered that a bind or rebind is required in order to run. The program attempted to autobind, and the autobind was unsuccessful. The program failed to initialize.

Check for corresponding database messages that might provide additional details about the source of the autobind failure. Possible problems include authorization failures, missing or incorrect control tables, or bind files that do not match the program. Correct the situation, and restart the program.

ASN0541E

This message is issued during initialization of the Capture program if the validation of the IBMSNAP_CAPPARMS table found that one of the parameter value settings is not valid. The Capture program terminates with this error.

Check the documentation for permitted parameter values allowed in this table. Correct the values and restart the Capture program.

ASN0542E

The program has internally retried a time-out or deadlock condition multiple times. If the program task that receives the persistent lock condition is critical, such as a worker thread, the whole program terminates. If the program task is not critical, such as pruning or monitoring, then the task will be retried at a later time, and the program remains active. Capture retries 10 times; Apply retries 100 times.

Check for corresponding database messages that might provide additional detail about the source of the locking contention. Correct the situation if the error is a user error, such as a user held lock. If the condition persists, contact IBM Software Support for assistance.

ASN0543E

The program is unable to obtain memory for a necessary in-memory storage structure.

Consider allocating more memory to the program, then restart the program.

ASN0544E

An attempt was made to start more than one Capture program per DB2 subsystem or database.

ASN0545E

The program cannot find the password file. The user specifies the password filename through the PWDFILE parameter. If the user specifies a path startup parameter, the password file should reside in the specified directory. If the user did not specify a path startup parameter, the password file should reside in the current directory in which the program is running.

Ensure that the password file name is correctly specified and is located in the proper directory.

ASN0546W

The Capture or Apply program cannot connect to, disconnect from, or receive a ready status indication from the Automatic Restart Manager (ARM). The message displays the unsuccessful call and the return or reason code that returned to the program from the ARM. The program does not terminate but cannot continue ARM processing.

Check the Automatic Restart Manager documentation for more information about the cause of this failure.

ASN0547I

The program code and the program message file do not match; the release level of the program and the message file catalog might not match.

Verify that the program message file is correctly installed with the appropriate file permission settings.

ASN0548I

This informational message indicates that a stop command was issued to the program.

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

ASN0552E

A nonzero SQLCODE returned when the Capture, Apply, or Monitor program issued an EXEC SQL statement or CLI call. This SQLCODE might be caused by a DB2 problem that needs to be investigated, such as, an out of space condition, or the database manager is unavailable for use by applications. This message is sometimes followed by a second message that provides information about what replication was doing when this SQLCODE was encountered.

See the messages and codes documentation of the database manager on your operating system for an explanation of this SQLCODE and for information about corrective actions that might need to be taken in DB2. If replication issued another message immediately following this one, see the explanation and user response for that message.

ASN0553W

Themsg_number is the message that the program was trying to issue. The num_tokens is the number of substitution tokens given for the message (not including the pgmname and program_qualifier tokens). The sub_tokens is the substitution tokens for the message in error separated by commas.

Take any corrective action possible based on the error code given. For example, if the message file was not found or could not be accessed, you should also see message ASN0513 which gives you the file name. Verify that the message file exists with the correct permissions. If you get error code 4, you might have an old message file.

ASN0554E

The program tried to process an insert or update which was denied by DB2 because the DB2 transaction log is full. The program will stop processing.

Check the amount of space remaining on the file system that contains your database files. Consider increasing the maximum log size in the database configuration file.

ASN0555W

The Capture, Apply or Monitor program cannot register to use Automatic Resource Manager services because the program libraries are not APF authorized.

If you desire Capture, Apply, or Monitor program to register with Automatic Resource manager, authorize the program libraries for APF and restart the program.

ASN0556E

The Capture program tried to initialize a registration and found that the CD table does not have any columns that match the source table. Nothing can be captured for this registration, and therefore it is considered not valid. The registration remains inactive if the STOP_ON_ERROR column in the register (IBMSNAP_REGISTER) table for this registration is set to N, otherwise, the Capture program stops.

Make sure that there is at least one column in the CD table that matches the source table for the registration.

ASN0557E

The Capture program tried to initialize a registration and found a value that is not valid for a column in the IBMSNAP_REGISTER table.

Correct the value for the column in error.

ASN0558E

The program parameters table was not defined correctly or was updated with rows that are not valid.

Ensure that there is only one row in the parameter table corresponding to the program_qualifier. Ensure that the parameters table has a unique index on the program qualifier.

ASN0559W

For z/OS only. The job was started with a CPU time limit of xx seconds. The program will terminate when the time limit expires.

To run the program continuously, cancel the current job. Resubmit the job specifying NOLIMIT or 1440 as the new job limit.

ASN0560E

The program is unable to create the database object in the database.The database object is being created in the same object table space as the server control tables.

Review the SQL error code that is related to this error message and take the appropriate action.

ASN0561W

For Linux, UNIX, Windows, and iSeries: The Capture program's application code page is different from the code page of the source database. Unless the two code pages are compatible, this difference can result in corrupted data or unexpected errors when the Capture program inserts data into CD tables.

If the code pages are compatible, no action is required. If the code pages are incompatible, stop the Capture program, change the Capture program's application code page to the code page of the database, and restart the Capture program.

ASN0562E

ASN0563W

The program was started with both parameters specified in the command or in the parameters table. These parameters are not compatible. One parameter was ignored when the program started and continued to run.

The next time you start the program, specify only the parameter that you want the program to use.

ASN0564I

The Capture, Apply, or Monitor control table is defined on a Version 8 new-function mode DB2 subsystem. The control table includes columns that do not support long schema, owner, and table names. The program attempted to convert the control table to support long schema, owner, and table names and the operation was unsuccessful. The replication program continues to run.

ASN0565E

The program maintains statistics about its activities, but it could not save this data in the table due to an unexpected SQL code. The program will attempt to insert the data again at the next interval.

Refer to the details for the given sqlcode.

ASN0566E

Pruning failed with an unexpected SQL error code. This error does not cause the program to terminate. The program will try to prune the table again at the next pruning interval or when the program is restarted.

If this SQL return code indicates a temporary error, then no action is required. Otherwise, take action as indicated for the SQL error in IBM Knowledge Center.

ASN0567I

See message text.

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

ASN0568W

Incompatible versions of ICU (International Components for Unicode) were encountered. The ICU function is the ICU API name. The return code was returned by this API. The details about the ICU operation are provided by the Q Capture program.

Ensure you have the correct version of ICU and try restarting the program.

ASN0569E

An unexpected error occurred in the program.

See "Collecting data for InfoSphere Replication Server and InfoSphere Data Event Publisher" for information on how you can assist in troubleshooting this problem.

ASN0571E

The program parameter table must have exactly one row.

Use the sample migration scripts in the sqllib/samples/repl directory for the DDL statements to redefine the content of the parameter table so that it contains exactly one row.

ASN0572I

See message text.

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

ASN0573I

The Capture or Q Capture program stopped for the stated reason.

If the reason was program error, look for other messages that might explain why the program stopped.

ASN0574E

The program cannot connect to the WebSphere MQ queue manager. This error causes the program to terminate.

Start the queue manager if it is not running, for example by using the strmqm command.

ASN0575E

A nonzero WebSphere MQ reason code was returned when the program issued an WebSphere MQ command. The reason code indicates that there is a WebSphere MQ problem (for example, storage is not available for WebSphere MQ objects) or that WebSphere MQ is not available.

The ERROR_ACTION value determines how the program behaves due to this error. The value for the Q Capture program is stored in the IBMQREP_SENDQUEUES table. The value for the Q Apply program is stored in the IBMQREP_TARGETS table.

See the reason code documentation in the WebSphere MQ Application Programming Reference for an explanation of this WebSphere MQ reason code and for information about actions that you might need to take. The following list provides information about possible actions that are specific to Q Replication.

2003 (X'07D3') MQRC_BACKED_OUT (Linux, UNIX, Windows)

If Q Capture receives this reason code, it might indicate that the size of your queue manager log is not large enough to handle the workload that Q Capture generates, especially if large transactions are being replicated. The queue manager log is used for recovery; the queue manager also has an error log. To determine if queue manager log size is a problem, check the queue manager error log for messages that indicate that the queue manager log became full (for example, message AMQ7469). By default, the queue manager error log is in a directory that has the following path: MQ_install_directory/queue_manager_name/errors. The error log files have names like AMQERR01.LOG. You can increase the size of the queue manager log by increasing the values of the following three queue manager properties: LogPrimaryFiles, LogSecondaryFiles, LogFilePages. For example, you might want to make sure that these properties are no smaller than the following:

• LogPrimaryFiles: 15
• LogSecondaryFiles: 10
• LogFilePages: 1024

ASN0576E

Either the queue does not exist or it is specified incorrectly in the control tables. The program terminated as a result of this error.

Ensure that the queue name is specified correctly in the control tables and that it is accessible to application programs. Create the queue if it does not exist.

ASN0580E

The program terminated because it cannot run without a license.

Install the program license or contact your IBM representative.

ASN0581W

With RRS/AF, you must first issue an Identify request. The request failed because the RRS service in z/OS was not started.

No action is required because the program will run correctly with CAF. However, if you want the program to use RRS/AF, you must first make sure RRS is started, and then restart the program.

ASN0582I

An operator command has suspended the program, and the program has entered a wait state.

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

ASN0583I

An operator command has resumed the program from a suspended state, and the program has continued running.

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

ASN0584E

An error occurred when trying to dynamically load a WebSphere MQ library.

If the environment variable ASNUSEMQCLIENT is set to TRUE, the WebSphere MQ client libraries are used; otherwise the WebSphere MQ server libraries are used. The server libraries are also used if the environment variable ASNUSEMQCLIENT is not set. If the server configuration is used, then ensure that the WebSphere MQ server is running on the local host. If the client configuration is used, then make sure that this host can communicate with the remote host that the server is running on.

If you did not install WebSphere MQ in the default location, ensure that the library path variable (for example LIBPATH on AIX, LD_LIBRARY_PATH on SUN OS, SHLIB_PATH on HPUX, and PATH on Windows) points to the correct installed path. If you have multiple versions of WebSphere MQ, make sure the variable points to the correct version.

ASN0585I

The dynamic loading of the WebSphere MQ library was successful

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

ASN0586E

An error occurred while retrieving the function address for the specified WebSphere MQ API command.

This error is likely to occur if there are differences in the API signatures for WebSphere MQ. Please check that you are using the correct versions of the WebSphere MQ server or client and its libraries. If the environment variable ASNUSEMQCLIENT is set to TRUE, the client libraries are used, otherwise the server libraries are used. The WebSphere MQ server libraries are also used if the environment variable ASNUSEMQCLIENT is not set. If the server configuration is used, then ensure that the WebSphere MQ server is running on the local host. If the client configuration is used, then make sure that this host can communicate with the remote host that the server is running on.

If you did not install WebSphere MQ in the default location, ensure that the library path variable (for example LIBPATH on AIX, LD_LIBRARY_PATH on SUN OS, SHLIB_PATH on HPUX, and PATH on Windows) points to the correct installed path. If you have multiple versions of WebSphere MQ, make sure the variable points to the correct version.

ASN0587I

The WebSphere MQ queue manager is not currently available, The thread is retrying to connect.

Restart the WebSphere MQ queue manager if it was not active.

ASN0588I

This message is issued when the program is initializing if the program cannot connect to the server with its control tables. The program shuts down.

Check for database messages that might explain why the program was unable to establish a database connection. Contact the database administrator for questions and diagnosis.

ASN0589I

The program received the stated return code from one of its routines. The return code and routine information might help IBM determine the cause of an error.

This message is for your information. This message is typically preceded by error messages, which you can view in the program's log file.

ASN0590I

The program received this return code when it stopped one of its threads. The following thread exit return codes are the most common:

0

Thread stopped successfully. There is no reason code.

n

The Apply program encountered n failed cycles.

2001

Thread was stopped by either a stop command or signal.

2009

Thread was stopped by the recovery manager.

2010

Thread was stopped by recursive calls to the recovery manager.

2011

Thread stopped itself without an error.

2012

Thread stopped because of an error.

This message is for your information. If this message is displayed with error messages, look in the program's log file that contains the messages.

ASN0591I

The thread received this signal before the thread shut down. The ACTION parameter value is either handled or not handled. The thread recovery function handles signals that it expects and does not handle signals that it does not expect. The HoldLThread normally receives a SIGUSR2 signal before the initial thread shuts the HoldLThread down. Other replication threads receive a SIGUSR1 signal if they are terminated by the initial thread.

This message is for your information. If this message is displayed with error messages, look in the program's log file that contains the messages.

ASN0592I

The program attached to an IPC command message queue. Replication command programs use message queues to communicate with the programs that they operate.

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

ASN0593I

The program detached from an IPC command message queue. Replication command programs use message queues to communicate with the programs that they operate.

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

ASN0594I

The program created an IPC command message queue. Replication command programs use message queues to communicate with the programs that they operate.

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

ASN0595I

The program removed an IPC command message queue while the program was initializing or terminating. Replication command programs use message queues to communicate with the programs that they operate. Every time the program starts, the replication program creates a new message queue. If the message queue exists, it removes it and creates a new one. Every time the replication program shuts down, it tries to remove the message queue.

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

ASN0596I

The program is not able to create its IPC command message queue. Replication command programs use message queues to communicate with the programs that they operate. Every time the program starts, the replication program tries to create a new message queue. If the message queue exists, it tries to remove it and create a new one.

If the reason is "Shared memory ID already exists with the given resource ID", perform the following steps to remove the file and its associated message queue manually:

1. Note the key values. The key values will look similar to these:

   (0x300667f7, 0x310667f7, 0x320667f7) 

2. Log into the server using the user ID that was used to start the replication program.
3. Enter the following command for each of the keys in the ASN0594I message:

   ipcs grep | 0x300667f7 

   If a key is located, note its IPC resource type, ID, and owner. The IPC resource type (m, q, or s) will be in the first column of the IPCS output on UNIX and z/OS servers. The IPC resource type will be identified by a header line on LINUX servers.

4. If the keys are not located, log into the server using the superuser ID and enter the IPCS command in step 3 for each of the keys.
5. Log into the server using the user ID that owns the IPC resources that was located in the steps above. If the key identifies a shared memory segment, enter the following command to remove the shared memory segment:

   ipcrm -m ID 

   If the key identifies a semaphore, enter the following command to remove the semaphore:

   ipcrm -s ID 

   If the key identifies a message queue, enter the following command to remove the message queue:

   ipcrm -q ID 

6. Log into the server using the user ID that owns the file specified by the PATHNAME parameter value. Enter a command to remove the file, as in this example:

   rm /tmp/dpropr5.SRCDB.TIMING03.APP.IPC 

ASN0597I

The program is not able to attach to a replication IPC command message queue. Replication command programs use message queues to communicate with the programs that they operate. The program that owned the message queue might not be running.

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

ASN0598W

The database manager has indicated that the server database and client application are using code pages for different language types and any characters outside the seven-bit ASCII range cannot be guaranteed (SQLCODE +863).

Verify that you have configured the operating system and database managers correctly for the code pages that are being used.

ASN0599E

The replication program is at a different product level than the control tables for the given program identifier. The program determines this by checking the architecture level that is set in the ARCH_LEVEL column of the IBMQREP_APPLYPARMS table, IBMQREP_CAPPARMS table, or IBMSNAP_APPLEVEL table.

Verify that you specified the correct database alias when you started the program. If the replication control tables are older than the program, migrate the tables to the same product level as the program.

ASN0600I

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

ASN0601I

The program is not able to send a message to a replication IPC command message queue. Replication command programs use message queues to communicate with the programs that they operate. The program that owned the message queue may no longer be running.

This message is issued as a follow-on message to error message ASN0508E and contains the error code that provides additional diagnostic information.

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

ASN0602I

The program is not able to read a message from its IPC command message queue. Replication command programs use message queues to communicate with the programs that they operate. The program that owned the message queue may no longer be running.

This message is issued as a follow-on message to error message ASN0508E and contains the error code that provides additional diagnostic information.

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

ASN0603E

Install a license for WebSphere Replication Server.

ASN0604E

Install a license for WebSphere Event Publisher and restart Q Capture before activating any publications.

ASN0605E

Install a license for WebSphere Event Publisher to have Q Capture process publications. Install a license for WebSphere Replication Server to have Q Capture process Q subscriptions.

ASN0606I

This message appears after a successful start of the replication program.

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

ASN0607E

The program encountered an error while loading the replication library.

Verify that the library exists in the specified path.

ASN0608I

This message appears after invoking the asnlevel program.

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

ASN0609W

The Q Capture program found a license for replication, but did not find a license for event publishing. The Q Capture program does not terminate because no active publications were found. Q Capture will not be able to activate new publications.

If you plan to create and activate publications, install a license for WebSphere Event Publisher. Otherwise, no action is required.

ASN0610W

The Q Capture program found a license for event publishing, but did not find a license for replication. The Q Capture program does not terminate because no active Q subscriptions were found. Q Capture will not be able to activate new Q subscriptions.

If you plan to create and activate Q subscriptions, install a license for WebSphere Replication Server.

ASN0612E

Install a license for WebSphere Event Publisher.

ASN0613E

The Q Capture program does not activate a Q subscription unless it finds a license for replication. The Q Capture program does not terminate. This situation can happen for one of the following reasons:

• A replication license was never installed.
• The program was migrated from Version 8 to Version 9 or Version 10 and a Version 9 or Version 10 replication license was not installed.
• A try-and-buy license expired.

Install a license for InfoSphere Data Replication.

ASN0614E

The Q Apply program terminated because a valid license was not found. This situation can happen for one of the following reasons:

• The license was never installed.
• The program was migrated from Version 8 to Version 9 or Version 10 and a Version 9 or Version 10 license was not installed.
• A try-and-buy license expired.

Install a license for InfoSphere Data Replication.

ASN0615E

Make sure that the libraries exist and are specified in STEPLIB on the z/OS operating system or the library path environment variable specific to your Linux, UNIX, or Windows system.

ASN0616W

The program tried to load the dynamic link libraries (DLLs) that are listed but received the operating system error that is listed.

Correct the operating system error and start the program.

ASN0617E

Remove the listed DLL from the STEPLIB so that the program can try a DLL with a different version.

ASN0618W

If neither UCS nor ICU can be used for conversion, take the necessary steps to enable either UCS or ICU for the listed CCSIDs.

ASN0619W

Take the necessary steps to enable either UCS or ICU for the listed CCSIDs.

ASN0620E

The replication capture program received an error from the database log read API while getting a log record for the table.

Use the reason code to determine the database log read error. Look for messages that were issued by the database, and look for subsequent capture messages that may give you more information about the error.

ASN0621E

Replication supports tables with EDITPROC definitions. The database log read API invokes the EDITPROC to decode the row contents before returning them to the replication capture program. The API could not use the EDITPROC to decode the row contents. Depending on the error action option specified, capture may stop or deactivate the subscription or registration.

Determine why the log read API could not use the EDITPROC to decode the row contents. Look for messages from the database that may give you more information about the error.

ASN0622E

Look for database-issued messages on the system console that may give you more information about the error.

ASN0623E

This message is for your information only.

ASN0624E

This message is for your information only.

ASN0625W

Check later messages to determine if a subsequent error condition occurred in replication. The information in these messages might help determine the cause of the error. Correct the problem as appropriate.

ASN0626E

During the target table loading process for Classic replication, the Q Apply program creates a temporary intermediate file on the target server to place data that it selects from the source table. The Q Apply program then reads from the file before inserting the data into the target. The user ID that runs the Q Apply program must have the authority to create this file.

Make sure the user ID that is running the Q Apply program has the authority to create the file and that there is enough disk space on the target server to create the file. Use the error information in the message to determine other reasons that the file could not be created.

ASN0627E

A required column is missing from a control table. This message only reports the first missing column; other columns might also be missing. The missing columns are likely to be columns that were added to the control tables for a new version, which indicates that the control tables need to be migrated.

If you installed a new version but did not migrate the control tables, run the necessary migration scripts and start the program.

ASN0628E

Ensure that the column option is specified correctly in the publication or Q subscription. Use the replication administration tools to perform the following steps:

1. Drop the Q subscription or publication and recreate it with a valid value for the column option.
2. Start the Q subscription or publication.

ASN0629E

The program found one or more columns in the source table that are defined with unsupported data types. Replication of the XML data type for Q Replication requires a COMPATIBITY value in the IBMQREP_CAPPARMS table of 0905 or higher.

Redefine the registration, Q subscription, or publication without the columns that contain unsupported data types. For source tables with the XML data type, ensure that the Q Capture program is at Version 9.5 or higher and that the COMPATIBILITY value is 0905 or higher.

ASN0631E

The Capture or Q Capture program tried to load the user-specified field procedure to decode data in the source column because the column is defined with this field procedure. An error occurred that prevented the program from calling the procedure.

Correct the error that is indicated by the system completion code and reason code and warm start Capture or Q Capture. The system completion code and reason code are explained in MVS System Codes.

ASN0632E

The user-specified field procedure detected an error while decoding data in the column. An error message from the field procedure might follow this message.

Correct the error that is indicated by the return and reason codes and warm start Capture or Q Capture. The meanings of the return and reason codes are defined by the field procedure.

ASN0633W

The program captured the start of the transaction but has not seen its commit or rollback log record for more than an hour. This might or might not be a problem.

If this is a long-running transaction, ignore this message. On z/OS, you can use the DSN1LOGP utility to format the contents of the recovery log and determine whether it is a long-running transaction.

ASN0634W

ASN0635I

ASN0636E

An error occurred when the program issued one of the following functions:

• A CONNECT to DB2 for VSE and VM
• A CONNECT to DB2 Call Attachment Facility (CAF)
• An implicit connect to DB2

See the DB2 codes in the messages and codes publication of the database manager on your operating system for the appropriate reason code. For DB2 for z/OS errors, see the section in the administration guide that describes the Call Attachment Facility.

ASN0637I

The Q Capture or Capture program was spilling an in-memory transaction to a file to relieve memory. Spilling was stopped because the file size reached the internal limit of 1 GB. Spilling might be resumed to a new file if memory is depleted again. No data is lost.

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

ASN0638W

When DB2_SKIPINSERTED=ON or DB2_SKIPDELETED=ON is set for the database manager instance, a select statement does not return rows that are inserted and deleted but not yet committed, even under the cursor stability isolation mode. The following results are possible:

• When you start a subscription that has a load phase, rows that are inserted or deleted might not be picked up by the EXPORT utility when the table is loaded at the target and might be missing from the replicated table at the target.
• The asntdiff utility might return inconsistent results.

Suspend any applications that insert into or delete from the source table until a CAPSTART signal for the table has been inserted into the IBMQREP_SIGNAL table. Also, suspend applications when you run the asntdiff utility.

ASN0639W

When DB2_SKIPINSERTED=ON or DB2_SKIPDELETED=ON is set for the database manager instance, a select statement does not return rows that are inserted and deleted but not yet committed, even under the cursor stability isolation mode. When you start a subscription that has a load phase, rows that are inserted or deleted might not be picked up by the EXPORT utility when the table is loaded at the target and might be missing from the replicated table at the target.

Suspend any applications that insert into or delete from the source table until the Q subscription for the table is started.

ASN0640I

The Q Capture program is running with the term invocation parameter set to N and Q Capture cannot connect to the WebSphere MQ queue manager. With term=N, Q Capture waits until it can either connect to the queue manager or is stopped by a stop command. After Q Capture connects to the queue manager, it continues capturing changes.

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

ASN0641E

The TERM=N parameter instructs the program to keep running when the database manager is not available and when the queue manager is not available.

This message was returned because either the database manager was not available or the queue manager was not available, but when the program temporarily stopped some threads to go into a waiting state, one or more of the threads did not stop gracefully. To avoid an inconsistent state, the entire program stopped.

Restart the program.

ASN0642E

The replication programs use the Q Capture compatibility parameter to determine the level of messages that are sent. The compatibility level that was found in the Q Capture control tables is not supported.

Change the compatibility level to a valid value and start the Q Capture program. For information about compatibilty, see "Coexistence support in Version 9.7 Q Replication and event publishing."

ASN0643E

A single percentage sign (%) was inserted into the IBMQREP_IGNTRAN table. Because this character is treated as a wildcard to represent any number of characters or none, inserting a single % into the table instructs Q Capture to ignore all transactions and is therefore invalid.

Update the IBMQREP_IGNTRAN table with a valid authorization token or plan name (z/OS) or authorization ID (Linux, UNIX, Windows). If the percentage sign is part of the data but is not being used as a wildcard character, use a backslash to escape the wildcard character (\\%). Then start the Q Capture or Capture program.

ASN0644W

On Linux, UNIX, or Windows, you can insert transaction identifiers into only the AUTHID (authorization ID) column of the IBMQREP_IGNTRAN table.

1. Specify a transaction identifier in the AUTHID column.
2. Reinitialize the Q Capture or Capture program.

ASN0646E

The replication program requires that the TZ environment variable be set to define the time zone and the offset from Coordinated Universal Time (CUT).

Define the TZ environment variable in one of the following locations:

• etc/profile
• The .profile file in the home directory of the user ID that executes the replication program
• A file that is specified by the LE _CEE_ENVFILE environment variable. The LE _CEE_ENVFILE environment variable enables a list of environment variables to be set from a specified file.

ASN0647E

Q Capture or Capture do not support capture of changes from this version of the database.

Upgrade to a supported version of the database.

ASN0648E

The Q Capture or Capture program looks for updates to the system catalog tables to detect ALTER TABLE ADD COLUMN and ALTER TABLE ALTER COLUMN SET DATA TYPE changes to tables. DATA CAPTURE CHANGES must be enabled for this system catalog table.

Enable DATA CAPTURE CHANGES for the system catalog table.

ASN0649I

A schema-level Q subscription was created that specifies that all tables with the same schema should be replicated. The program tried to create a Q subscription for the table, but an inactive Q subscription for the table already exists. The program will proceed to create the new Q subscription and overwrite the inactive Q subscription.

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

ASN0650I

When a table with a matching schema-level subscription is dropped, the Q subscription for the table is deleted.

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

ASN0651E

The capture program normally replicates changes to the structure of source table columns. However, the program could not find the table structure (schema) information in its version tables, and so it took no action and stopped.

1. REORG the source table.
2. Contact IBM Software Support.

ASN0652I

The program defined an AF_UNIX socket and is listening for NMI client connection requests.

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

ASN0653I

The program received an NMI TERM message and closed all NMI client connections.

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

ASN0661E

The job was canceled explicitly by the user or as a result of an unexpected event, such as an ABEND.

Investigate the cause and restart the program.

ASN0662I

The program detected that a replication source table was altered and the ADMIN_REVALIDATE_DB_OBJECTS procedure was run to revalidate the table.

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

ASN0663E

After a table is altered, the table might be moved to reorg pending state. The table must be revalidated if it is in reorg pending state before any INSERT, UPDATE, or DELETE operations may be performed. The ADMIN_REVALIDATE_DB_OBJECTS stored procedure performs this validation. The call to ADMIN_REVALIDATE_DB_OBJECTS failed and the table remains in reorg pending state.

Manually reorganize the table or ensure that the Q Capture or Capture program has EXECUTE privilege on the ADMIN_REVALIDATE_DB_OBJECTS procedure.

ASN0664W

The Q Capture or Capture program was started with the warntxsz parameter, which prompts the program to issue this warning message when transactions that are about to be replicated exceed a specified size. The size of a transaction has exceeded the warntxsz value. This might or might not be a problem.

If this is an unexpected transaction, you can stop the program and use the provided transaction ID with the ignore_transid or transid runtime parameter to skip the transaction upon restart.

ASN0665E

The program was started with the nmi_enable parameter to enable it to operate as an NMI server. The program must be APF-authorized in this situation.

APF-authorize the program load library and restart the program.

ASN0666E

The program ioctl() SECIGET command did not get the NMI client security identity values because of a system error. The NMI client connection request is denied because the replication NMI server is unable to authenticate the requester's authorization ID.

See the explanation of system error for the ioctl() C function to determine the cause of the error.

ASN0667E

The NMI client connection request is denied because the replication NMI server is unable to authenticate the requester's authorization ID.

Refer to the zOS Security Server RACROUTE Macro Reference (SA22-7692-13) for descriptions of the RACROUTE return and reason codes.

ASN0668I

A Q Capture QSTATUS command was issued to display the status for this send queue, including the number of Q subscriptions that use the send queue and are not inactive.

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

ASN0669I

A Q Apply QSTATUS command was issued to display the status for this receive queue.

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

ASN0670E

The qstatus command was used for a send queue that does not exist.

Check that the queue name or replication queue map name is correct and reissue the qstatus command.

ASN0671E

The qstatus command was used for a receive queue that does not exist.

Check that the queue name or replication queue map name is correct and reissue the qstatus command.

ASN0672E

The Q Capture or Capture program does not support the data type of the column, even though the data type is supported by the source database. This situation can occur when the Q Capture or Capture program is at a lower version level than the database (for example a Version 9.7 Q Capture program running on a DB2 10 for z/OS subsystem).

Remove the column from the table and from the Q subscription, publication, or registration, or upgrade the Capture or Q Capture program to the same level as the database that it works with.

ASN0673I

The Q Capture or Capture program was spilling an in-memory transaction to a file to relieve memory. Spilling was stopped because the file size reached the internal limit of 1 GB. Spilling might be resumed to a new file if memory is depleted again. No data is lost.

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

ASN0674I

When the program is running, it periodically checks for database connectivity. If the database is not available, the program continues running and waits until the database is available if the term=n option is specified in the invocation parameters of the program. After the database is available, the program connects and starts processing

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

ASN0675I

The program generated a seed and saved the seed value in the file. The program will generate a key from the seed and use the key to create an IPC queue.

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

ASN0676I

The program is not able to generate a seed. The program generates a key from the seed and uses the key to create an IPC queue. The program tried to generate the seed after the ftok() function returned a key for a message queue that already exists.

Remove the IPC file and its associated message queue manually by following the steps in, "Troubleshooting problems with IPC message queues."

ASN0677E

The program was started with the nmi_enable parameter so that it can operate as an NMI server. A valid NMI socket name must start with a forward slash character (/) and not be longer than 64 characters.

Correct the NMI socket name and restart the program.

ASN0678E

The term=y parameter causes the program to terminate when the database manager is unavailable.

Take one of the following actions:

• Start the DB2 for z/OS subsystem and then restart the program with term=y.
• Start the program with term=n. The program will start, and then will wait for the subsystem to become active before the program begins to replicate data.

ASN0679E

The term=y parameter causes the program to terminate when the database manager is unavailable. Because the DB2 for z/OS subsystem was started in restricted access mode, the program terminated.

Take one of the following actions:

• Start the DB2 for z/OS subsystem in full access mode and then restart the program with term=y.
• Start the program with term=n. The program will start, and will wait for the subsystem to run in full access mode before the program begins to replicate data.

ASN0685W

The program invoked the GetAddrinfo socket call to determine the IP address that is associated with the specified host name and port or service.

This message can be returned for two reasons:

• An incorrect host name was specified in the EIF_CONN1 and EIF_CONN2 columns in the IBMQREP_APPLYPARMS table
• The correct host name was specified in the IBMQREP_APPLYPARMS table, but TCP/IP was unable to resolve that host name to an IP address

Verify the following details:

• The EIF_CONN1 and EIF_CONN2 columns in the IBMQREP_APPLYPARMS table specify valid host names, IP addresses, service names, or ports
• TCP/IP is able to resolve the host name that is specified in the IBMQREP_APPLYPARMS table to an IP address

If changes were recently made to the name server or local host table, refresh the resolver.

ASN0686W

The program invoked the create socket call to create an endpoint for communication. The call failed for the specified reason.

Determine the meaning of the reason that was issued by z/OS UNIX System Services or z/OS Communications Server.

ASN0687W

The program invoked the SetSockOpt socket call to set socket options. The call failed for the specified reason.

Determine the meaning of the reason that was issued by z/OS UNIX System Services or z/OS Communications Server.

ASN0688W

The program invoked the SetSockOpt socket call to establish a connection with the server socket. The call failed for the specified reason.

Determine the meaning of the reason that was issued by z/OS UNIX System Services or z/OS Communications Server.

ASN0689W

The program invoked the SetSockOpt socket call to send data on the socket. The call failed for the specified reason.

Determine the meaning of the reason that was issued by z/OS UNIX System Services or z/OS Communications Server.

ASN0690E

The Q Capture or Capture program does not support capture from tables with the attribute ORGANIZE BY COLUMN. Only ORGANIZE BY ROW is supported.

Take one of the following actions:

• Convert the table to ORGANIZE BY ROW and activate the Q subscription, registration, or publication.
• Delete the Q subscription, registration, or publication.

ASN0691E

The Q Capture or Capture program could not decode log records for this table. The table structure (schema) as recorded in the IBMQREP_TABVERSION and IBMQREP_COLVERSION control tables is not consistent with the format of the log records.

Follow these steps:

1. Manually deactivate the registration or Q subscription if it is active to allow capture to progress past this point in the log.
2. Run the REORG TABLESPACE utility for the table space that contains this table.
3. Activate the registration or Q subscription.

ASN0692W

A wide row is one where the the maximum width of the row is wider than the page size of the table space that contains the table. When a row becomes wide, one or more of the variable-length character columns are converted to large object (LOB) data. The Q Capture or Capture program cannot replicate values that have been converted into a LOB, and will instead replace the values with an empty string.

To avoid data loss, move this table into a table space that has a larger page size than the maximum row width of this table.

ASN0693E

In a data-sharing environment, the instrumentation facility interface (IFI) might return log records out of order because the records have log record sequence numbers (LRSNs) beyond the end of scope for a buffer. On a subsequent IFI 306 READS request, the buffer might contain older log records from other data-sharing members. The capture program does not read these log records because they are out of sequence.

Take one of the following actions:

• Format the database logs by using DSN1LOGP and determine if any replicated tables have log records that fall within the LRSN range. Compare those tables and reload them if necessary.
• Look for a DB2 APAR that resolves the IFI issue and apply the APAR to your DB2 environment.

ASN0694I

A Q Capture QSTATUS command was issued to display the database name and table space name for the source table that is part of the specified Q subscription.

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

ASN0696E

These table attributes are required to capture data:

DB2

DATA CAPTURE CHANGES

Oracle

Supplemental logging

DB2

Alter the table and add DATA CAPTURE CHANGES.

Oracle

Alter the table and add supplemental logging for all columns.

ASN0697E

While communicating with the CDC target datastore, Q Capture encountered a communication error.

Verify that the target is accessible and check the CDC target engine logs for errors.

ASN0698E

During creation or decoding of a message an error condition was encountered.

Contact IBM support.

ASN0700E

The CDC target datastore sends heartbeat messages to notify the Q Capture program that it is running. The absence of a message indicates that the datastore is unavailable.

Investigate the reason that the target datastore is unavailable.

ASN0701E

The connection to the target datastore was refused. The following reason codes are valid:

1

The user ID or password was incorrect.

2

The mapping group is already known to the target but the program indicated that it is new.

Review the reason codes in the explanation, and take the appropriate action:

1

Correct the user ID or password that is used for connecting.

2

Remove the subscription at the target that corresponds to the mapping group at the source.

ASN0702E

The connection information to connect to the target datastore was not found for the specified mapping group. No connection can be established.

Correct the apply instance information for the mapping group.

ASN0718I

A nonzero WebSphere MQ reason code was returned when the program issued a WebSphere MQ command. The reason code indicates that there is a WebSphere MQ problem (for example, storage is not available for WebSphere MQ objects) or that WebSphere MQ is not available.

This message is for your information only.

ASN0719W

When you want the Q Capture or Capture program to ignore certain transactions, you can use the percentage sign (%) as a wildcard character to represent any number of characters or none. Using a wildcard in this manner allows you to ignore groups of authorization IDs, authorization tokens, or plan names. If you use only the wildcard in the AUTHID, AUTHTOKEN, or PLANNAME column of the IBMQREP_IGNTRAN table, Q Capture or Capture does not replicate any transactions.

If you do not want to ignore all transactions, update the IBMQREP_IGNTRAN table with a different authorization token or plan name (z/OS) or authorization ID (Linux, UNIX, Windows). If the percentage sign is part of the data but is not being used as a wildcard, use a backslash character to escape the percentage sign. After you update the IBMQREP_IGNTRAN table, reinitialize the Q Capture or Capture program.

ASN0720W

The Q Capture warnlogapi parameter sets a threshold for the number of milliseconds that the Q Capture program waits for the DB2 for z/OS instrumentation facility interface (IFI) to return log records before issuing a warning. The database log read call exceeded the threshold.

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

ASN0721W

The replication NMI server invoked the close socket call to shut down the socket that is associated with the socket descriptor and to free resources that are allocated to the socket. The call failed for the specified reason.

Determine the meaning of the reason that was issued by UNIX System Services for z/OS or by the z/OS Communications Server. Take any corrective action that is recommended.

ASN0722W

The program invoked the unlink socket call to remove the AF_UNIX socket file that was created at bind() time. The call failed for the specified reason.

Determine the meaning of the reason that was issued by z/OS UNIX System Services or by the z/OS Communications Server. You might need to delete the AF_UNIX socket file that was created by the replication program at bind() time.

ASN0723W

Migrating to DB2 for z/OS V11 compatibility mode alters the SYSIBM.SYSTABLES system table to add new columns. Capture is unable to decode SYSIBM.SYSTABLES log records that are written before the SYSIBM.SYSTABLES catalog tablespace, SYSTSTAB, is reorganized. Capture will skip the SYSIBM.SYSTABLES log records that it is unable to decode and continue running.

This message if for your information only. No response is required.

ASN0724W

Migrating to DB2 for z/OS V11 compatibility mode alters the SYSIBM.SYSTABLES system table to add new columns. Capture is unable to decode SYSIBM.SYSTABLES log records that are written before the SYSIBM.SYSTABLES SYSIBM.SYSTABLES catalog tablespace, SYSTSTAB, is reorganized. Capture will skip the SYSIBM.SYSTABLES log records that it is unable to decode and continue running.

This message if for your information only. No response is required.

ASN0725W

While reading the log for changes to be replicated, the Q Capture or Capture program detected one or more log records that were out of order (a lower LSN following a higher LSN). This situation can cause the program to not replicate changes that involve the out-of-sequence log records and potentially result in data loss at the target table.

If a comparison of the source and target tables shows differences that involve these log records, you might need to restart the Q Capture or Capture program from a point in the log that is previous to the problematic records. If no differences are detected, you can ignore this message.

ASN0726E

DB2 returned an error when the program called the instrumentation facility interface (IFI). The program stops in this situation.

Check the DB2MSTR log for any additional diagnostic information to identify the cause of the problem. Try to restart Q Capture or Capture after you have collected the necessary diagnostics and resolved any problems.

ASN0727I

In response to a FORCETRANS signal or command, the Q Capture or Capture program committed and processed the transaction that is identified by the transaction identifier (transid) that was provided with the FORCETRANS signal or command. This action resulted in the transaction being inserted into the change-data (CD) table (SQL Replication), or published to the queue (Q Replication).

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

ASN0728I

In response to a FORCETRANS signal or command, the Q Capture or Capture program aborted its processing of the transaction that is identified by the transaction identifier (transid) that was provided with the FORCETRANS signal or command. Because of this action, the transaction was discarded from capture memory and was not replicated or published.

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

ASN0729W

The Q Capture or Capture program received a FORCETRANS signal or command, but the transaction that is identified by the specified transid was not found among the transactions that are currently in memory. The program took no action.

Check that the transid is correct and reissue the FORCETRANS command or signal if required.

ASN0730I

The capture program read an SQL command from the IBMQREP_CAPCMD table and ran the command.

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

ASN0731I

An IGNORETRANS command was issued to the capture program, but the program did not recognize the format of the transaction identifer that was provided. The identifier should be a 10-byte or 12-byte value in the format xxxx:xxxx:xxxx:xxxx:xxxx or xxxx:xxxx:xxxx:xxxx:xxxx:xxxx.

Reissue the IGNORETRANS command with a valid value for the transaction identifier.

ASN0732I

The levels have the following meaning:

• possible_level: The maximum function level that can be set in this program.
• current_level: The current level of function that is used by this program. The highest level that you can set for current_level is the value of possible_level.
• control_tables_level: The current level of the control tables, as set when the ASNCLP MIGRATE command was run, or when the control table migration was last run.

Current maintenance identifies the APAR or PTF level at the last time the program was built.

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

ASN0733I

The program was started with the activate_level option, or a utility was run against the program with the activate_level option. The program successfully activated the given level.

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

ASN0734E

To run the program with the given value for current_level, the value of control_tables_level must be upgraded.

Migrate the control tables by using the sample migration scripts or the ASNCLP MIGRATE command.

ASN0735E

The program is running with the reported value for control_table_level, but a required column does not exist.

Add any missing control table columns by running and verifying the given migration scripts for this level of control tables.

ASN0736E

When the program starts this message is issued if a parameter value is invalid.

Check the message tokens or documentation for permitted parameter values in this table. Correct the values and restart the program.

ASN0737I

The capture log reader made an IFI READS for IFCID 306 F-call to request log records beyond the requested LSN. The IFI READS for IFCID 306 F-call returned the end-scope LSN to the capture program.

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

ASN0738I

The capture log reader made an IFI READS for IFCID 306 N-call to return the remaining log records that met the previous F-call criteria.

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

ASN0739W

The FORCETRANS signal is not valid and is replaced with the IGNORETRANS command.

Use the IGNORETRANS command to remove a transaction from capture memory.

ASN0740W

The capture program cannot remove a transaction from capture memory while it is backing out transaction changes. Capture will run the IGNORETRANS command after the changes are undone.

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

ASN0745E

The capture program is unable to recognize the version of the Db2 catalog table.

Contact IBM Software Support.

ASN0746W

You should specify the URID for each thread that is part of the global transaction if you need to run DSN1LOGP to format the contents of the recovery log for the global transaction.

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

ASN0749E

The number of parameters that you specified when you invoked the replication program exceeds the maximum that is allowed.

Refer to the Q and SQL Replication documentation on the appropriate number of invocation parameters.

ASN0777I

The Additional information shown in this message refers to an informational text message. The reason codes provide supplemental return code information related to this message text. If an informational code field is not applicable, it contains "*" (an asterisk).

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

ASN0888E

The EEE error condition shown in this message is the description of an EEE-specific error that occurred in the specified program with the specified qualifier (if displayed). The error codes provide supplemental information related to this message text. If an error code field is not applicable, it contains "*" (an asterisk).

Use the information from the EEE error condition and from the specified error codes to determine the cause of the error. Contact IBM Software Support if you cannot resolve the error.

ASN0999E

The Error condition shown in this message is the description of an error that occurred in the specified program with the specified qualifier (if displayed). The error codes provide supplemental information related to this message text. If an error code field is not applicable, it contains "*" (an asterisk).

Use the information from the Error condition and from the specified error codes to determine the cause of the error. Contact IBM Software Support if you cannot resolve the error.