ASN1000-1999

ASN1001E

An error occurred during the execution of an SQL statement.

Refer to your database message reference for an explanation of the SQL error code.

ASN1002E

The Apply program could not lock the table.

Refer to your database message reference.

ASN1003E

The Apply program attempted to connect to the database and received a failing return code. There are many possible reasons why the Apply program could not connect to the database. For example, the Apply program would receive a failing return code if the database was down or too many users were accessing it.

Look up the SQLCODE (from the Apply diagnostic log) in IBM Knowledge Center to determine why the connection failed.

ASN1006E

The content of the registration module (ASNAPR61) for replication is not as expected for this version of DB2. No further use of the product is possible until you provide the correct registration module.

Verify that the database manager was installed without errors. If errors occurred, correct them and try again.

If the database manager was installed without error and you are correctly accessing the feature-registration module (ASNAPR61), contact IBM Software Support for assistance.

ASN1008E

The subscription set is not defined correctly.

Make sure that the subscription set has at least one member in the ASN.IBMSNAP_SUBS_MEMBR table or one BEFORE_OR_AFTER SQL statement in the ASN.IBMSNAP_SUBS_STMTS table.

ASN1009E

There is no subscription set defined for Apply qualifier qualifier.

Define at least one subscription set for Apply qualifier qualifier.

ASN1010E

This is an SQL return code indicating that the audit trail table was not set up with the same structure as the IBMSNAP_APPLYTRAIL table.

Resolve the underlying error code.

ASN1011E

This is an SQL code indicating that the attributes of the target table must be compatible with the attributes of the source table.

Refer to the SOURCE_STRUCTURE column in the register table for the compatibility of the source and target attributes.

ASN1012E

This is an SQL return code indicating that the source table structure in the register table was not set up according to the SOURCE_STRUCTURE column in the register table.

Use a valid source table structure.

ASN1013E

The target table structure in the subscription-targets-member table was not valid.

Use a valid table structure.

ASN1014E

The CD table was not defined in the IBMSNAP_REGISTER table because either the Apply program did not find the change-data table name in IBMSNAP_REGISTER or the source table was not registered correctly.

Verify that the CD table is correctly defined in the IBMSNAP_REGISTER table.

ASN1015I

This message is for your information only.

Verify that the Capture program is running.

ASN1016I

While attempting to perform a full refresh, the Apply program encountered a DISABLE_REFRESH column in the register table which was set on.

Either turn off the DISABLE_REFRESH column or bypass the Apply program and perform a manual refresh.

ASN1017E

The Apply program could not find any columns in the IBMSNAP_SUBS_COLS table.

Redefine the subscription set and subscription-set members.

ASN1018I

This message is for your information only.

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

ASN1019E

The Apply program cannot find key column names in one of the columns that requires a unique index or primary key.

Redefine the subscription set and subscription-set members.

ASN1020E

The Apply program could not obtain the required (memory) storage.

Contact IBM Software Support.

ASN1021E

The Apply program cannot read the work file because of a system error.

See the explanation of system error for the C function to determine the cause of the error. On many operating systems, descriptions of ERRNO can be found in C header file named errno.h. Determine if the problem is caused by lack of space, and contact your system administrator to obtain what is needed.

ASN1022E

Either the user ID not have the proper access authority for one or all of the files, or insufficient space remains after the Apply program writes to the target file.

See the explanation of system error for the C function to determine the cause of the error. On many operating systems, descriptions of ERRNO can be found in C header file named errno.h. Determine whether the problem is caused by a lack of access authority or a lack of space, and contact your system administrator to obtain what is needed.

ASN1023E

The Apply program cannot open the work file because of a system error.

See the explanation of system error for the C function to determine the cause of the error. On many operating systems, descriptions of ERRNO can be found in C header file named errno.h.

ASN1024E

The Apply program cannot close the work file because of a system error.

See the explanation of system error for the C function to determine the cause of the error. On many operating systems, descriptions of ERRNO can be found in C header file named errno.h.

ASN1025I

This message is for your information only.

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

ASN1026I

An error occurred during the execution of bind.

Refer to your database message reference.

ASN1027E

Too many large object (BLOB, CLOB, or DBCLOB) columns are specified for a subscription set member. The maximum number of columns allowed is 10.

Remove the excess large object columns from the subscription set member.

ASN1028E

If you allow users to update columns in the source table that are part of the target key, (IS_KEY=Y in the IBMSNAP_SUBS_COLS table), you must specify that the Apply program use before-image values from the source table when it updates target key columns. Two steps are required:

• You must define the source registration to capture the before-image values of the columns that make up the target key.
• You must select the subscription-set member option for the Apply program to use before-image values for target key updates. Selecting this option adds before-image column information to the IBMSNAP_SUBS_COLS table.

Follow these steps:

1. Deactivate the subscription set.
2. In the Replication Center, open the Member Properties dialog for the subscription-set member.
3. On the Target-Table Index page, click the Let the Apply program use before-image values to update target-key columns check box.
4. Activate the subscription set.

ASN1029E

The user-specified SQL statement did not execute successfully.

Refer to the corresponding information in the IBMSNAP_APPLYTRAIL table and to the SQL manual of your database for detailed information.

ASN1031E

The SQL statement is an empty string.

Specify the SQL statement to be executed.

ASN1032E

The Apply program could not open the log file.

For more information on the return code, refer to the manual that describes troubleshooting for your particular operating system.

ASN1033E

The Apply program could not write to the log file.

For more information on the return code, refer to the manual that describes troubleshooting for your particular operating system.

ASN1034I

This message is issued at successful initialization of the Apply process.

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

ASN1035E

An error occurred during the execution of an SQL statement.

Refer to your database message reference for SQL.

ASN1036E

The value for the COL_TYPE column in the subscription columns table is not valid.

Change the value to A, B, C, D, F, L, or R.

ASN1038E

Column names or expressions for a copy statement must be specified.

Use the replication administration tools to redefine the subscription-set member to include the desired source-target column mappings or expressions.

ASN1039E

The Apply program plan could not be opened.

Refer to the Apply for z/OS Program Directory.

ASN1040E

Execution of a z/OS system operation failed.

Refer to your z/OS system library information.

ASN1041I

This message informs you that the Apply program started using the specified subsystem name.

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

ASN1042W

The number of parameters you specified when you invoked the Apply program exceeds the maximum allowed.

Refer to the Capture and Apply chapter for your operating system for information on the appropriate number of invocation parameters.

ASN1043E

Verification attempt failed.

Make sure that only one instance of the Apply program with the specified Apply qualifier is running under this user ID on this subsystem or database.

ASN1044I

The Apply program becomes inactive in the following scenarios:

• At the end of an active Apply cycle, the Apply program will sleep for an amount of time calculated according to the following formula:

   [SLEEP_MINUTES] - [time spent in the cycle] 

  For example, if SLEEP_MINUTES is set to '1' and the Apply cycle lasts 10 seconds, the Apply program will be inactive for 50 seconds at the end of the cycle.

• When the Apply program does not find any subscription data to process, the Apply program will automatically sleep for 5 minutes.

You can configure whether this message is returned when the Apply program becomes inactive by specifying the inamsg parameter with the asnapply command.

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

ASN1045I

This message informs you from which database the Apply program is running.

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

ASN1047I

There are too many columns specified for a member in the subscription.

The user must reduce the number of columns specified for the member in the subscription. The maximum number of columns supported is determined by the total length of all the column names. More columns can be specified if the length of the column names is shorter.

ASN1048E

An Apply cycle failed. In the message, text identifies the target_server, target_owner, target_table, stmt_number, and cntl_server.

Check the APPERRM fields in the audit trail table to determine why the Apply cycle failed.

ASN1049E

Execution of a system operation failed.

Refer to the system library information for your operating system.

ASN1050E

The operation field of a row fetched from the source table is not valid.

Contact IBM Software Support.

ASN1051W

The Apply program detected that the Capture program skipped logged changes or deleted rows from CD tables before the Apply program could copy the data. For example, the Capture program was cold started or retention limit pruning occurred.

Look for message ASN0100I to determine if the Capture program was started recently. If so, look for ASN0529I to determine if the value of the STARTMODE parameter was COLD. If so, the Apply program performs a full refresh of target tables unless full refresh has been disabled. If you find that the Capture program performed retention limit pruning of a CD table, the corresponding subscription may need a full refresh to synchronize the target table with the source.

ASN1052E

The Apply program cannot find the ASNLOAD program in the current directory.

Make sure that ASNLOAD is in the directory from which you are invoking the Apply program.

ASN1053E

The ASNLOAD exit routine detected an error and passed the error information back to the Apply program. The following values are valid return codes:

98

An unexpected error has occurred (The ASNLOAD exit routine has failed with an unexpected error. No processing will be performed.)

99

DB2 pwdfile keyword supplied - password file not found (The pwdfile parameter was passed, but no password file was found. This is an error, and no connections or other processing will be performed.)

100

The CONNECT statement in the exit routine specified a user ID and password that use values supplied in the encrypted Apply password file. The password file and a user ID and password combination for the database server were found, but the connection failed.

101

DB2 connect without a user/using phrase failed - no pwdfile found (A connection without a user/using phrase was made because no password file was provided. The connection failed.)

102

DB2 connect without a user/using phrase failed - pwdfile found, no entry (A connection without a user/using phrase was made, because no server entry was found in the pwdfile for the database server. The connection failed.)

103

DB2 connect with a user/using phrase failed - uid/pwd from asnload.ini used (A connection with a user/using phrase was made using values supplied in the asnload.ini file. This file and a userid/password combination for the database server were found, but the connection failed.)

104

DB2 connect without a user/using phrase failed - no asnload.ini found (A connection without a user/using phrase was made, because no asnload.ini file was found. The connection failed.)

105

DB2 connect without a user/using phrase failed - no uid/pwd found for server (A connection without a user/using phrase was made. The asnload.ini file was found, but no uid/pwd combination was provided. The connection failed.)

106

User specified LOADX_TYPE = 2, no user code provided (The value of LOADX_TYPE in the table ASN.IBMSNAP_SUBS_MEMBR was set by the user to the value of 2, indicating that the user was supplying custom code in the ASNLOAD exit routine. However this code was not found, and the ASNLOAD exit routine failed when the Apply program passed a LOADX_TYPE value of 2.)

107

DB2 import utility failed (The import utility failed to execute. The SQL code returned by the utility is passed as the reason code.)

108

DB2 export utility failed (The export utility failed to execute. The SQL code returned by the utility is passed as the reason code.)

109

DB2 load utility failed (The load utility failed to execute. The SQL code returned by the utility is passed as the reason code.)

110

DB2 load utility failed - invoked as crossload (The load utility failed to execute. The load utility was invoked with the load from cursor option. The SQL code returned by the utility is passed as the reason code.)

111

The LOADX_TYPE was set to an not valid value (The ASNLOAD exit routine was invoked with a LOADX_TYPE value that was set by the user. The LOADX_TYPE value is not valid for this environment, and the ASNLOAD exit routine failed.)

112

LOADX_TYPE 3 requires a nickname for select (The ASNLOAD exit routine failed. The ASNLOAD exit routine was invoked with a LOADX_TYPE value that was set by the user. The LOADX_TYPE value is not valid for this environment unless a nickname is created for the remote DB2 source table and stored in the ASN.IBMSNAP_SUBS_MEMBR table.)

113

LOADX_TYPE 4 is incompatible with target table (The ASNLOAD exit routine failed. The ASNLOAD exit routine was invoked with a LOADX_TYPE set by the user. The LOADX_TYPE value is not valid for this environment, because the target table cannot be serviced by the DB2 for Linux, UNIX, and Windows load utility.)

114

LOADX_TYPE 5 is incompatible with target table (The ASNLOAD exit routine failed . The ASNLOAD exit routine was invoked with a LOADX_TYPE set by the user. The LOADX_TYPE value is not valid for this environment, because the target table cannot be serviced by the DB2 import utility.)

115

The ASNDLCOPY exit routine has failed (The ASNLOAD exit routine called the ASNDLCOPY exit routine, because there were DATALINK columns for the subscription-set member. The ASNDLCOPY exit routine failed; therefore, the process that loads this subscription-set member also failed.)

Check the return code and the corresponding explanation. Check for additional information in the ASNLOAD message file and in the message files generated by the DB2 utility, if applicable.

ASN1054E

The source table registration is incorrect or incomplete.

Drop and redefine the registration.

ASN1055E

The source table registration is incorrect.

Drop the subscription and redo it.

ASN1056E

The Apply program could not find the password and user ID to connect to the server.

