This chapter contains a list of messages issued by DB2 replication for AS/400 for the Capture and Apply programs; the trigger programs for the register table, the pruning control table, and the critical section table; and the delete receiver exit routine.
The replication messages have the following prefixes:
Unless otherwise stated, all error codes "<error_code>" described in error messages are internal error codes used by IBM Software Support. Also, unless otherwise stated, error messages are issued with a return code of 8.
You can also obtain explanations for messages by typing the following command at a DB2 command prompt:
db2 message_number
ASN1001 | The Apply program encountered an SQL error. |
Explanation: The SQL was statement was not successful.
User Response: Check the messages in the job log to determine the cause of the problem. Try the request again.
ASN1002 | Critical section table not available. |
Explanation: The Apply program could not lock the critical section table.
User Response: Try the request again when the critical section table is available.
ASN1003 | Apply program could not connect to server "<server_name>". |
Explanation: The Apply program tried to connect to server "<server_name>" but was not successful.
User Response: Ensure the connection to the server is active. Check the messages in the job log to determine the cause of the problem. Try the request again.
ASN1011 | Copy request attributes not compatible. |
Explanation: The attributes of the target table must be compatible with the attributes of the base table.
User Response: Change the incompatible copy request values.
ASN1036 | The column type is not valid. |
Explanation: The column type "<col_type>" for expression "<expression>" is not valid. The error code is "<error_code>".
User Response: Change the column type to a valid value. The valid column types are: 'A' is an after-image column. 'B' is a before-image column. 'C' is a computed column without SQL column functions. 'F' is a computed column with SQL column functions. 'R' is a relative record number after-image key column.
ASN1050 | Refresh operation not valid. |
Explanation: The Apply program encountered an operation during refresh that is not valid. The operation is "<operation>". Error code "<error_code>".
User Response: Record the message number, operation code and error code, and contact your system administrator.
ASN1054 | Registration information not found. |
Explanation: The Apply program could not find the registration information for source owner "<src_ownr>", source table "<src_tbl>", and source view qualifier "<src_view_qual>". The error code is "<error_code>".
User Response: Examine the subscription and registration information. The data in the ASN.IBMSNAP_PRUNCNTL table does not correspond to the data in the ASN.IBMSNAP_REGISTER table for source owner "<src_ownr>", source table "<src_tbl>", and source view qualifier "<src_view_qual>". The user should remove the source table registration and try adding the source table registration again.
ASN1055 | Prune control information not found. |
Explanation: The Apply program could not find the prune control information for source owner "<src_ownr>", source table "<src_tbl>", source view qualifier "<src_view_qual>", target owner "<tgt_ownr>", and target table "<trt_tbl>". The error code is "<error_code>".
User Response: Examine the subscription and registration information. The data in the ASN.IBMSNAP_PRUNCNTL table does not correspond to the data in the ASN.IBMSNAP_REGISTER table for source owner "<src_ownr>", source table "<src_tbl>", and source view qualifier "<src_view_qual>". The user should remove the source table registration and try adding the source table registration again.
ASN1063 | Maximum number of set members exceeded. |
Explanation: The number of subscriptions has exceeded the maximum allowed number of 200. The error code is "<error_code>".
User Response: Remove excess members from the subscription set.
ASN1066 | Synchpoint could not be determined. |
Explanation: The synchpoint value for the set could not be determined because an internal Apply error occurred. The error code is "<error_code>".
User Response: Record the message number and error code, and contact your system administrator.
ASN1067 | Update conflicts detected. |
Explanation: More than one application updated the same row in a table from different locations. Some transactions have been rejected and compensated. The error code is "<error_code>".
User Response: See the unit of work table (ASN.IBMSNAP_UOW) for details. The user should refer to the product information for an explanation of the values in the IBMSNAP_REJ_CODE column.
ASN1068 | Referential integrity violation detected. |
Explanation: A referential integrity violation was detected when copying data from the source table to a replica. The subscription has been deactivated. The error code is "<error_code>".
User Response: Correct the referential integrity error and reactivate the subscription.
ASN1069 | Referential integrity violation detected. |
Explanation: A referential integrity violation was detected when replicating data from the replica to the user table. All of the affected units of work have been marked in the unit of work table (ASN.IBMSNAP_UOW) and compensated. The subscription has been deactivated. The error code is "<error_code>".
User Response: Correct the referential integrity error and reactivate the subscription.
ASN1070 | Target table not available. |
Explanation: The Apply program could not lock target table "<tgt_tbl>" in library "<library>" on server "<server>" to check for update conflicts. The error code is "<error_code>".
User Response: The user should verify that all the target tables are available before restarting the Apply program.
ASN1071 | Internal error in Apply program. |
Explanation: The Apply program detected an error while reading the temporary work file. The error code is "<error_code>".
User Response: The user should record the message number and error code, and contact their system administrator. The 7E00470E, 7F004714, and 81004706 error codes, indicate that the Apply program cannot read the format of the file that was generated by the ASNDLCOPY program. If you modified the ASNDLCOPY program, check to see if your changes are causing the invalid format.
ASN1073 | Program "<program>" in library "<library>" failed. |
Explanation: The set completion notification (ASNDONE) user exit program "<exit_program>" in library "<library>" failed. The reason code is "<reason_code>", and the return code is "<return_code>". The error code is "<error_code>". This message also indicates that the DATALINK file copy (ASNDLCOPY) user exit program "<exit_program>" in library "<library>" failed. The reason code is "<reason_code>", the return code is "<return_code>", and the error code is "<error_code>".
User Response: If the reason code is -999, the resolve system pointer (RSLVSP) MI instruction failed, or the call to the set completion notification (ASNDONE) user exit program failed. The user should refer to the job log to obtain information about the failure. If the reason code is not -999, the user should refer to the documentation for the set completion notification (ASNDONE) user exit program "<exit_program>" in library "<library>" for an explanation of the reason code and return code values. If the exit program is ASNDLCOPY, refer to the log file that was generated by the ASNDLCOPY program for detailed information.
ASN1110 | Row could not be inserted into apply trail table. |
Explanation: The Apply program could not insert a row into the apply trail table (ASN.IBMSNAP_APPLYTRAIL). The table structure of the apply trail table is not correct. The error code is "<error_code>".
User Response: The user should refer to the product information to obtain the correct table structure for the ASN.IBMSNAP_APPLYTRAIL table. The ASN.IBMSNAP_APPLYTRAIL table must be changed to have the table structure that is documented in the product information.
ASN1112 | Source table structure is not valid. |
Explanation: The value in the SOURCE_STRUCTURE column in the register table (ASN.IBMSNAP_REGISTER) is not valid. The error code is "<error_code>".
User Response: The source table structure for the registration must be changed to a valid value. A list of valid source table structure values can be found in the product information.
ASN1113 | Target table structure is not valid. |
Explanation: The value in the TARGET_STRUCTURE column in the subscription targets table (ASN.IBMSNAP_SUBS_MEMBR) is not valid. The error code is "<error_code>".
User Response: The target table structure for the subscription must be changed to a valid value. A list of valid target table structure values can be found in the product information.
ASN1114 | Change data table not found. |
Explanation: The Apply program could not find a source for the copy request because it could not find the change data table. The change data table was not defined in the register table (ASN.IBMSNAP_REGISTER). The error code is "<error_code>".
User Response: A change data table must be correctly defined in the register table (ASN.IBMSNAP_REGISTER) for the source table. The CD_OWNER and CD_TABLE columns must be specified for the registered table.
ASN1115 | Apply program waiting for global SYNCHTIME to advance. |
Explanation: The Apply program is waiting for the Capture program at server "<server>" to advance the global SYNCHTIME. The error code is "<error_code>".
User Response: Verify that the Capture program is running.
ASN1117 | No target column names were supplied. |
Explanation: The Apply program could not find any columns in the subscription columns table (ASN.IBMSNAP_SUBS_COLS). The error code is "<error_code>".
User Response: Redefine the replication subscription.
ASN1120 | Storage block could not be reserved. |
Explanation: The Apply program could not reserve a storage block. The error code is "<error_code>".
User Response: Record the message number and error code, and contact your system administrator.
ASN1121 | Apply program could not read from work file. |
Explanation: The Apply program could not read a record from the work file. The user probably does not have the proper access authority for one or all of the files. The error code is "<error_code>".
User Response: Determine whether the problem is caused by a lack of access authority and contact your system administrator to obtain what is needed.
ASN1122 | Apply program could not write into work file. |
Explanation: The Apply program could not write a record to the work file. Either the user does not have the proper access authority for one or all of the files or not enough space is left in the work file for the record. The error code is "<error_code>".
User Response: 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.
ASN1123 | Work file could not be opened. |
Explanation: The Apply program could not open the work file. The error code is "<error_code>"
User Response: Record the message number and error code, and contact your system administrator.
ASN1124 | Work file could not be closed. |
Explanation: The Apply program could not close the work file. The error code is "<error_code>".
User Response: Record the message number and error code, and contact you system administrator.
ASN1129 | SQL statement was not successful. |
Explanation: The SQL statement that the user specified to run as an EXECUTE IMMEDIATE SQL statement was not successful. The error code is "<error_code>".
User Response: Refer to the previous messages in the job log and the apply trail table (ASN.IBMSNAP_APPLYTRAIL) for detailed information.
ASN1135 | Subscription columns table not available. |
Explanation: The subscription columns table (ASN.IBMSNAP_SUBS_COLS) could not be accessed.
User Response: Check the messages in the job log to determine the cause of the problem. Try the request again when the ASN.IBMSNAP_SUBS_COLS table is available.
ASN1138 | No column names or expressions supplied. |
Explanation: No column names or expressions were specified in the subscription columns table (ASN.IBMSNAP_SUBS_COLS). Column names or expressions must be supplied for a subscription. The error code is "<error_code>".
User Response: Specify column names or expressions for the subscription request.
ASN1140 | OS/400 system operation failed. |
Explanation: The Apply program encountered an error on an OS/400 system operation. The error code is "<error_code>". The return code is "<return_code>".
User Response: Record the message number and error code, and contact your system administrator.
ASN1148 | Subscription was not successful. |
Explanation: The subscription did not run successfully. The error code is "<error_code>".
User Response: Check the messages in the job log or the apply trail table (ASN.IBMSNAP_APPLYTRAIL) to determine why the subscription failed. Correct the error and try the request again.
ASN1151 | Subscription was not successful. |
Explanation: The Apply program determined that a gap exists between the source table "<src_tbl>" and the target table. The error code is "<error_code>".
User Response: Check the control tables to determine why the gap is present. Take proper action to preserve data integrity before you reset the control table information to run the definition again.
ASN1B08 | The subscription set with Apply qualifier "<qual_name>" and set name "<set_name>" is not defined correctly. ERRCODE is "<error_code>". Explanation: The subscription set is not defined correctly. |
Explanation: The subscription set is not defined correctly.
User Response: Make sure that the WHOS_ON_FIRST column in ASN.IBMSNAP_SUBS_SET is specified correctly.
ASN1B09 | There is no subscription set defined for Apply qualifier "<qual_name>". |
Explanation: Define at least one subscription set for Apply qualifier "<qual_name>".
User Response: Define at least one subscription set for Apply qualifier "<qual_name>".
ASN200A | User table "<table_name>" registration not satisfied. The registration probably should be removed. |
Explanation: There are many reasons that data capturing for a replication source cannot continue. Depending on the severity, you can receive either an ASN2004 or an ASN200A message.
Because a journal job is usually responsible for capturing data from several replication sources, the journal job is not affected by these messages. These messages were generated due to a specific replication source. After sending the ASN2004 or ASN200A message, the Capture journal job continues processing other replication sources. The program ends only if the last erring replication source is the last journal job processing.
User Response: Use the DSPMSGD command to determine the conditions that caused this message. For example:
DSPMSGD ASN200A QDPR/QDPRMSG
ASN2002 | Turning Parameter table not found. |
Explanation: The journal job in the capture process has ended unexpectedly.
User Response: Check the job log of the referenced job to determine why that job ended unexpectedly. End the capture process (ENDDPRCAP command) and start it again (STRDPRCAP command).
ASN2004 | User table "<table_name>" registration not satisfied. The registration probably should be removed. |
Explanation: See ASN200A. This message was displayed because the user table "<user_table>" in library "<library>" is registered in the Register table, or the Change Data Control table, but it could not be processed because of reason code "<reason_code>". The reason codes and their meanings are located in the following list:
User Response: Use the DSPMSGD command to determine the conditions that caused this message.
ASN2017 | Starting point not found for journal "<table_name>" (C I G R). |
Explanation: One of the first tasks in the Capture control job is to establish the starting point with which to resume journal entry processing. The journal receiver containing entries corresponding to that starting point must be online. If that receiver is deleted prematurely, the control job sends message ASN2017 to ask you how you want to proceed.
Response I tells the control job to ignore the fact that a receiver is missing. Data capturing resumes using the current receiver chain. If you respond I, you are responsible for the integrity of the replication. The Capture program can not guarantee that all of the changes are made to the replication targets.
Response C cancels the Capture control job.
Response R retries establishing the starting point.
User Response: In most cases, a response of G is appropriate. (Cold start all the replication sources using this journal.)
ASN2019 | Not authorized to Tuning Parameters table. |
Explanation: You are not authorized to the IBMSNAP_CCPPARMS table in library ASN.
User Response: Ask the security officer to grant authority (GRTDPRAUT command) to you.
ASN2028 | Internal error in Capture program. |
Explanation: The Capture control job detected an internal error and posted a reason code.
User Response: Record the reason code and contact your system administrator.
ASN2029 | Internal error in Capture program. |
Explanation: The Capture program detected an unexpected exception.
User Response: Record the exception code and contact your system administrator. Refer to the job log for additional information relating to that exception.
ASN2030 | Cannot submit job. |
Explanation: The Capture controlling job could not submit a subordinate journal job to process changes.
User Response: Check the messages in the job log to determine the problem. Correct the errors and try the request again. If the problem recurs, contact the system administrator.
ASN2037 | Cannot send data queue message to job. |
Explanation: The Capture controlling job could not send message to the data queue of a subordinate job because the data queue is not empty.
User Response: To resume normal operation, end data capture environment by issuing the ENDDPRCAP command and start it again by issuing the STRDPRCAP command. It may be necessary to end that subordinate job by using the end-immediate option to allow the capture environment to be ended completely.
ASN2038 | Too many registrations for journal. |
Explanation: For the named journal, the number of base tables that are being actively captured exceeds the limit of 300.
User Response: Remove some registrations. If this is not possible, create a new journal and have some registrations changed to use the new journal.
ASN2039 | Lag limit exceeded. |
Explanation: Exceeding the lag limit causes the Capture component to send an ASN2039 message to the job log and to the system operator message queue.
User Response: By gathering system performance data, you can better determine what action might be necessary. Some possible solutions are:
ASN2042 | No registrations were found to process. |
Explanation: No registrations in the IBMSNAP_REGISTER table met the selection criteria provided on the Start DPR Capture (STRDPRCAP) command.
User Response: Change the selection criteria or specify *ALL on the JRN keyword and try the request again.
ASN2043 | No registrations for the specified journal. |
Explanation: The journal specified for the JRN keyword on either the STRDPRCAP command or the INZDPRCAP command is not one that has any tables registered in the table IBMSNAP_REGISTER in library ASN. The journal will be ignored.
User Response: Check for possible misspelling of the journal name. If this is the case, reissue the command with the correct name.
ASN2045 | Data changes not captured for table. |
Explanation: User table is registered in the Register table but it could not be processed.
User Response: Correct the problem and try the request again.
ASN2046 | Not authorized to Unit of Work table. |
Explanation: You are not authorized to the IBMSNAP_UOW table in library ASN.
User Response: Ask the security officer to grant authority to you by issuing the command GRTDPRAUT specifying AUT(*CAPTURE).
ASN2047 | Not authorized to index of Pruning Control table. |
Explanation: You are not authorized to index IBMSNAP_PRUNCNTLX in library ASN.
User Response: Ask the security officer to grant authority to you by issuing the command GRTDPRAUT specifying AUT(*CAPTURE).
ASN2048 | Not authorized to Capture Trace table. |
Explanation: You are not authorized to the IBMSNAP_TRACE table in library ASN.
User Response: Ask the security officer to grant authority to you by issuing the command GRTDPRAUT specifying AUT(*CAPTURE).
ASN2049 | Not authorized to Warm Start table. |
Explanation: You are not authorized to the IBMSNAP_WARM_START table in library ASN.
User Response: Ask the security officer to grant authority to you by issuing the command GRTDPRAUT specifying AUT(*CAPTURE).
ASN2050 | Registration Extension table not found. |
Explanation: The IBMSNAP_REG_EXT table was not found in library ASN.
User Response: Restore the ASN library from the previous save volume or call the QZSNCRTC program (CALL QDPR/QZSNCRTC) or restore the IBM DataPropagator Relation Capture and Apply for OS/400 licensed program (5769-DP2).
ASN2051 | Not authorized to Registration Extension table. |
Explanation: You are not authorized to the IBMSNAP_REG_EXT table in library ASN.
User Response: Ask the security officer to grant authority (GRTDPRAUT command) to you.
ASN2052 | Not authorized to index of Register Extension table. |
Explanation: You are not authorized to index IBMSNAP_REG_EXTX in library ASN.
User Response: Ask the security officer to grant authority to you by issuing the command GRTDPRAUT specifying AUT(*CAPTURE).
ASN2053 | Not authorized to index of Unit of Work table. |
Explanation: You are not authorized to index IBMSNAP_UOW_IDX in library ASN.
User Response: Ask the security officer to grant authority to you by issuing the command GRTDPRAUT specifying AUT(*CAPTURE).
ASN2055 | Not able to find full refresh start time. |
Explanation: The attempt to start Capture for Version 5 failed. The program is not able to find the full refresh starting time for source table.
User Response: The full refresh starting time is kept in the table ASN/IBMSNAP_REG_EXT. There should be a row in that table for each source table. The FR_START_TIME column in that row should have a valid time stamp. If this is not the case, there may be a few possibilities. One of which is that the row in table ASN/IBMSNAP_REG_EXT has been updated incorrectly. The other is that the table ASN/IBMSNAP_PRUNCNTL does not have program QZSNCAP5 in library QDPR as its trigger program.
ASN2056 | Registration for source table is invalid. |
Explanation: There is a registration entry for the source table in question. That table name is an SQL alias name. It has been altered since it was first registered. It is now based on a different physical file (or physical file member) from the one it was based on at the time of registration. This difference cannot be tolerated.
User Response: If the alias name that was registered has been changed since the registration, change it back to the way it was when you registered it. If you cannot change it back, delete the registration and re-register it.
ASN2057 | Not authorized to Authenticity Token table. |
Explanation: You are not authorized to the IBMSNAP_AUTHTKN table in library ASN.
User Response: Ask the security officer to grant authority to you by issuing the command GRTDPRAUT specifying AUT(*CAPTURE).
ASN2058 | Not authorized to Critical Section table. |
Explanation: You are not authorized to the IBMSNAP_CRITSEC table in library ASN.
User Response: Ask the security officer to grant authority to you by issuing the command GRTDPRAUT specifying AUT(*CAPTURE).
ASN2201 | Internal error in Capture program. |
Explanation: An error occurred in the Capture program.
User Response: Check the job log to determine the cause of the problem. Record the reason code and contact your system administrator.
ASN2301 | Internal error in Capture program. |
Explanation: This message is sent by the journal job as an escape message before the journal job ends. A condition exists that makes it impossible to continue capturing data.
User Response: Check the job log to determine the cause of the problem. To aid in problem determination, use the DSPMSGD command to determine the conditions that caused this message to be displayed. For example:
DSPMSGD ASN2301 QDPR/QDPRMSG
Record the reason code and contact your system administrator.
ASN2501 | Not authorized to register table. |
Explanation: You are not authorized to the ASN/IBMSNAP_REGISTER table.
User Response: Ask the security officer to grant authority to you or use the GRTDPRAUT command with *REGISTRAR.
The other replication messages include:
DataPropagator puts database triggers on the register table (table ASN/IBMSNAP_REGISTER). This trigger is called when any replication administration tool tries to insert, update, or delete a register table row. It is also called when someone tries to work with the register table directly.
The purpose of this trigger program is to maintain the register extension table (table ASN/IBMSNAP_REG_EXT, which exists only on AS/400). A secondary purpose of this trigger is to maintain the journal list in Capture program's primary control table.
The messages issued from the trigger program may appear in any job that works on behalf of the replication administration tools.
DataPropagator puts database triggers on the pruning control table (table ASN/IBMSNAP_PRUNCNTL). This trigger is called when any Apply program tries to insert, update, or delete a pruning control table row.
The triggers are needed to reduce CPU overhead of the Capture program and to maintain the FR_START_TIME column in the register extension table (table ASN/IBMSNAP_REG_EXT).
These messages will most likely appear in the Apply job log (or the equivalent of the jog log on other platforms).
DataPropagator puts database triggers on the critical section table (table ASN/IBMSNAP_CRITSEC). This trigger is called when any Apply program tries to insert, update, or delete a critical section table row.
The triggers are needed to support update anywhere.
The messages will most likely appear in the Apply job log (or the equivalent of the job log on other platforms).
The delete receiver exit routine errors are from the delete receiver exit routine QZSNDREP in library QDPR. This routine is called when a user tries to delete a journal receiver. It is usually called from a database server job, QDBSRC0x, which handles automatically deleting unneeded journal receivers. When the automated deleting of receivers seems to be not working, use the WRKACTJOB command to find any messages in these server jobs' job logs. You might find one of the listed messages or you might find other messages sent by the operating system.
ASN3050 | Change data table "<table_name>" not found. |
Explanation: The change data table referred to in the Register table was not found.
User Response: Remove the registration for that source table. Then register the source table and try the STRDPRCAP command again.
ASN3053 | Source table not found. |
Explanation: There is a registration entry found for the named source table. That source table is not found.
User Response: Delete the registration for that source table and register the source table again when appropriate.
ASN4501 | Register table not found. |
Explanation: The table ASN/IBMSNAP_REGISTER is not found.
User Response: Restore the ASN library from the previous save volume or run the CRTDPRTBL command or restore the IBM DataPropagator Relational Capture and Apply for OS/400 licensed program (5769-DP2).
ASN4502 | Register table index not found. |
Explanation: The index ASN/IBMSNAP_REGISTERX is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4503 | Pruning control table not found. |
Explanation: The table ASN/IBMSNAP_PRUNCNTL is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4504 | Pruning Control index not found. |
Explanation: The index ASN/IBMSNAP_PRUNCNTLX is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4505 | Trace table not found. |
Explanation: The table ASN/IBMSNAP_TRACE is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4506 | Warm start table not found. |
Explanation: The table ASN/IBMSNAP_WARM_START is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4507 | Critical section table not found. |
Explanation: The table ASN/IBMSNAP_CRITSEC is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4508 | Critical section index not found. |
Explanation: The index ASN/IBMSNAP_CRITSECX is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4509 | Index for the unit of work table not found. |
Explanation: The index ASN/IBMSNAP_UOW_IDX is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4510 | Register extension index not found. |
Explanation: The index ASN/IBMSNAP_REG_EXTX is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4525 | Apply qualifier cross reference table not found. |
Explanation: The table ASN/IBMSNAP_AUTHTKN is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4526 | Apply qualifier cross reference table index not found. |
Explanation: The index ASN/IBMSNAP_AUTHTKNX is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4527 | Unit of work table not found. |
Explanation: The table ASN/IBMSNAP_UOW was not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN4529 | Unit of work index not found. |
Explanation: The index ASN/IBMSNAP_UOW_IDX is not found.
User Response: Restore the ASN library from the previous save volume or run the Create DPR Tables command (CRTDPRTBL).
ASN6063 | Failed to update the PCB. |
Explanation: The trigger program for Register table issued a QUSCHGUS AP call in an attempt to update the user space QZSNCTLBLK in library ASN. The API call failed with an exception.
User Response: Record the reason code and try to correct the problem. If the problem recurs, contact your system administrator.
ASN6064 | Number of journals exceeds the limit. |
Explanation: An attempt was made to add an entry to the journal list in user space QZSNCTLBLK in library ASN. It has a limit of 500 entries. That limit is exceeded.
User Response: Reduce the number of journals that all registered source tables use to be less than the allowed limit.
ASN6065 | Attempt to convert base table name to system name failed. |
Explanation: An attempt was made to convert the base table name from the SQL name to system name for the subject source table. The conversion attempt failed.
User Response: Make sure the source table exists before retrying the request.
ASN6068 | Cannot find a matching row in IBMSNAP_REG_EXT. |
Explanation: An attempt was made to read a matching row for the named source table in table IBMSNAP_REG_EXT. The matching row was not found.
User Response: Ignore the error if you are trying to remove a registration. If you are not trying to remove a registration, insert a row in table IBMSNAP_REG_EXT with VERSION set to 5. SOURCE_OWNER and SOURCE_TABLE are set to the appropriate values. SOURCE_NAME is set to the system name of the source table. JRN_NAME and JRN_LIB should have the journal name and its library name of the journal the source table uses. SOURCE_TABLE_RDB should be NULL if the source table is in the same system, and should have the RDB name of the system where the source table is at otherwise. SOURCE_VIEW_QUAL is set to the corresponding value in the registration.
ASN6069 | Error detected in trigger program for IBMSNAP_REGISTER. |
Explanation: An error occurred in the trigger program (QZSNJRNL) for the Register table for Data Propagator Relational/400. This trigger program is needed to maintain a list of journals that all the registered base table in the system use. Additional message may be found in the job log which can help determine the cause of the problem.
User Response: Check the job log of the job that sent this message. Correct the problem and try the request again.
ASN6071 | Internal error in trigger program for IBMSNAP_REGISTER. |
Explanation: An error occurred in the trigger program (QZSNJRNL) for the Register table for DataPropagator Relational/400. This trigger program is needed to maintain a list of journals that all the registered base tables in the system use. Check the job log for possible additional messages which can help determine the cause of the problem.
User Response: Record the reason code and contact your system administrator.
ASN2401 | Internal error in trigger program. |
Explanation: An error occurred in the trigger program for Pruning Control table IBMSNAP_PRUNCNTL in library ASN.
User Response: Record the reason code and try to correct the problem. For example, for reason code 60 (Could not find a matching row for source table in index ASN/IBMSNAP_REG_EXTX) and reason code 90 (Could not find a matching row for source table in table ASN/IBMSNAP_REGISTER) your action could be to register the source table before trying to insert a row in the Prune Control table. For some other reason codes, it is possible that the referenced table is temporarily unavailable. Your action could be just to retry the task at a later time. If the problem recurs, contact your system administrator.
ASN2403 | Internal error in trigger program. |
Explanation: An error occurred in the trigger program for Pruning Control table IBMSNAP_PRUNCNTL in library ASN.
User Response: Record the reason code and try to correct the problem. If the problem recurs, contact your system administrator.
ASN2023 | Error occurred on file. |
Explanation: An error occurred when processing the named file.
User Response: Check the messages in the job log to determine the problem. Correct the errors and try the request again.
ASN6022 | Failed to read the journal list from the PCB. |
Explanation: Attempt to read the journal list from the user space QZSNCTLBLK in library ASN (the Primary Control Block) failed.
User Response: Check the message in the job log to determine the problem. Correct the errors and try the request again.
ASN6025 | Could not open table. |
Explanation: See message(s) in the job log for additional information about the reason why the open failed.
User Response: Correct the problem and try the request again.
ASN6067 | Program QZSNDREP gets an unexpected exception. |
Explanation: The DataPropagator for AS/400 registered an exit program for deletion of journal receivers. This delete receiver exit program (QZSNDREP) gets an exception unexpectedly.
User Response: Check the job log of the job that sent this message. Contact your system administrator.
ASN6068 | Cannot find a matching row in IBMSNAP_REG_EXT. |
Explanation: See above under "Messages from Trigger Program for Register Table".
User Response: See above under "Messages from Trigger Program for Register Table".