Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

An error occurred during the execution of an SQL statement.

Explanation

The connection to the specified server could not be established.

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

• 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.

Explanation

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

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

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

Explanation

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.

Explanation

The replication action started at the specified monitor server.

Explanation

The replication action ended successfully at the specified monitor server.

Explanation

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

Explanation

The value of the specified input parameter is not correct.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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

Explanation

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.

Explanation

This message is for your information only.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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

Explanation

The specified registered source has already been deactivated.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

The valid range for this column is 0 to 999.

Explanation

The valid range for this column is 0 to 999.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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

Explanation

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.

Explanation

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.

Explanation

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

Explanation

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.

Explanation

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

The command was entered with incorrect syntax.

Explanation

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

Explanation

The Replication command line processor encountered an unrecoverable error condition.

Explanation

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.

Explanation

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

Explanation

The ASNCLP session generated information in the specified files.

Explanation

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

Explanation

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).

Explanation

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

Explanation

The indicated input parameter must be specified.

Explanation

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.

Explanation

The command was entered with incorrect syntax.

Explanation

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

Explanation

The asnpwd command completed successfully.

Explanation

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

Explanation

No password file was found.

Explanation

The password file already exists in the specified path.

Explanation

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.

Explanation

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.

Explanation

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.

Explanation

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.