Make sure that the Apply program password file exists. The Apply program password file resides in the same directory from which you start the Apply program. If you are using DB2 Satellite Edition, make sure that the password and user ID are defined on the client systems.

ASN1057E

The Apply program found no password.

If you want to use the AUTHENTICATION=SERVER scheme, you must provide a password, as described in the Apply program section in the Capture and Apply chapter for your operating system.

ASN1058E

The Apply program could not close the password file.

Contact IBM Software Support.

ASN1059E

The Apply program could not recognize a line in the password file.

Correct the syntax error in the password file.

ASN1060E

A system error was encountered during dynamic allocation.

Contact IBM Software Support.

ASN1061E

An invocation parameter that is not valid has been specified and has been ignored by the Apply program.

Correct the invocation parameter.

ASN1062W

The ASNLOAD exit routine cannot detect a user-specified LOADX_TYPE value, and no utilities are available to process this subscription-set member. Therefore, the ASNLOAD exit routine passes full refresh control back to the Apply program. The ASNLOAD exit routine does not currently support and is not able to process some target table types (such as the Sybase and MS SQL Server target tables).

This message is for your information only, and no action is required. However, you can set the value of the LOADX_TYPE to 1 for these subscription-set members in order to avoid unnecessary processing by the ASNLOAD exit routine.

ASN1063E

The number of subscriptions has exceeded the maximum allowed number of 200.

Remove excess members from the subscription set.

ASN1064W

The Apply program cannot attempt a full refresh for the subscription set, because the Capture program for this source has never been cold started and is not ready to process the CAPSTART signals are be inserted by the Apply program.

Start the Capture program for this source.

ASN1065E

The Apply program cannot process data for this subscription set, because at least one of the registrations has STATE='S' in the IBMSNAP_REGISTER table.

The Capture program stops a registration if there is a problem with the registration that requires your intervention. Refer to the STATE_INFO column in the IBMSNAP_REGISTER table for error information. The integrity of the captured data for the registration might be compromised, and the Apply program must perform a full-refresh. This problem might occur if the registered source table was altered with data capture none.

Fix the stopped registrations using the information from the error messages. Reactivate the registrations. When you reactivate the registrations, the Apply program performs a full refresh.

ASN1066E

An internal Apply program error occurred.

Contact IBM Software Support.

ASN1067E

More than one application updated the same row in a table from different locations. Some transactions have been rejected and compensated.

See the documentation for the IBMSNAP_UOW table for details.

ASN1068E

A constraint violation was detected when copying data from the source table to a target table. The Apply program has terminated and the subscription has been deactivated.

Correct the constraint error and reactivate the subscription.

ASN1070E

The Apply program could not lock the target tables before it was to check update conflicts.

Verify that all the target tables are available before restarting Apply.

ASN1071E

The Apply program has detected an error while reading the temporary work file.

Contact IBM Software Support.

ASN1072E

The Apply program could not find the user exit program, ASNDONE.

Verify that the ASNDONE program is located in the correct directory.

ASN1073E

An error occurred while calling the user exit program, ASNDONE.

Contact IBM Software Support.

ASN1074E

The Apply program did not find the ASNDLCOPY program in the current search path.

Add the ASNDLCOPY program to the search path and run the Apply program again.

ASN1075E

The ASNDLCOPY program detected an error and passed the error information back to the Apply program. The following values are valid return codes:

98

Unexpected error occurred.

99

The arguments passed to the ASNDLCOPY program are not valid.

100

Unable to allocate memory.

101

Unable to open the ASNDLSRVMAP configuration file.

102

The number of entries in the ASNDLSRVMAP configuration file exceeds the maximum limit.

103

An entry that is not valid has been found in the ASNDLSRVMAP configuration file.

104

No user login information was found in the ASNDLUSER configuration file for a given file server.

105

An entry that is not valid has been found in the ASNDLPARM configuration file.

106

Unable to open the ASNDLUSER configuration file.

107

An entry that is not valid has been found in the ASNDLUSER configuration file.

108

An I/O error occurred when reading from the input file.

109

An entry that is not valid has been found in the input file.

110

Unable to open the input file.

111

Unable to open the result file.

112

An I/O error occurred when writing to the result file.

113

An error occurred when initializing the control channel of the FTP protocol.

114

An error occurred when sending data through the control channel.

115

Unable to log on to the file server with the given user and password.

116

The copy daemon has not yet started.

117

An error occurred when initializing the data channel of the FTP protocol.

118

Unable to retrieve the file from the source file server.

119

Unable to store the file on the target file server.

120

An error occurred when transferring files in the passive mode.

121

Cannot find the path mapping for the given file reference.

122

An error occurred when executing the FTP BINARY command.

123

An error occurred when executing the FTP SIZE command.

124

An error occurred when executing the FTP MODTIME command.

125

An error occurred when executing the FTP SITE UMASK command.

126

An error occurred when executing the FTP SITE TOUCH command.

127

An error occurred when executing the FTP SITE CHMOD command.

Check the return code and its corresponding meaning. The return code is based on the sample ASNDLCOPY program that is shipped with the product. Additional information is provided in the log file.

ASN1076E

The result file that was generated by the ASNDLCOPY program is not in an expected format.

If you modified the ASNDLCOPY program, check that your changes are not causing the invalid format. If your changes are not the cause of the problem, check that your machine has enough space for the result file.

ASN1077E

The DATALINK column field of a row fetched from the source table is not valid.

Contact IBM Software Support.

ASN1078E

The ASNDLCOPY program terminated abnormally by the given signal.

Check the specified log file for the cause of the error. If you modified the ASNDLCOPY program and the signal is generated by the modified code, fix the code and rerun. Otherwise, contact IBM Software Support.

ASN1079E

There was an invalid update made to the MEMBER_STATE column in the IBMSNAP_SUBS_MEMBR table. Valid values for this column are: 'N', 'L', 'S', or 'D'.

Update the MEMBER_STATE column with a valid value and start the Apply program again. Refer to the IBMSNAP_SUBS_MEMBR table for details about the values in the MEMBER_STATE column.

ASN1080E

The Apply program's ASN.IBMSNAP_SUBS_COLS control table contains no information about the columns in the specified target table. Column information may have been manually removed during editing of the SQL script generated by the Replication Center or ASNCLP command-line program.

Drop and recreate the subscription. If you know of a reason that the subscription cannot be dropped, you need to insert column data manually into the ASN.IBMSNAP_SUBS_COLS table.

ASN1097I

The error reported previously caused the Apply program to stop.

Fix the error reported before this message.

ASN1207E

The selected subscription is inactive.

Either activate the subscription or select another one.

ASN1210E

You must specify an Apply qualifier following the keyword -q.

Specify an Apply qualifier following the keyword -q.

ASN1212E

A read-only set name was specified following the keyword U or D.

Specify only replica for the keywords U and D.

ASN1221I

This message is for your information only.

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

ASN1242E

This message is for your information only.

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

ASN1243E

Either a subscription set has not been selected or the apply qualifier is not valid.

Verify the subscription names and apply qualifier.

ASN1304E

The Capture program returned an error.

Determine the error from the Capture log file.

ASN1305E

The Apply program returned an error.

Determine the error from the Apply log file.

ASN1310E

An operating system error occurred while calling ASNCAP.

Make sure that the Capture program is in the execution path.

ASN1311E

An operating system error occurred while calling ASNAPPLY.

Make sure that the Apply program is in the execution path.

ASN1312E

The target server name was not specified, and the ASNSAT program could not determine the default database name from the DB2DBDFT variable.

Specify the target server name following the -t keyword.

ASN1314E

The user did not specify the Apply qualifier. The ASNSAT program encountered an error while retrieving the USER special register.

Specify the Apply qualifier following the -q keyword.

ASN1315E

An error occurred while attempting to connect to the target database.

Refer to your database message reference.

ASN1316E

An error occurred while attempting to auto bind.

Make sure that the bind file exists in the sqllib\bnd directory.

ASN1317E

An SQL error occurred while selecting from the register table.

Refer to your database message reference.

ASN1318E

An error occurred while retrieving the node type configuration parameter.

Refer to your database message reference.

ASN1319I

To ensure that the full refresh of the target table successfully selects all data from the source server, the Apply program must bind the SQL packages with this option. The option forces the SELECT operation to wait until all in-progress transactions that modify the source table are completed before beginning to retrieve the rows.

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

ASN1320W

The program encountered an error when it attempted to bind a required package for full refresh.

Interpret the SQLCODE of the failed bind call. If you need to ensure that no data is lost during a full refresh, fix the problem and then restart the Apply program. You can manually bind the required packages by connecting to the source database and running the following command:

 db2 bind @qapplycs.lst    CONCURRENTACCESSRESOLUTION WAIT_FOR_OUTCOME 

If you are only performing differential refresh, you can ignore this warning.

ASN1321I

The Apply program committed the indicated number of rows to the target table during the most recent commit of the full refresh. You can control the number of rows in each commit by using the nickname_commit_ct parameter.

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

ASN1322W

When MONITOR_ENABLED is set to Y, the Apply program inserts information about its status into the ASN.IBMSNAP_APPLYMON table. The table was not found and so no status information can be saved.

Take one of the following actions:

• Create the ASN.IBMSNAP_APPLYMON table on the Apply control server. You can use the following SQL statements:

   CREATE TABLE ASN.IBMSNAP_APPLYMON         (MONITOR_TIME TIMESTAMP NOT NULL, 	 APPLY_QUAL CHAR(18) NOT NULL, 	 WHOS_ON_FIRST CHAR(1), 	 STATE SMALLINT,          CURRENT_SET_NAME CHAR(18), 	 CURRENT_TABOWNER VARCHAR(128), 	 CURRENT_TABNAME VARCHAR(128) 	 ); 	  CREATE INDEX IXIBMSNAP_APPLYMON ON     ASN.IBMSNAP_APPLYMON(MONITOR_TIME,                          APPLY_QUAL,                          WHOS_ON_FIRST); 

  Restart the Apply program with MONITOR_ENABLED=Y after the table is created.

• Continue without Apply status information. Apply issues the warning message once and keeps processing subscriptions if the table does not exist. You can change the value of the MONITOR_ENABLED column in the ASN.IBMSNAP_APPPARMS table to N and Apply will use this value the next time it is restarted.

ASN1323E

When you migrate to SQL Replication Version 10 and set Capture compatibility to 10xx on the source server, you must set the value of the ARCH_LEVEL column in the ASN.IBMSNAP_SUBS_SET table to 1001. The variable xx identifies the release within Version 10.

Follow the steps in the SQL Replication Version 10 migration information to migrate the Apply control server, and then activate the subscription set.

ASN1324E

The Capture server is at Version 10, which requires the Apply program and Apply control server to also be at Version 10 to support new restart information and 16-byte columns for log sequence numbers.

Follow these steps:

• Upgrade the Apply program and Apply control server to Version 10 or above.
• Migrate the Apply control tables to Version 10.
• Reactivate the subscription set.

ASN1325E

When the Capture program is at Version 10, target CCD tables require 16-byte LSN columns (IBMSNAP_COMMITSEQ, IBMSNAP_INTENTSEQ) to hold log sequence number details from the Capture program.

Follow the steps in the SQL Replication Version 10 migration information to upgrade target CCD tables to 16-byte LSN columns and reactivate the subscription set.

ASN1326E

Because the Apply program is older than Version 10, it does not support 16-byte LSN columns. The source CCD table was upgraded to 16-byte LSN columns, and so the Apply program cannot work with this table

Upgrade the Apply program and Apply control server to Version 10 or above to support 16-byte LSN columns and reactivate the subscription set.

ASN1327E

When the ARCH_LEVEL value for a subscription set is 1001, the Capture compatibility value must be changed to 1001.

Run the Version 10 Capture migration and compatibility script, and reactivate the subscription set.

ASN1328E

The program parameter table must have exactly one row.

Follow these steps:

1. Make sure that the parameter table is in the right format and contains exactly one row. You can find the correct DDL for the table in the migration scripts in the sqllib/samples/repl/mig10 directory.
2. Reactivate the subscription set.

ASN1329E

When the compatibility value for the Capture program is 10xx, where xx identifies the release within Version 10, the ARCH_LEVEL value for a subscription set must be changed to 10xx. The higher ARCH_LEVEL value indicates that the Apply control tables are at the correct level to work with a Version 10 Capture program. Also, the ARCH_LEVEL in the ASN.IBMSNAP_SUBS_SET table must be updated to 1001 if the source server is on Linux, UNIX, or Windows, or to 1021 if the source server is on z/OS.

Run the Version 10 Apply migration script for your operating system and reactivate the subscription set. The script updates the control tables to the Version 10 level and updates the ARCH_LEVEL value.

ASN1330I

The source ARCH_LEVEL in the IBMSNAP_CAPPARMS table for this subscription set is 1021, while the ARCH_LEVEL in the ASN.IBMSNAP_SUBS_SET table is 08xx. The variable xx identifies the release within V8. Apply successfully migrated the subscription set to ARCH_LEVEL 1021 to match the Capture ARCH_LEVEL. The SYNCHPOINT of the subscription set is the value of SYNCHPOINT in the IBMSNAP_PRUNE_SET table on the Capture server.

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

ASN1331E

The source ARCH_LEVEL in the IBMSNAP_CAPPARMS table for this subscription is 1021, while the ARCH_LEVEL in the ASN.IBMSNAP_SUBS_SET table is 08xx. The variable xx identifies the release within V8. Apply tried to migrate the subscription set to ARCH_LEVEL 1021 to match the Capture ARCH_LEVEL but the migration failed.

Look for a previous message that indicates an error with the same subscription set and use the information in the message to correct the error. Start Apply if it stopped.

ASN1500I

Valid values for action name are Create Capture server control tables and Drop Capture server control tables.

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

ASN1501I

Valid values for action name are Create Capture server control tables and Drop Capture server control tables.

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

ASN1502I

Valid values for action name are Create Apply server control tables and Drop Apply server control tables.

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

ASN1503I

Valid values for action name are Create Registration, Drop Registration, Alter Registration, Add Registration, and Promote Registration.

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

ASN1504I

Valid values for action name are Create Registration and Drop Registration.

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

ASN1505I

Valid values for action name are Create Subscription Set, Drop Subscription Set, Alter Subscription Set, and Promote Subscription Set.

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

ASN1506I

Valid values for action name are Create Subscription Set, Drop Subscription Set, Alter Subscription Set, and Promote Subscription Set.

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

ASN1507I

Valid values for action name are Create Subscription Set, Drop Subscription Set, Alter Subscription Set, and Promote Subscription Set.

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

ASN1508I

Valid values for action name are Create Subscription Set, Drop Subscription Set, Alter Subscription Set, and Promote Subscription Set.

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

ASN1510I

Valid values for action name are Create Capture server control tables, Drop Capture server control tables, Create Apply control server control tables, and Drop Apply control server control tables.

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

ASN1511I

Valid values for action name are Create Registration, Drop Registration, Alter Registration, Add Registration Column, and Promote Registration.

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

ASN1512I

Valid values for action name are Create Subscription Set, Drop Subscription Set, Alter Subscription Set, Add Statements to Subscription Set, Drop Statements from Subscription Set, and Promote Subscription Set.

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

ASN1513I

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

ASN1514I

At least one of the tasks in the ASNCLP script failed. The number of errors depends partly on the following options that determine whether the ASNCLP continues to process commands after errors:

SET RUN SCRIPT NOW

• STOP ON SQL ERROR ON (default)
• STOP ON SQL ERROR OFF

SET RUN SCRIPT LATER

• GENERATE SQL FOR EXISTING NO (default)
• GENERATE SQL FOR EXISTING YES

The ASNCLP log file has messages for any tasks that fail. The messages are prefaced by an ASN error code. For more details about the task that prompted an error, look for an informational message for that task, for example Create Q Subscription - ASN2003I.

ASN1550E

The input parameter is mandatory for this action and is missing.

Provide the mandatory parameter and rerun the Replication action.

ASN1551E

The value provided for the input parameter is not a valid value. The following values are valid for the reason code:

0

Blocking minutes value should be between 0-999.

1

Commit Count value should be between 0-999.

2

Server Type value should be Capture Server.

3

Table type value should be one of the following types:

• USERTABLE
• CCD TABLE
• POINT IN TIME
• BASE AGGREGATE
• CHANGE AGGREGATE
• REPLICA
• USERCOPY

4

Remote Server Name value should be NULL.

5

Server Type value should be one of the following types:

• Capture Server
• Control Server
• Capture and Control Server
• Capture, Control and Target Server

6

Internal CCD tables must be noncomplete.

7

The Apply qualifier exceeds the maximum length of 18 characters.

8

The set name exceeds the maximum length of 18 characters.

9

Event names must be 128 bytes or fewer in length.

10

The source Capture schema name exceeds the maximum length of 128 bytes.

11

The target Capture schema name exceeds the maximum length of 128 bytes.

12

The BEFORE_OR_AFTER statement value must be 'A', 'B', or 'S'.

13

The EI_OR_CALL value must be 'C' or 'E'.

14

SQLSTATES must be 50 digits or fewer in length.

15

SQLSTATES must be numeric

16

The CONFLICT_LEVEL must be zero (0) or NONE.

17

The CHGONLY value must be 'N'.

18

The external CCD table is noncondensed and contains LOB columns.

19

The CONFLICT_LEVEL must be between 0 and 2.

20

The CHGONLY value must be 'Y' or 'N'.

21

The RECAPTURE value must be 'Y' or 'N'.

22

The DISABLE_REFRESH value must be 0 or 1.

23

The CHG_UPD_TO_DEL_INS value must be 'Y' or 'N'.

24

The STOP_ON_ERROR value must be 'Y' or 'N'.

25

The BEFORE_IMG_PREFIX value must be only one character.

26

The corresponding table space does not have the "New Tablespace" flag set to true in any of the previous scenarios.

27

The table name is not a valid control table.

28

A federated server was found but a corresponding federated schema name was not provided. When calling the API for a federated system, ensure that the federated schema name is provided.

29

The specified remote source database name on the OS/400 system does not match the remote source database name of the registration.

Provide a valid value for the input parameter, and rerun the replication action.

ASN1552E

The value provided for the replication parameter conflicts with another parameter specification.

Provide valid values for the input parameters and rerun the replication action.

ASN1553E

The value provided for the replication parameter conflicts with one of the values for the existing subscription set.

Provide a valid value for the input parameter or change the subscription set definition, and rerun the replication action.

ASN1560E

An error occurred during the execution of an SQL statement.

Refer to your database message reference for SQL.

ASN1561E

The connection to the specified server could not be established.

Refer to your database message reference for SQL. Verify that the userid and password information is correct.

ASN1562E

The specified action cannot be performed because of a run time error.

Contact IBM Software Support.

ASN1563E

The specified replication architecture level is not supported on the specified server operating system, version, or release.

Specify a supported replication architecture level in the ARCH_LEVEL column of the IBMSNAP_REGISTER table.

ASN1564E

The replication architecture level found in the IBMSNAP_REGISTER table for this Capture schema does not allow the specified replication action.

Migrate the Capture control tables to Version 8 architecture level before retrying this action.

ASN1565E

The replication architecture level found in the ASN.IBMSNAP_SUBS_SET table does not allow the specified replication action.

Migrate the Apply control tables to Version 8 architecture level before retrying the action.

ASN1567W

The DB2 stored procedure READTSCINFOS cannot be found on the Capture server or target server. The stored procedure is required to retrieve DB2 table space container information for that server.

Determine whether the stored procedure exists on the server: check if the file db2rtsc exists in the function directory of the sqllib directory. The file db2rtsc might not exist if the server is a pre-V8 server. If the stored procedure does not exist, then edit the table space container definition that is provided in the output script.

ASN1568E

The database object type provided in the second parameter allows a length that is smaller than the length of the actual object provided in the third parameter. As in the Properties file, the following values are valid for the object: Table, Index, Tablespace, Table owner, Nickname.

Refer to the SQL Reference for the appropriate database, and provide the correct name length.

ASN1569E

The database object cannot be created because there is already a database object of the same type with the same name. As in the properties file, the following values are valid for the object: Table, Index, Nickname, Tablespace, Table owner.

Provide a name for that object that does not already exist in DB2, and reissue the replication task.

ASN1570E

The database object does not exist in the DB2 catalog. This object must exist in order to be defined as a source or target of a subscription set, as per the replication action. This object might have been defined as part of an existing registration or subscription-set definition but is not found in the DB2 catalog. As in the properties file, the following values are valid for the object: Table, Index, Nickname, Tablespace, Table owner, View.

Provide a name that already exists in DB2, and reissue the replication task. If the object was defined as part of an existing registration or subscription-set definition, verify that the object exists in the DB2 catalog.

ASN1571E

Refer to the SQL reference for the appropriate database.

ASN1572E

The row size of a table cannot exceed the table space page size for that table. The table space page size is derived from the buffer pool page size to which it belongs. No script is generated.

You might have to create the table in a different table space. Refer to your DB2 platform documentation.

ASN1573E

The number of columns that a database object (table or index) can contain depends on the DB2 platform but cannot exceed a predefined number. No script is generated. The following values are valid for object type: table, index.

Redesign the DB2 object.

ASN1574E

The page size must be valid for the table space to be created successfully. The following values are valid for reason code:

0

Page size is not equal to the page size of the given buffer pool.

1

Page size is not equal to one of the following: 4K, 8K, 16K, 32K.

Refer to the DB2 SQL Reference for appropriate page size ranges or values.

ASN1575W

No table space name was specified indicating where to create the specified table, so the table will be created in the DB2 default table space. This might be a problem if the default table space specifications are not appropriate for the specified table.

Refer to the SQL Reference for the DB2 defaults. If you require the table to be in its own table space, then reissue the replication task with the appropriate specifications. No action is required if the default is appropriate for the table.

ASN1576W

A table space (for workstation operating systems) or an index space (for z/OS operating systems) was not provided into which the specified index might be created. Therefore, the index is created using the DB2 defaults. This might be a problem if the default specifications are not appropriate for the specified index.

Refer to the SQL Reference for the DB2 defaults. If you require the index to be in its own table space or index space, then reissue the replication task with the appropriate specifications. No action is required if the default is appropriate for the index.

ASN1577W

For z/OS operating systems only, a database was not provided into which the specified table space might be created. Therefore, the table space is created using the DB2 defaults. This might be a problem if the default specifications are not appropriate for the specified table space.

Refer to the SQL Reference for the DB2 defaults. If you require the table space to be in its own database, then reissue the replication task with the appropriate specifications. No action is required if the default is appropriate for the table space.

ASN1578I

For workstation and z/OS operating systems only, a storage group was not provided into which the specified table space might be created. Therefore, the table space is created using the DB2 defaults. This might be a problem if the default specifications are not appropriate for the specified table space.

Refer to the SQL Reference for the DB2 defaults. If you require the table space to be in its own storage group, then reissue the replication task with the appropriate specifications. No action is required if the default is appropriate for the table space.

ASN1579I

For workstation and z/OS operating systems only, a storage group was not specified into which the DB2 index might be created. Therefore, DB2 created the index using the default specification. This might be a problem if the default specifications are not appropriate for the specified index.

Refer to the SQL Reference for the DB2 defaults. If you require the index to be in its own storage group, then reissue the replication task with the appropriate specifications. No action is required if the default is appropriate for the index.

ASN1580I

For workstation and z/OS operating systems only, a buffer pool was not provided into which the specified table space might be created. Therefore, the table space is created using the DB2 defaults. This might be a problem if the default specifications are not appropriate for the specified table space.

Refer to the SQL Reference for the DB2 defaults. If you require the table space to be in its own buffer pool, then reissue the replication task with the appropriate specifications. No action is required if the default is appropriate for the table space.

ASN1581I

For workstation and z/OS operating systems only, a buffer pool was not provided into which the specified index might be created. Therefore, the index is created using the DB2 defaults. This might be a problem if the default specifications are not appropriate for the specified index.

Refer to the SQL Reference for the DB2 defaults. If you require the index to be in its own buffer pool, then reissue the replication task with the appropriate specifications. No action is required if the default is appropriate for the index.

ASN1582W

• For applications on a DB2 for z/OS database, the buffer pool is not active into which the table space might be created.
• For applications on a DB2 for Linux, UNIX, and Windows database, the buffer pool does not exist into which the specified table space might be created.

• For a DB2 for z/OS database, make sure the buffer pool is active at the time of running the script.
• For a DB2 for Linux, UNIX, and Window database, make sure that the buffer pool exists at the time of running the script.

ASN1583E

The given PageSize does not match the PageSize of the default buffer pool. The table space cannot be created.

Change the PageSize or choose another buffer pool.

ASN1584E

The Replication architecture level found in the captureschema.IBMSNAP_REGISTER does not allow the specified replication action.

Drop the control tables on the Capture control server manually because the architecture level is not supported. Create the control tables with a valid architecture level.

ASN1585E

The Replication architecture level found in the ASN.IBMSNAP_SUBS_SET does not allow the specified replication action.

Drop the control table on the Apply control server manually because the architecture level is not supported. Create the control tables with a valid architecture level.

ASN1586W

For z/OS operating systems only, a database was not provided into which the specified table might be created. Therefore, the table is created using the DB2 defaults. This might be a problem if the default specifications are not appropriate for the specified table.

Refer to the SQL Reference for the DB2 defaults. If you require the table space to be in its own database, then reissue the replication task with the appropriate specifications. No action is required if the default is appropriate for the table.

ASN1587E

The provided value is not valid or conflicts with another parameter value.

Refer to the SQL reference for valid values.

ASN1588E

The provided value for the encoding scheme is not valid for the DB2 version of the server. No script is generated.

Refer to the SQL reference for a valid value of the encoding scheme for the DB2 version.

ASN1589W

The calculation of the table space container size has resulted in a value that is too low to be used in a valid table space container definition. To ensure that the definition will be accepted by DB2, a replication-specific minimum container size has been provided for the table space container definition.

For the calculation based on a percentage of the current source table size, check whether the source table contains data and if the statistics of the source table are up to date (using the RUNSTATS utility) . For the calculation based on a number of rows, check whether the number of rows is realistic.

ASN1590E

The provided table space is a partitioned table space. Creation of the replication control tables in a partitioned table space is not supported. No script is generated.

Specify a table space that is not partitioned.

ASN1600E

The specified remote server name cannot be found in the federated catalog table SYSIBM.SYSSERVERS, for the SERVERNAME value that was provided. The non-DB2 relational server cannot be accessed.

Verify the input provided for the remote server name and try the action again.

ASN1601E

The remote authentication information cannot be found in the federated catalog table SYSIBM.SYSUSEROPTIONS, for the SERVERNAME value provided. The non-DB2 relational server cannot be accessed.

Verify the input provided for the remote server name and try the action again.

ASN1602E

The federated replication functions are only supported on DB2 for Linux, UNIX, and Windows Version 8 and higher.

Make sure that the specified database server is at the correct level or do not issue the replication task against a server that does not support it.

ASN1603E

Non-DB2 relational servers can be Capture control servers or target servers, but they cannot be Apply control servers.

Specify a database server as the Apply control server.

ASN1604E

The specified remote table exists in the remote database but the corresponding nickname is not found in the federated database.

Create the nickname in the federated database, and then issue the replication task again.

ASN1605E

The nickname for the specified remote table exists but the corresponding remote table does not exist in the remote database.

ASN1606W

The nickname for the specified remote table exists but the corresponding remote table does not exist in the remote database. Although this is an orphan nickname, this inconsistent state is still tolerated when dropping Replication definitions. A script is generated.

The source nickname is not dropped when dropping the replication definitions. To ensure a consistent catalog, drop the nickname.

ASN1607W

A mismatch was found between a source column data type and its corresponding nickname target column data type. The mismatch does not violate DB2 compatibility rules, but it might cause a problem to native non-IBM end-user applications. The problem does not occur during replication of the column data. The problem does occur if end-user applications retrieve the data. For example, if the nickname data type is created using the default mappings from the non-DB2 relational data type to the DB2 data type, the column will hold the broadest range of data type values, which might clash with the end-user application requirement of a more restrictive data type. A script is generated.

Check the target to ensure that the nickname data type you need at the target is indeed the source column data type. If it is, then issue an ALTER NICKNAME statement to change the local data type of the nickname column. When you alter the nickname local data type to be the same as the source column data type, you enforce that the end-user application on the non-DB2 relational server sees the same data type as the source column data type.

ASN1608I

When creating the nickname for a CCD table, the nickname is altered based on the data type of the CCD table that is created in the non-DB2 relational server to ensure the proper data type setting. A script is generated that updates the definitions that were provided in the replication administration tool.

No action is required if the replication updates are acceptable.

ASN1609E

The target table nickname exists, and contains only a subset of the columns requested in the subscription.

Use another Nickname as the target table or change the subscription to match the columns in the existing nickname.

ASN1620E

The IBMSNAP_REGISTER table for this Capture schema and the ASN.IBMSNAP_SUBS_SET table already exist at the given server.

• If the architecture level of the existing IBMSNAP_REGISTER table for this Capture schema is 0201:
  • If the IBMSNAP_REGISTER table is already populated with valid replication definitions, migrate the Capture control tables to the latest version supported by replication.
  • If the IBMSNAP_REGISTER table is empty, drop the older version of the Capture control tables and reissue the replication task again.
• If the architecture level of the existing Capture control tables is Version 8 or later and it is the architecture level you intend, consider creating Capture control tables with a different Capture schema name.
• If the architecture level of the existing ASN.IBMSNAP_SUBS_SET table is 0201:
  • If the ASN.IBMSNAP_SUBS_SET table is already populated with valid replication definitions, migrate the Apply control tables to the latest version supported by replication
  • If the ASN.IBMSNAP_SUBS_SET control table is empty, drop the older version of the Apply control tables and reissue the replication task again.
• If the architecture level of the existing Apply control tables is Version 8 or later and it is the architecture level you intend, consider creating Apply control tables on a different server.

ASN1621W

The control tables of the replication schema selected for the drop request are not empty. Replication control information will be deleted if the generated scripts are executed.

If the architecture level is 0201, migrate the Capture or Apply control tables to the latest architecture level before dropping the control tables.

ASN1622E

Replication definitions are stored in Replication control tables. These tables must exist before a registration or subscription definition can be created. The existence of the IBMSNAP_REGISTER table is used to check if the control tables for the Capture control server already exist for a particular Capture schema. The existence of the IBMSNAP_SUBS_SET table is used to check if the control tables on the Apply control server already exist. The existence of IBMSNAP_SUBS_MEMBR is checked at the time of checking for the existence of a subscription member.

If the control table IBMSNAP_SUBS_MEMBR table does not exist, then your environment is in an inconsistent state. You must drop all the control tables from the Apply control server and then create them before attempting the action.

ASN1623W

The Drop Capture control tables or Drop Apply control server control tables action was issued and the control table was missing. The script will not generate the appropriate DROP statement for that control table.

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

ASN1624I

The captureschema.IBMSNAP_REGISTER table could not be found. A server is defined as a Replication Capture server when the appropriate Capture server control tables (including the IBMSNAP_REGISTER table) exist on the server.

Create the appropriate Capture server control tables, if needed.

ASN1625I

The ASN.IBMSNAP_SUBS_SET table could not be found. A server is defined as a Replication Apply control server when the appropriate Apply control server control tables (including the IBMSNAP_SUBS_SET table) exist on the server.

Create the appropriate control tables on the Apply control server, if needed.

ASN1626E

The table captureschema.IBMSNAP_REGISTER already exists at the given server.

ASN1627E

The table captureschema.ASN.IBMSNAP_REGISTER does not exist although other Capture server control tables were found at the given server. Capture server control tables cannot be created until the tables are dropped. The Replication definitions at the Capture server are in an inconsistent state.

Drop the remaining Capture server control tables to clean up the Capture control server definitions, and reissue the Create control table task. Loss of data occurs, so look at the content of the remaining control tables before issuing the drop task.

ASN1628E

The table captureschema.IBMSNAP_REGISTER does not exist with the provided architecture level. No script is generated.

Issue the replication task again at the appropriate architecture level for the appropriate Capture control server and Capture schema.

ASN1629E

No control tables exist on the Capture control server. No control tables are dropped, and no script is generated.

Issue the replication task again at the appropriate architecture level for the appropriate Capture control server and Capture schema.

ASN1630W

The IBMSNAP_REGISTER table does not exist on the Capture server. The replication architecture level is unknown, and if you provide an incorrect architecture level, you might lose critical data. No checks occur to determine whether a particular architecture level for the Capture control tables can be inferred. The control table is dropped if it exists. A script is generated.

Issue the task again with the appropriate architecture level for replication.

ASN1631E

The table ASN.IBMSNAP_SUBS_SET already exists at the given server. No script is generated.

ASN1632E

The table ASN.IBMSNAP_SUBS_SET does not exist although other Apply control server control tables were found at the given server. Apply control server control tables cannot be created until the tables are dropped. The Replication definitions at the Apply control server are in an inconsistent state. No script is generated.

Drop the remaining control tables on the Apply control server to clean up the Apply control server replication definitions. Reissue the Create control table task. Loss of data occurs, so look at the content of the remaining control tables before issuing the Drop task.

ASN1633E

The table ASN.IBMSNAP_SUBS_SET does not exist with the provided architecture level. No script is generated.

Issue the replication task again at the appropriate architecture level for the appropriate Apply control server.

ASN1634E

There are no control tables to drop from the Apply control server. No script is generated.

Issue the replication task again at the appropriate architecture level for the appropriate Apply control server.

ASN1635W

The table ASN.IBMSNAP_SUBS_SET does not exist on the Apply control server. The replication architecture level is unknown, and if you provide an incorrect architecture level, you might lose critical data. No checks occur to determine whether a particular Apply control server control table architecture level can be inferred. If the control table exists, it is dropped. A script is generated.

Reissue the task with the appropriate architecture level for replication.

ASN1636E

The synchpoint is either less than 0 or equal to hex zeros.

Make sure you run the before load script to translate the hex zeros and capture is running on the server.

ASN1637E

The target structure of at least one of the target subscription-set members in the given subscription set is greater than eight. A manual full refresh does not support target structures that are greater than eight.

Make sure that the target structure of the subscription-set member is less than or equal to eight, and then reissue the replication task.

ASN1638W

The manual full refresh supports complete targets only. The given subscription-set member is not complete and cannot be included.

No action is required.

ASN1639E

The manual full refresh supports complete targets only, and none of the targets is complete.

Make sure that at least one of the subscription-set members in the subscription set is complete, and reissue the replication task.

ASN1640E

The subscription set does not contain any subscription-set members.

Add at least one subscription-set member to the subscription set, and reissue the replication task.

ASN1641E

Neither the replication center nor the command line supports the replication action on an OS/400 system. The possible actions might be: creating capture server control tables, creating apply server control tables, dropping capture server control tables, or dropping apply server control tables.

Issue OS/400 commands to perform the replication action.

ASN1650I

The replication action started at the specified monitor server.

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

ASN1653I

The replication action ended successfully at the specified monitor server.

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

ASN1654E

The length of the specified input parameter is longer than the maximum allowable length. No script is generated.

Verify the input parameter value, and re-enter the parameter value.

ASN1655E

The value of the specified input parameter is not correct.

Refer to your documentation for valid parameter values.

ASN1656E

A value for this specified input parameter is mandatory for this action. However, the value is missing. No script is generated.

Enter a value for this mandatory input parameter, and rerun the replication action.

ASN1657E

You must specify at least one optional parameter value when issuing a command in which each parameter value is optional. No script is generated.

Issue the command again with the correct parameters.

ASN1658E

The value of one input parameter is the same as the value of another input parameter and will result in the creation of inconsistent definitions. No script is generated.

Issue the command again with valid parameter values.

ASN1659E

The specified contact name already exists in one of the rows in the ASN.IBMSNAP_CONTACTS table. Contact names must be unique. No script is generated.

Issue the command again with a different contact name.

ASN1660E

The specified contact name does not exist in any of the rows in the ASN.IBMSNAP_CONTACTS table. The contact name must exist in the ASN.IBMSNAP_CONTACTS table before you can alter, substitute, delegate, or drop the name. No script is generated.

Issue the command again with a different contact name.

ASN1661E

A group should have at least one associated contact. The specified contact is the last contact in each associated group, and the last contact cannot be dropped. No script is generated.

Drop each associated group before attempting to drop the contact.

ASN1662E

The contact name that you are attempting to drop is the only contact associated with conditions for either the Capture or Apply components. No script is generated.

Use the SUBSTITUTE option in the DROP CONTACT command, or use the SUBSTITUTE command to change the contact name of the conditions. If you do not need the conditions, drop the conditions and then drop the contact.

ASN1663E

You cannot enter a start date that is beyond the end date. No script is generated.

Issue the command again with a valid combination of dates.

ASN1664E

The specified group name already exists in one of the rows in the ASN.IBMSNAP_GROUPS table. Group names must be unique.

Change the group name, and issue the command again.

ASN1665E

The specified group name does not exist in any of the rows in the ASN.IBMSNAP_GROUPS table. The group name must exist in the ASN.IBMSNAP_GROUPS table before you can alter or drop the group name. No script is generated.

Verify the group name, and reissue the command.

ASN1666E

The group that you are attempting to drop is the only group associated with conditions for either the Capture or Apply components. No script is generated.

In order to drop the group, alter the contacts of the associated conditions and then reissue the command.

ASN1667E

The contact name that you are attempting to drop is not associated with the specified group.

Verify the specified contact name and reissue the command.

ASN1668E

The contact name that you specified is already associated with the specified group.

No action is required.

ASN1671E

The alert condition that you are attempting to create already exists with the same specified parameters on the monitor control server.

Verify this alert condition and issue the command again.

ASN1672E

The alert condition that you are attempting to drop or to alter does not exist on the monitor control server.

Verify the alert name and issue the command again.

ASN1673W

The condition name is not valid with a subscription-set name value. The name of the subscription set will be ignored.

Do not specify the subscription-set name value.

ASN1674W

The condition name is valid only with update-anywhere subscription sets.

Do not set this condition. This condition will be ignored.

ASN1675I

This message is used to send a test e-mail verifying the e-mail address entered in the contact.

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

ASN1677E

The apply qualifier and the subscription-set name do not exist in the IBMSNAP_SUBS_SET table on the specified apply control server.

Supply a valid apply qualifier and a valid subscription-set name.

ASN1678E

The capture schema does not exist in the ASN.IBMSNAP_CAPSCHEMAS table on the specified capture control server.

Supply a valid capture schema.

ASN1679E

The contact name does not exist in the ASN.IBMSNAP_CONDITIONS table. A contact can be substituted only if it exists in the ASN.IBMSNAP_CONDITIONS table. No script is generated.

Supply a valid contact name.

ASN1680I

This message is for your information only.

No action required.

ASN1681E

The monitor control tables already exist on the given server. No SQL script is generated.

Otherwise, the architecture level is not valid. You need to drop the tables manually before attempting to create the tables.

If the architecture level of the existing monitor control tables stored in the ARCH_LEVEL column of the ASN.IBMSNAP_MONPARMS table is at the latest level supported by replication, there is no need to run the command since the control tables already exist.

ASN1682E

There are no Monitor control tables to drop. No script will be generated.

Issue the replication task again for the appropriate server containing the Monitor control tables.

ASN1683E

The IBMSNAP_CAPSCHEMAS table already contains the Capture schema value that was specified as input for the "Create Capture Server Control tables" action. The Capture schema value must be unique.

Make sure that you have specified the correct value for the Capture schema field and delete the row containing the specified Capture schema from the IBMSNAP_CAPSCHEMAS table. Reissue the task.

ASN1684W

You tried to drop a nickname of a replication control table that was already dropped or deleted; therefore, the generated script does not contain a DROP statement for that nickname.

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

ASN1685W

You tried to drop a replication object that was already dropped or deleted; therefore, the generated script does not contain a DROP statement for that replication object.

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

ASN1686E

A non-DB2 object name was specified whose length is longer than the maximum length allowed for the actual object.

Refer to the SQL reference for your database.

ASN1687E

The specified table space does not belong to the default IBMCATGROUP node group. The replication action does not support this node group.

Verify the table space name and reissue the task.

ASN1688E

You can customize the table space when you create the control tables. You can use existing table space, a new table space, or a table space that has already been specified for another control table earlier in the same session. The values specified in these table space options are ambiguous. There are either no values, or more than one value is specified for these table space options.

Verify the values of the table space options and reissue the task.

ASN1689E

No alert conditions are defined for the specified monitor qualifier, Capture or Apply control server, and schema or Apply qualifier.

Define at least one alert condition for the monitor qualifier, Capture or Apply control server, and schema or Apply qualifier.

ASN1700E

The column cannot be supported by the replication capture program as defined. No script to register the specified is generated. The following values are valid for the reason code:

0

The data type is not supported.

1

The column is already registered.

2

z/OS fieldproc column.

3

This column does not qualify as a before-image column.

4

The data type is not supported through DB2 for federated.

5

The column does not exist in the source object.

6

The maximum number of registered LOB columns was exceeded for that table.

7

The column name starts with the before-image prefix.

8

This column does not qualify as a before-image column or as an after-image column.

9

A mixed-case column name is not supported when the source table is on a non-DB2 server.

10

This column name is a duplicate of one already provided for this source.

Check the reason code to determine why the column cannot be registered and take appropriate action.

ASN1701E

Locksize should be equal to the P(PAGE), R(ROW) or A(ANY), in the case of z/OS operating system.

Provide the correct locksize and submit your action again.

ASN1702W

before-image columns are required to support null values. If no before-image column value is present, an INSERT statement will fail. A script is generated to update user-provided definitions.

This message is for your information only; no action is required.

ASN1703E

The table cannot be supported by the Capture program as defined. No script is generated. The following values are valid for the reason code:

0

The table with a z/OS validproc.

1

Existing internal CCD table.

2

Existing CD table.

3

DB2 catalog table (Windows, UNIX, iSeries)

4

The table is already registered.

5

The source for an internal CCD table is not a registered source.

6

The source is a CD table and cannot be registered.

7

This source name is a duplicate for this session.

8

The source is a replication control table.

9

Not one of the source columns qualifies for registration.

10

The maximum number of registered LOB columns has been exceeded for this table.

11

Structured data types are not supported.

12

The before-image prefix can be only one character.

13

An internal error occurred.

14

A blank character is not a valid before-image prefix.

15

iSeries: The source table or view should not have blank spaces in it.

16

iSeries: A blank space character is not valid in the CD Table Owner/Name field.

17

iSeries: For a given source, you cannot register some before-image columns and some after-image only columns. Either all or none of the columns must have the before-image.

18

The CD name for this source is a duplicate; that CD name already exists for this session.

19

The source object type is not a valid object type for replication.

Check the reason code to determine why the table cannot be registered for change-capture replication and take appropriate action.

ASN1704E

The view cannot be supported by the Replication Capture mechanism, as defined. No script is generated. The following values are valid for the reason code:

0

None of the dependent tables for the view are registered.

1

The source-table columns on which the view is dependent are not registered.

2

The view is on an internal ccd.

3

The view is already registered.

4

The view has an 'OUTER JOIN' syntax.

5

The view includes more than one table or view column with a function, and no correlation is provided in the view definition for each table.

6

The view contains a reference to an aggregate function.

7

The view contains a subselect/subquery.

8

The view contains a reference to another view.

9

The view has an UNION.

10

No correlation is provided for the column.

11

The base table does not have the schema name.

12

The base table does not exist.

13

The view contains Table Expression as Table.

14

The dependent table does not exist.

15

A view on view cannot be registered.

16

The given source object is not a view.

17

This source view is a duplicate for this session.

18

The view definition cannot be supported.

19

The view has an asterisk (*) instead of a specific column name in the view definition.

20

The view contains the join of a CCD and a non-CCD table.

21

The view defined at the CCD table must be complete and condensed.

22

The dependent table is a nickname.

23

A federated registration expects a nickname to be registered as a source.

Check the reason code to determine why the view cannot be registered. If appropriate, fix the problem and register the view again.

ASN1705E

The change data table or view cannot be used for the current source to be registered, because it already exists at the Capture server. No script is generated.

Provide a different name for the change data object.

ASN1706W

If the new column is needed in dependent subscription sets, you first have to add the column to the internal CCD subscription member before adding the column to any subscription member needed.

Provide a different name for the change data object.

ASN1707W

The registered source is successfully updated. However, the Capture program does not recognize the corresponding captureschema.IBMSNAP_REGISTER table updates until a REINIT command forces it to do so. A script is generated. A Capture command is required afterwards for the effect of the script to be in action.

ASN1708E

The specified replication object is not defined in the replication control tables. No script is generated.

Ensure that the object is correctly specified in the command and it exists.

ASN1709W

Subscription members rely on the underlying source registrations that define the source member. If you drop a registered source table, the dependent source members of a subscription set are no longer valid. The subscription sets that are associated with the specified registration source can be found in the captureserver.IBMSNAP_PRUNCNTL table at the Capture control server, where the SOURCE_OWNER and SOURCE_TABLE correspond to the registered source that is dropped. The appropriate Apply control server and subscription set names are columns in the IBMSNAP_PRUNCNTL table. The associated subscription sets fail if Apply is running. A script is generated.

Deactivate or drop the dependent subscription sets before running the script, if the registered source has dependent subscription sets.

ASN1710W

View registrations rely on the underlying registration of the tables that make up the view definition. If you drop a registered source table, you invalidate any view registration that is based on the table. The views that might be affected can be found in the captureserver.IBMSNAP_REGISTER table at the Capture server, where the PHYS_CHANGE_OWNER and PHYS_CHANGE_TABLE are the same as the CD_OWNER and CD_TABLE of the registered source that is dropped. The associated subscription sets, which depend on the view registrations, fail, if Apply is running. A script is generated.

Deactivate or drop the appropriate subscription sets, or view registrations, before running the script, if the registered source has dependent view registrations.

ASN1711W

An active registration has a SYNCHPOINT value that is not null in its captureschema.IBMSNAP_REGISTER table. When the Capture program started, it expected all active registrations to always exist and be valid. So the Capture program needs to be signaled that a registered source was dropped because the drop action invalidates the registration information. Failure to provide that information to the Capture program causes the Capture program to fail. A script is generated, but is NOT ready to run.

ASN1712E

Inconsistent information was found for this registered source in the Capture server control tables. No script is generated.

Drop the registered source and create the registration again.

ASN1713E

The following values are valid for reason code:

0

The source is registered as a FULL REFRESH and therefore cannot be deactivated.

1

The source is a CCD and CCD registrations cannot be deactivated.

2

The source is a view and view registrations cannot be deactivated.

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

ASN1714E

The following values are valid for the reason code:

0

The CD table for this source has RRN column (iSeries only). The RRN column must be the last column in the table, so the source cannot be altered.

1

The source is a view, and view registrations cannot be altered.

2

The source is registered for full refresh and cannot be altered.

3

The source table column does not match the column being altered.

4

The column is a LOB, DATALINK, or ROWID data type and does not qualify for a before-image value.

5

The before-image column value cannot be null or a blank character.

6

An after-image value has not been registered for the given column.

7

The before-image prefix cannot be updated if it is used with an existing registered source.

8

The use of the current before-image prefix makes one of the columns ambiguous in this registered source.

9

The before-image prefix can be only one character.

10

An internal error occurred.

11

The specified registration source name is a duplicate of a source included with that was changed, and the script for that registration was not yet executed.

12

The conflict level cannot be updated for the replica registration.

Check the reason code to determine why the source cannot be altered and take appropriate action.

ASN1715E

An error was encountered while issuing the appropriate command on the OS/400 operating system or iSeries servers. No script is generated.

Refer to the OS/400 Console Log for more detailed error information.

ASN1716W

A warning was encountered while issuing the appropriate command on the OS/400 operating system or iSeries server. A script is generated.

Refer to the iSeries Console Log for more detailed warning information.

ASN1717I

An informational message was encountered while issuing the appropriate command on the OS/400 operating system or iSeries server. A script is generated.

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

ASN1718E

The nickname is not supported by the Capture program as defined. No script is generated. The following values are valid for the reason code:

0

The internal CCD table (your CD table) already exists.

1

The nickname is on the native catalog table.

2

The nickname is already registered.

3

A federated registration expects a nickname as a source to be registered.

4

No columns are eligible for the Capture program.

5

The provided nickname is a duplicate from an earlier registration, but the corresponding script has not been executed.

6

A federated registration supports only user tables.

7

A federated registration supports only noncondensed and noncomplete CCD tables.

8

The CCD nickname provided is a duplicate of a CCD nickname from an earlier registration, but the script for that registration has not yet been executed.

9

Remote server information is not provided for the nickname registration.

Check the reason code to determine why the nickname cannot be registered.

ASN1719W

Dropping a registered source implies dropping all the objects that were created during the source registration, regardless of later updates. A script is generated.

Copy the trigger logic before dropping the registered source, if needed.

ASN1720E

A row is found in the captureschema.IBMSNAP_REGISTER table for the given source nickname but the CCD table information for that source is missing. The Change data table information is required to drop the replication definitions. A script is not generated.

Please make sure the correct source name is given and call the action again.

ASN1722W

The view must be registered as full refresh, because the base tables of this view are registered as full refresh only or are not registered replication sources.

No action is required.

ASN1723W

The view must be registered for change-capture replication, because the base tables of this view are registered for change-capture replication.

No action is required.

ASN1724E

The object that you specified cannot be created, because there is an existing object with the same type and same name on the non-DB2 relational server.

Provide a unique name for the object, and reissue the replication task.

ASN1725W

An trigger with this name already exists on the remote table in the non-DB2 relational database. The database manager might not indicate a conflict and might subsequently overwrite your existing trigger if you run the CREATE TRIGGER statement in the generated script. The database manager also might return a SQL error indicating that the object already exists. Generated trigger names cannot be customized, because customized triggers cannot be dropped when the registration is dropped.

First, determine how to merge the pre-existing triggers with the generated triggers. Then, either create your own script to merge your existing logic with the trigger logic that is generated by the replication tool, or update the script that is generated by the replication tool to include your existing trigger definitions.

ASN1726W

The trigger does not exist on the remote database. The trigger might have been dropped.

No action is required.

ASN1727I

The specified registered source has already been deactivated.

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

ASN1728W

For the given capture schema, the Apply program will join the IBMSNAP_UOW table and the CD table of the given source if the column JOIN_UOW_CD in the ASN.IBMNSNAP_MEMBR table is set to Y. This column contains Y if the target type of the associated subscription-set member is not user copy, or if any columns of the IBMSNAP_UOW table are used in the WHERE clause of the subscription-set member. If the Apply program joins tables with different encoding schemes, an error will occur.

For subscription members that will use this registration, define the target table with a type of user copy and do not use any IBMSNAP_UOW columns in the WHERE clause.

ASN1729E

The registration for this nickname cannot be dropped. No script is generated. The following value is valid for the reason code:

0

The specified nickname is a duplicate of a nickname included with a prior registration drop. However, the script for that registration drop has not yet been executed.

Resolve the problem indicated by the reason code.

ASN1730W

A procedure with this name already exists in the non-DB2 relational database. The database manager might not indicate a conflict and could subsequently overwrite your existing procedure if you run the CREATE PROCEDURE statement in the generated script. Or, an SQL error might be returned indicating that the object already exists. Generated procedure names cannot be customized because customized procedures cannot be dropped when the registration is dropped.

Determine how to merge the existing procedures with the generated procedures. Then, either create your own script to merge your existing logic with the procedure logic that is generated by the replication tool, or update the script that is generated by the replication tool to include your existing procedure definitions.

ASN1731W

The following value is valid for the reason code:

0

The non-DB2 relational database is an Oracle database and the Number column in that table will be converted to a Double data type in the nickname by the federated server.

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

ASN1732E

The native OS/400 command requires the source table to be journaled with both the before-image and after-image columns before registration.

Journal the source table with both the before-images and after-images before executing the generated script for the table registration.

ASN1733E

The following value is valid for the reason code:

0

The provided source is a duplicate from a prior DROP registration, but the corresponding script was not executed.

Check the name of the source provided and issue the task again.

ASN1734W

You are attempting to alter or add one or more columns to an existing registered source. The source registration has dependent view registrations, but the altered columns will not be reflected in the view registration definitions.

No action is required if you do not want the new column information to be reflected in the view registration.

ASN1735E

The table, view, or nickname was previously registered and dropped. However, the associated subscription set members were not dropped and the information for these members still exists in the replication control tables. To avoid any problems with the Capture and the Apply programs, the table or nickname is being re-registered and the information being requested needs to match the information that is stored in the control tables for the orphan members. The following values are valid for the reason code:

0

You are attempting to register the table or nickname for FULL REFRESH ONLY. The rows in the IBMSNAP_PRUNCNTL table indicate that this table or nickname was previously registered with the change-capture mechanism and the registration was dropped.

1

You are attempting to register the table or nickname with the change-capture mechanism. The rows in the IBMSNAP_PRUNCNTL table indicate that this table or nickname was previously registered as FULL REFRESH ONLY and the registration was dropped.

2

You are attempting to register the table or nickname with the change-capture mechanism. The source table was previously defined and was dropped. The values of the PHYS_CHANGE_OWNER and PHYS_CHANGE_TABLE columns in the IBMSNAP_PRUNCNTL table do not match with the input values specified for the CD/CCD owner or the CD/CCD table fields.

Take the specific actions for the following reason codes:

0

Register the table or nickname with the change-capture mechanism.

1

Register the table or nickname as FULL REFRESH ONLY.

2

Register the table or nickname and make sure that the change data or the consistent change data owner and the table names match those that are in the IBMSNAP_PRUNCNTL field. Do not customize these values so that the replication action will take the values stored in the control table.

ASN1736W

When the specified before-image prefix is appended to the column name, the name is longer than the maximum allowed column name limit on the non-DB2 relational server. The column name is truncated from the trailing end such that the length of the column name is equal to the maximum length.

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

ASN1737W

The procedure or trigger definition on the IBMSNAP_PRUNCNTL table prunes the CCD tables for all the registered nicknames. Each time that a nickname is registered or dropped from the registration, the procedure or trigger on the IBMSNAP_PRUNCNTL table is dropped and rebuilt using the new information for that particular nickname. The information specified for this registration does not contain the necessary information to define the procedure or the trigger on the IBMSNAP_PRUNCNTL table; therefore, the generated script does not contain a DROP or CREATE statement for the procedure or trigger.

Drop the registration for the missing nickname or the missing table.

ASN1738W

The procedure or trigger definition on the IBMSNAP_PRUNCNTL table recognizes the CCD tables for all the registered nicknames. Each time a registration is created, the procedure or trigger on the IBMSNAP_PRUNCNTL table is dropped and re-created with the existing and new registration information. The definitions stored in the control tables indicate that there are prior registrations on this server, but the procedure on the IBMSNAP_PRUNCNTL table could not be found. The procedure will still be created on the IBMSNAP_PRUNCNTL table with the definitions stored in the control tables.

Ensure that the generated procedure or trigger statement on the IBMSNAP_PRUNCNTL table has all the registered sources.

ASN1739W

The following value is valid for the reason code:

0

You cannot insert or update a column of data type TIMESTAMP in a Sybase or a Microsoft SQL Server database. A CCD table is being created on one of the non-DB2 relational systems with a column using data type TIMESTAMP (IBMSNAP_SYBTMSTMP column or the IBMSNAP_MSTMSTMP column). A table in a Sybase or Microsoft SQL Server database cannot have more than one column with a data type of TIMESTAMP; therefore, the data type of the column in the user table will be converted to a Binary(8) data type.

No action is necessary if the new data type is acceptable. If the new data type is unacceptable, do not run the generated script. Remove the specified column selection from the registration definition and reissue the task.

ASN1740W

The procedure or trigger definition on the IBMSNAP_PRUNCNTL table recognizes the CCD tables for all the registered nicknames. Each time a registration is created, the procedure or trigger on the IBMSNAP_PRUNCNTL table is dropped and re-created with the existing and new registration information. The remote CCD table does not exist on the non-DB2 server even though the nickname exists in the federated server. This table will not be included in the re-creation of the PRUNCNTL trigger or procedure.

Determine why the CCD table was dropped. If the table was dropped by mistake, either drop the registration of that source or re-create the CCD table with the original definition.

ASN1741W

The procedure or trigger definition on the IBMSNAP_PRUNCNTL table recognizes the CCD tables for all the registered nicknames. Each time a registration is created, the procedure or trigger on the IBMSNAP_PRUNCNTL table is dropped and re-created with the existing and new registration information. The CCD nickname does not exist in the federated server. This table will not be included in the re-creation of the PRUNCNTL trigger or procedure.

Determine why the CCD nickname was dropped. If the nickname was dropped by mistake, either drop the registration of that source or re-create the CCD nickname.

ASN1742E

There are existing registrations in the IBMSNAP_REGISTER table for non-DB2 relational sources that pertain to an earlier architecture level. You cannot register a new source until you migrate all registrations to the new architecture level.

Migrate your existing registrations for non-DB2 relational sources to the current architecture level. For details, refer to Migrating to SQL Replication Version 8.

ASN1800E

There can only be one subscription set with the same name, for a given Apply qualifier and Apply control server. No script is generated.

Create a new set name, or add new members to the existing set.

ASN1801E

The length of the statement exceeds the allowed limit (1024 in V8). No script is generated.

Rework the statement string so that its length is less than the allowed limits.

ASN1802W

In an update-anywhere scenario, changes made in one target replica will not be recaptured at the source when RECAPTURE='N'. If there is more than one target replica that subscribes to the same source, then the changes made to one target replica will not be reflected in the other replica targets.

If you want the changes propagated to the other replica targets, set RECAPTURE='Y'.

ASN1803I

A previous subscription set was dropped, without dropping all its appropriate statements. A script is generated for the new subscription set which shares the same name as the previous subscription set that was dropped. The previous subscription Statements are not dropped.

Issue a Drop Subscription Statements to delete the orphan statements.

ASN1804I

The valid range for this column is 0 to 999.

No action is required if the default value of 30 minutes is acceptable.

ASN1805I

The valid range for this column is 0 to 999.

No action is required if the default value of 0 minutes is acceptable.

ASN1806E

The subscription set would be not be valid if the member were added. No script is generated. The following values are valid for the reason code:

0

The subscription set has reached its maximum limit for members.

1

The source member for the Capture schema is not the same as the subscription set for the Capture schema.

2

The iSeries source member is not the same as the subscription set journal.

3

The condensed table member structure is incompatible with the other member structures.

4

The source member does not support change-capture replication, but the target member relies on change-capture. The target structure is either a CCD or replica table, but the source has no CD table.

5

The source member is not a complete table.

6

The target member definition expects the existence of the target table, but the target table does not exist.

7

The target member definition asks for creation of the target table, but the target table already exists.

8

The set contains only full refresh supported target tables, but the new member supports change-capture replication.

10

The set contains only target tables supported by change-capture replication, but the new member supports full refresh only.

11

Replica rule: if target member is a replica, the source member can be either a replica or a user table.

12

The target structure is not supported for this operating system.

13

The target structure is a CCD, which is set as a registration source (autoregistration), but the structure is not complete

14

The source member is not registered.

15

The source member columns have column definitions, but the target type is not an aggregate.

16

At least one of the excluded target columns from the subscription set is neither nullable nor NOT NULL with defaults.

17

The target member is a view that cannot be updated.

18

The subscription-set member already exists.

19

Unable to find a target column or expression with a valid mapping to the registered source.

20

Multiple effective sources have been found but have not been defined consistently.

21

The external CCD table is noncondensed and contains either DataLink or LOB columns.

22

The source member journal library or journal name does not match.

23

The remote journal name is not valid.

24

The journal name or library is not valid.

25

A replica table with remote journaling is not allowed.

26

An internal CCD table already exists for the specified registered source table.

27

The source and target servers must be the same for internal CCD tables.

28

The internal CCD table must be noncomplete.

29

The source table is remotely journalled and contains LOBs or DATALINK columns.

30

No related information exists in the IBMSNAP_PRUNCNTL table.

31

No related information exists in the IBMSNAP_PRUNE_SET table.

32

An internal CCD table with a view as a source is not allowed.

33

The target table is already shared by another existing member, and a conflict has been detected between the replication definitions with respect to the values of the NAME, IS_KEY, EXPRESSION, and TYPE fields stored in the IBMSNAP_SUBS_COLS table and the definitions requested for the new member.

34

The source is on a non-DB2 server and the requested target type is a replica. This scenario is not supported.

35

The specified source member does not have a valid nickname at the target server. The error occurred for one of the following reasons:

• You did not provide a nickname when creating the source member.
• You provided a nickname that does not exist at the target server and one cannot be created for you.
• You provided an object that is not a nickname.
• You provided a nickname that does exist at the target server but it is not associated with the specified source member.

For reason codes 1 through 34, either create the new member in a different subscription set or create a new subscription set for the new member.

For reason code 35, make sure that you provide a valid nickname that already exists at the target server and is associated with the source member.

ASN1807I

This message is for your information only, and no action is required. A script is generated. The following values are valid for reason code:

0

The new set results in a mixture of replica and read-only target members.

1

The subscription set supports transaction commit counts, but the target member does not qualify for transaction processing.

2

At least one member has a target member that is a CCD table, but not all members have a target member CCD table. Different generations of tables are contained in the same set.

3

The target member is a non-condensed, non-complete CCD table, without extra columns from IBMSNAP. This target table is essentially the same as the CD table.

Review the reason codes in the explanation, and respond with the following options:

0

Consider keeping all the replica tables in one set, and the read-only tables in another.

1

Consider keeping all the target types that support transaction processing in the same set, and other tables in another set.

2

To maintain a consistent age of data across sets, consider keeping all the CCD target tables, which are part of the same generation, in the same set. Also, consider keeping all non-CCD target tables in a different set. The second set depends on the data being in the first set, as, for example in the middle-tier stage.

3

Consider whether you need the CCD target table.

ASN1808E

The target table allows its index keys to be updated (PRIMARY_KEY_CHG = 'Y'). To support this requirement, the Apply program needs to access the before-image columns of the index keys. So these before-image columns must exist in the Change Data table for the source member. If they do not exist, the Apply program fails. A script is not generated.

ASN1809W

In the cases listed, the PRIMARY_KEY_CHG settings are meaningless. A script is generated that was updated with Replication definitions that override user-provided definitions. The following values are valid for reason code:

0

The target table type CCD: PRIMARY_KEY_CHG is not valid.

1

The value of the CHG_UPD_TO_DEL_INS in the IBMSNAP_REGISTER table is set to 'Y'.

2

The target table is not condensed.

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

ASN1810W

Referential integrity constraints at the target table are not enforced by DB2 at the replica site. This might not be the intended behavior at the replica site. A script is generated, and the script might not be ready to execute.

Update the generated script to include the appropriate referential constraints at the target if needed.

ASN1811W

The Apply program relies on the unique index definition to correctly update and delete rows in the target table, for some target types. If the provided index does not guarantee uniqueness, the Apply program will have some rework. Understand your application to ensure that this will not be the case. The following values are valid for reason code:

0

At least one column is generated by an SQL function, which does not guarantee the uniqueness of the index.

1

In a unique index, nullable columns are not generated by SQL functions.

ASN1812E

Target members that require a unique index are target types of point-in-time, user copy, and replica tables, and condensed CCDs. If these targets do not have a unique index, the Apply program fails. A script is not generated. The following values are valid for reason code:

0

The target table does not already exist but the target key information could not be derived from the source table.

1

The target key information cannot be found nor derived, and the RRN is not defined for the CD table (iSeries only).

2

The target table or view already exists but the required target key information is missing.

3

The target table or view already exists but the target key information is incompatible with the existing partitioning key information.

4

The target table of type replica already exists. The specified column is part of the target key information but the source key information does not contain this column. The keys on both the source and the target members must match when the target table is of type replica.

5

The specified target key column is not found in the target table definition.

ASN1813I

Constraints at the source table are not enforced by DB2 if they are not specified during the target member definition. This might not be the intended behavior at the replica table server. A script is generated that might not be ready to execute. Constraints are described in the following valid values for reason code:

0

At least one NOT NULL WITH DEFAULT clause in the target member.

1

Partitioned table space.

Update the generated script to include the appropriate DB2 constraints at the target, if needed.

ASN1814E

The subscription member fails the subscription column checks. A script is not generated. The following values are valid for reason code:

0

The column data type is not supported by replication. Data types that are not supported by DB2 prompt the replication programs to issue message ASN1648E.

1

The target data type is incompatible with the corresponding source data type.

2

The column is not found in the source table registration.

3

The column type is not supported for federated targets.

4

The target column is a LOB. The maximum number of LOB columns is exceeded for the target member.

5

The source column contains SQL column function, but the target member structure is neither base aggregate nor change aggregate.

6

The target table type is replica, and the source column is a LOB column.

7

The target table type is replica, and source column is DATALINK value. But the CONFLICT_LEVEL > 0.

8

A noncondensed CCD target table with LOB columns is not supported.

9

The column is not in the existing target table.

10

The target column is already defined in the subscription member definition.

11

The data-type definition of the specified column prevents either an insert or an update operation or both on the column.

12

The specified target column name does not match the mapped source column name. The target column name cannot be different from that of the source column name because the target table is a replica.

13

The target column is mapped from a before-image column in the source and the source column can contain null values; however, the target column is neither nullable nor not null with default.

14

The specified target column name does not match with the mapped CD column name. The target column name cannot be different from that of the CD because the target table is an internal CCD.

Review the reason code in the explanation and respond as follows:

0

Change the data type to one that is supported.

1

Make sure the target data type matches the source data type.

2

Register the column of the source table.

3

Choose a valid data type that is supported for federated targets.

4

Make sure the number of LOB columns at the target member does not exceed the allowable limit.

5

Change either the source column expression or the target table structure.

6

Remove the LOB column for the replica target from the subscription member.

7

Remove the DATALINK column from the subscription member if the replica needs a conflict level greater than 0. Otherwise, change the replica conflict level.

8

Remove the LOB columns.

9

Verify the column name.

10

Verify the column name.

11

Remove the column from the subscription target member.

12

Make sure that the target column name matches the mapped column name in the source column name.

13

Modify the definition of the column in the target member to allow null or default values.

14

Make sure that the target column name matches the mapped column name in the CD table.

ASN1815E

The subscription set is not dropped because at least one member exists in the ASN.IBMSNAP_SUBS_MEMBR at the provided Apply control server, for the provided Apply qualifier of the particular subscription set. A script is not generated.

Drop the subscription members that still exist, and then drop the subscription set. Alternatively, issue the Drop Subscription Set task, with no requirement for the subscription set to be empty.

ASN1816W

When a subscription set is dropped successfully, all the set members are automatically dropped also.

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

ASN1818W

The specified member already contains a predicate. The new predicate overwrites the old one. A script is generated.

Provide the complete predicate clause for the replication task. You might need to update the predicate clause if does not contain all of the existing predicate clause.

ASN1819W

The Capture pruning logic does not prune any CD table until the dependent subscription members have been populated by the Apply program. A script is generated. It might need to be updated, if the disabling of the subscription set is not the ideal choice, and dropping the subscription set is a better option.

If the subscription set is going to be disabled for a considerable amount of time that the pruning process of the CD tables will be impacted, or if the impact to the CD tables for the dependent registered sources will impact dramatically the Capture program and the Capture server CD tables, then consider dropping the subscription set and creating it again later, instead of simply disabling it. Alternatively, deactivate the appropriate registrations.

ASN1820E

The specified string is not a valid. A script is not generated.

Please correct the appropriate object syntax and issue the replication task again.

ASN1821W

The dependent subscriptions rely on their source member tables to exist. If these source members are maintained as replication targets, and these targets are dropped, then the Apply program fails when it processes the dependent subscription sets. Dependent subscription sets might be impacted if the captureserver.IBMSNAP_PRUNCNTL table at the target server contains SOURCE_OWNER or SOURCE_TABLE rows for which these values are the target tables being dropped. A script is generated.

Deactivate or drop the dependent subscription sets before running the script, if required.

ASN1822E

The specified member cannot be found in the ASN.IBMSNAP_SUBS_MEMBR for the provided Apply qualifier at the provided Apply control server.

Make sure the Apply qualifier, set name, member name, and control server provided are correct.

ASN1823E

The specified subscription set cannot be found in the ASN.IBMSNAP_SUBS_SET for the provided Apply qualifier at the provided Apply control server.

Make sure the Apply qualifier, set name, member name, and control server provided are correct.

ASN1824W

The source is a view of multiple tables, and the commit count is null for the set. A Commit count of 0 is enforced for the set.

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

ASN1825W

Even though the request was made to drop the view the action was not completed as requested.

You need to manually drop the view.

ASN1826W

Please make sure the Capture schema exists before adding any members to the subscription set.

Create the Capture server control tables at the source server with the Capture schema specified.

ASN1827W

A DB2 column attribute of the source column differs from the corresponding target column. The following values are valid for reason code:

1

The source column is nullable and the target column is not nullable.

2

The source column is not nullable and the target column is nullable.

3

The source column has a default value and the target column has none.

4

The target column has a default value and the source column has none.

If the reason code is 1, then check whether there are null values in the source column that will be applied to the target column. If necessary, change the target column to NULLABLE. Alternatively, update the generated script to include the appropriate DB2 attributes at the target, if needed.

ASN1828E

These are current restrictions. No script is generated. The following values are valid for reason code:

0

Not supported.

1

Supported for the following target table structures: point-in-time, CCD, user copy.

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

ASN1829I

An existing target nickname was found in the federated database that is valid for this subscription (the data type mapping checks for columns are valid). However, there is no check to validate the existence of the target table on the non-DB2 relational database server.

Make sure that the remote table exists for the provided nickname. Otherwise, the Apply program fails.

ASN1830E

The subscription-set member is invalid, and no script is generated. A possible reason code is:

0

The predicate references columns from non-existing CD or UOW tables.

Verify the accuracy of the specified predicate, and refer to the documentation on advanced change predicate features.

ASN1831E

No subscription statements exist for the specified subscription-set name with this Apply qualifier.

Verify that the specified subscription-set name under this Apply qualifier contains subscription-set statements.

ASN1832W

The specified column already exists in the ASN.IBMSNAP_SUBS_COLS table.

No action is required.

ASN1833E

For the given capture schema, the Apply program will join the IBMSNAP_UOW table and the CD table of the given source if either the target type of the associated subscription-set member is not user copy, or if any columns of the IBMSNAP_UOW table are used in the WHERE clause of the subscription-set member. If the Apply program processes such a subscription-set member defined with the given source table and capture schema by joining the CD table of the source table with the IBMSNAP_UOW table, an error will occur because of the different encoding schemes of the tables.

Take one of the following actions:

• Select a target type of user copy and do not use columns of the IBMSNAP_UOW table in the WHERE clause of the subscription member.
• Register the source using a different capture schema and create the CD table in a table space with the same encoding scheme as those of the IBMSNAP_UOW table of the new capture schema.

ASN1834W

The subscription set requires a target Capture schema, and the default value of 'ASN' is used.

No action is required if the default is appropriate for the target Capture Schema column in this subscription set.

ASN1835W

The source column definition does not exactly match with the target column definition. Therefore, if the data that is selected from the source by the Apply program is not appropriate for the target column, the Apply program might fail or might modify the source data (by truncating it). Note: If your application does not generate data that will make the Apply program fail, there is no problem with the definition mismatch.

The following values are valid for the reason code:

1

The target column length is less than the resolved source column expression.

2

The target column scale is less than the resolved source column expression.

3

The target column precision is less than the resolved source column expression.

4

The target and source column data types are compatible only for certain source values.

If possible, change the definitions at the target site to be compatible with the source definitions. (This is usually driven by the applications that run at the target site.)

If you must keep the definition mismatch (because you have a specific reason why the target definitions must be different than the source definitions), review your applications to ensure that the definition mismatch will not cause a run-time problem.

ASN1836W

The target table is registered as a source under the specified Capture schema. If the table is dropped, the registration will no longer be valid.

Drop the registration for the table, and then drop the table.

ASN1837W

The target table is a replica or an external consistent-change data (CCD) table (CCD). The table is also registered at the target server so it may be the source for dependent targets. The table cannot be dropped automatically.

Drop the registered source for the replica or external CCD table. Then, manually drop the DB2 target table or delete the replica or external CCD subscription member. The deletion of the member will drop the DB2 target table.

ASN1838E

The following values are valid for the reason code:

0

The specified target table name does not exist or its schema is not created using either the "Create Collection" or "Create Schema" command; therefore, the specified table is not journaled. The journal information of the target table is required when registering the target table in the 'F' direction subscription set for the replica. The table needs to be created on an OS/400 system.

1

The specified target table exists but there is no journaling information for the table. The journal information of the target table is required at the time of registering the target table in the 'F' direction set for the replica.

ASN1839I

The source member is of type view in this replica scenario. Views cannot be updated; therefore, the registered base table of the view that has the largest number of columns will be used as the target member in the 'F' direction.

Verify that your scenario is still valid.

ASN1840W

The target database is on an OS/400 system and the target table space definition will be ignored.

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

ASN1841E

A series of checks are performed on the given expression value for the target member against the source member to ensure data integrity rules. The specified expression failed in one or more of the checks performed.

Refer to the SQL message returned and the SQL reference for any additional information.

ASN1842W

The internal CCD table takes precedence over the CD table when Apply tries to apply the changes to the target. An internal CCD is created for the specified source, which already has a CD table and subscription members defined. Some of the columns in the CD table do not exist in the internal CCD table and those members that were defined before the CCD table was created will become invalid.

Make sure that your scenario is valid.

ASN1843E

For OS/400 only. Duplicate rows are not allowed in the IBMSNAP_REG_EXT table for each combination of source_owner, source_table, and source_view_qualifier.

Delete the row from the IBMSNAP_REG_EXT table that does not belong and reissue the task.

ASN1844E

The source table and the source table registration can reside on different servers only if both the source database and the Capture database are located on iSeries machines. At least one of the servers is not on an iSeries system.

Make sure the source table and the source table registration reside on the same server before reissuing the task.

ASN1845E

The z/OS replication control tables are created with the maximum length of the table name as 30 characters. The error message was received because either the Capture control server or the Apply control server or both are on a z/OS system, and the specified target table name length is greater than 30. The subscription set member cannot be created.

Ensure that the table name length of the target member is not longer than 30 characters. In some cases the source database restrictions limit the capabilities at the target, because the target table name must be stored at the Capture control server and at the Apply control server. In such cases, you can create a view of the target table using a name that is less than or equal to 30 characters, and define the subscription set member using the target view name.

ASN1846E

An error has occurred while promoting the given set because the set has one or more invalid members.

Verify the information that you are inputting is correct, and reissue the task.

ASN1847E

You are unable to map a view column to the corresponding base table column because the view definition is unsupported.

Verify that the view definition is correct, and reissue the task.

ASN1848W

The target object is a view. A target key will be created on the view. The unique index supporting this target key could not be created on the base table of the view because the view columns used for the target key could not be mapped to the base table columns.

Create the index on the base table manually.

ASN1849E

The following value is valid for the reason code:

0

Either the Capture server or the target server is a federated database. Promote subscription works only for subscription sets on two DB2 systems.

This is a current restriction, and no action is required.

ASN1850W

The specified column can contain rational digits, but it is mapped to an integer column. Some of the digits in the original data might be truncated.

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

ASN1851E

The specified object cannot be added to the table definition because the new definitions and the existing table properties cannot coexist according to the DB2 rules for the coexistence of table constraints for partitioned tables.

See the SQL Reference for further details on table constraints.

ASN1852E

The specified object cannot be added to the table definition because the new definitions and the existing table properties for the partitioning key cannot coexist according to the DB2 rules for the coexistence of table constraints for partitioned tables.

See the SQL Reference for further details on table constraints.

ASN1853E

The specified index definition and the partitioning keys have conflicting definitions and cannot co-exist according to the DB2 rules for the coexistence of index properties and partitioning keys for partitioned tables.

See the SQL Reference for further details on table constraints.

ASN1854E

The following value is valid for the reason code:

0

The table definition is missing the required properties such as unique indexes supporting a ROWID, a primary key, and unique constraints, or LOB column properties such as a ROWID, LOB table spaces, auxiliary tables, and auxiliary indexes. At least one of the these mentioned needs to be present in the table definition to make it complete.

Redefine the table definition to include the required table properties.

ASN1855E

You selected the target key change option for the key column during subscription. The corresponding after-image column was not found in the replica source table.

Make sure that the original after-image column is available for subscription in the replica source.

ASN1856E

The specified OS/400 collection is not valid. The script will not be generated

Refer to the iSeries Console Log for more details on error information.

ASN1857E

The definitions stored in the replication control tables indicate that the source member already exists in another subscription set with an internal CCD defined as condensed. The same source member is being added as a source in another subscription set, but the target member is non-condensed. The data at the source side is already condensed and cannot be copied to a non-condensed target. The script will not be generated

Modify the target member definitions and reissue the task.

ASN1858E

The specified type of the table or view is not supported for the DB2 platform. You can include only certain types of tables as sources or targets in a subscription, depending on the DB2 platform.

Include only supported tables or views.

ASN1859E

The value for the LOADX_TYPE column in the IBMSNAP_SUBS_MEMBR table is 3 for the specified member. This value indicates that the crossloader will be used for this member. A nickname for the source table must be created at the target server and specified in the LOAD_SRC_N_OWNER and LOAD_SRC_N_TABLE columns. One or both of these values are missing.

Provide a value for either the LOAD_SRC_N_OWNER field or the LOAD_SRC_N_TABLE field, and reissue the task.

ASN1860W

The target table, view or nickname does not exist on the target database and it will not be dropped.

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

ASN1861E

The columns in the IBMSNAP_SUBS_COLS control table already contain values for NAME, IS_KEY, EXPRESSION, and TYPE and those values differ from the ones requested for the new member. A script for creating the new member is not generated.

To create the new subscription set member, use the same target properties as those that are stored in the IBMSNAP_SUBS_COLS table.

ASN1862E

Make sure that you provide a valid nickname that already exists at the target server and is associated with the source member.

ASN1863E

The Capture server is on a Version 8 new-function mode DB2 subsystem and the Apply control server is either on a workstation or an earlier version of DB2 for z/OS. The maximum length allowed for a schema name on a Version 8 new-function mode DB2 subsystem is much longer than the length allowed on this server.

Redefine your setup to use a Version 8 new-function mode DB2 subsystem as the Apply control server and issue the task.

ASN1864E

The target server is on a Version 8 new-function mode DB2 subsystem and either the Apply control server or the Capture control server is on a workstation or an earlier version of DB2 for z/OS. The maximum length allowed for a schema name on a Version 8 new-function mode DB2 subsystem is much longer than the length allowed on the control server.

Redefine your setup to use a Version 8 new-function mode DB2 subsystem as either the Apply control server or the Capture control server.

ASN1865E

The specified Capture control server is on a Version 8 new-function mode DB2 subsystem and the architecture level value obtained from the capture_schema.IBMSNAP_REGISTER table must be 0805. The architecture level obtained from the table is not 0805. You are running replication in Version 8 new-function mode; however, you did not migrate your control tables to support the new architecture level. No script is generated.

Run the migration program AASNSAMP member(ASNM2V8) to alter the replication control table definitions. This migration program sets the architecture level to 0805 and alters some of the columns of the control tables to a longer length.

ASN1866E

The specified Apply control server is on a Version 8 new-function mode DB2 subsystem and the architecture level obtained from the ASN.IBMSNAP_SUBS_SET table does not support Version 8 new-function mode DB2 subsystems. No script is generated.

Migrate the Apply control tables to the latest architecture level and then retry the action.

ASN1867E

Migrate your existing registrations for non-DB2 relational sources to the current architecture level. For details, refer to Migrating to SQL Replication Version 8.

ASN1900E

The following values are valid for reason code:

0

The table type on this operating system is not supported for promote request.

1

The source server operating system required for the promote needs to match the target server operating system.

2

The table or view does not exist.

Review the reason code in the explanation and respond as follows:

0

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

1

Current restriction.

2

Verify that the table or view exists on the source server operating system.

ASN1901E

The following values are valid for the reason code:

0

The table or view is not a registered source.

1

The registered source is a replica table.

2

The registered source is on DB2 for iSeries but has a remote journal.

3

The table or view has already been promoted.

4

A view on a view is not supported by the replication promote registration function.

Review the reason code in the explanation, and respond as follows:

0

The table or view name that you specified in the IBMSNAP_REGISTER table contained no entries for the specified Capture schema. The table or view registration cannot be promoted for this particular Capture schema.

1

The table you specified is of type replica (with a SOURCE_STRUCTURE column value of 7) in the captureschema.IBMSNAP_REGISTER table. The table cannot be promoted as a registered source. A replica can be promoted only within the context of a subscription set to ensure that proper definitions are maintained between the source user table and the replica target.

2

The registered source is maintained on DB2 for iSeries with a remote journal, which can be promoted only with SQL script.

ASN1902W

The promote tasks allows you to provide a new Capture server and new Capture server schemas. However, the promote tasks do not connect to the new Capture server to verify the names and existence of the Capture server and schemas. You must verify this information before running the script to ensure that the script executes successfully.

To generate the required objects, run the appropriate SQL prior to running the script.

ASN1903W

Since the promote tasks allow you to provide a new Apply control server name, the tasks detect whether some required objects exist to ensure proper execution of the generated script. A script is generated, but is not ready to run. The following values are valid for reason code:

0

The Apply control server control tables do not exist.

1

The registration information for all source members of a promoted set.

To generate the required objects, run the appropriate SQL prior to running the script.

ASN1904I

This message is for your information only; no action is required. A script is generated that might need some updates before being executed. The following values are valid for reason code:

0

The source member structure is incompatible with the target member structure.

1

The target member is a replica (replica1) that is also the source member of another replica (replica2.) The RECAPTURE value for the registration row of replica2 does not allow updates from the user table to be replicated at replica2.

2

The source member is a user table that is also the source member of more than one replica (replica1 and replica2). The RECAPTURE value for the registration row of the user table does not allow updates at replica1 to be replicated at replica2, and vice-versa.

Review the reason code in the explanation, and respond as follows:

0

Check the ASN.IBMSNAP_SUBS_MEMBR table, TARGET_STRUCTURE column. The value in the column should be compatible with the corresponding source member captureschema.IBMSNAP_REGISTER table, SOURCE_STRUCTURE column.

1, 2

Update the values, if needed.

ASN1905W

The promote task detected that the Capture server alias and the Capture schema name are the same on both on the host and new system. The generated SQL script must be modified, or it will fail when executed.

Take one of the following actions: 1) Run the same task with different Capture server alias and Capture schema name values for the host or new system. 2) Or, change the Capture server alias or Capture schema name in the generated script.

ASN1950E

The command was entered with incorrect syntax.

Check the documentation to verify your command syntax.

ASN1951E

A profile must exist before it can be used in a command.

Issue the corresponding SET PROFILE command, and then re-enter the command that failed.

ASN1952E

The Replication command line processor encountered an unrecoverable error condition.

Obtain the log file with the error, and contact IBM Software Support.

ASN1953I

All commands of this ASNCLP session completed successfully. Please note that some individual commands in this session may have produced errors, warnings, or informational messages.

Check the ASNCLP log file for any errors, warnings, or informational messages produced by the commands in this session.

ASN1954E

At least one command in the ASNCLP session failed, and processing stopped.

Look in the ASNCLP log file to diagnosis the error. Then fix the error, and try the command again.

ASN1955I

The ASNCLP session generated information in the specified files.

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

ASN1956I

All input for this command has been successfully parsed, and the command that generates the script is now invoked.

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

ASN1957E

The value of the input parameter is incorrect. The following values are valid reason codes:

1

The input parameter is a character value but should be a numeric value.

2

The input parameter is a numeric value but should be a character value.

3

The command line processor cannot access the specified file.

4

The date must be in the format yyyy-mm-dd and the time must be in the format hh:mm:ss.fffffffff. All components of date and time are mandatory except for the fraction part of time, denoted by fffffffff. The hyphens and colons are also mandatory.

5

The value of RELEASE must be 91 (Version 9.1), 95 (Version 9.5), 97 (Version 9.7), or 9.7.3 (Version 9.7 Fix Pack 3).

Check the reason code, and provide a valid input parameter value.

ASN1976E

The key that you specified already exists in the password file.

Enter this command again using the MODIFY parameter instead of the ADD parameter.

ASN1977E

The indicated input parameter must be specified.

Invoke the utility again using a valid input parameter value.

ASN1978E

The asnpwd command supports a maximum of eight characters for the length of the database alias and a maximum of 128 characters for the length of both the user ID and the password. The specific lengths of the user ID and the password are dependent upon the operating system that you are using.

Invoke the API using an input parameter with a valid length.

ASN1979E

The command was entered with incorrect syntax.

Check the documentation to verify your command syntax.

ASN1980E

The asnpwd command encountered system problems as indicated in the message.

Take action based on the information in the message. Enter the command again after fixing the error.

ASN1981I

The asnpwd command completed successfully.

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

ASN1982E

The key that you specified with the MODIFY or DELETE parameter does not exist in the password file.

Enter the command again using the ADD parameter.

ASN1983E

No password file was found.

Verify that the password file exists in the specified path. If you are using the Password Management utility for the first time, use the INIT parameter.

ASN1984E

The password file already exists in the specified path.

Verify that the password file has been deleted. Then retry the command.

ASN1985E

The operating system produced an unexpected error when trying to access the password file. No information about this error is available. However, this error might have occurred if the password file was manually edited causing the format of the file to change.

Retry the command. If the problem persists, use the INIT parameter to create a new password file.

ASN1986E

Password files created using Encrypt All contain only encrypted data (alias, user ID, and password). Encrypted data cannot be listed. Data can be listed only from password files created using the Encrypt Password parameter.

If you want to use the List option you must maintain a password file in which only the password is encrypted. You must delete the old password file using the asnpwd delete command and create a new password file using the asnpwd init encrypt password command.

ASN1987E

On 64-bit Windows operating systems, the ADD, MODIFY, DELETE, and LIST options of the ASNPWD command are not supported for password files that were created using the ASNPWD command before Version 9.5 Fix Pack 2. The ASNPWD command began using a new encryption method starting with this fix pack.

Take one of the following actions:

• Create a new password file using the ASNPWD INIT option. If you use this method, the password file can only be decrypted and read by replication programs that are at or newer than Version 9.5 Fix Pack 2. Do not use this method if an older replication program needs to read the password file.
• Use a different operating system to change the password file by running the ASNPWD command with the ADD, MODIFY, DELETE, or LIST options.

ASN1988E

Replication programs can read only password files that were created using the Advanced Encryption Standard (AES) algorithm. This algorithm is used by the asnpwd command when it creates encrypted password files.

Migrate the password file by using the asnpwd command with the migrate option, for example:

asnpwd migrate using mypwd.aut