CDCL mufname PLUS-n MNT-n DBID-n
Reason:
This message was generated because a STATUS_CDC console command was issued to monitor the status of Change Data Capture (CDC). This message provides information relating to the output slots with the number of AUD log records to process and the DBID where the slot output is directed.
Refers to the Change Data Capture Listener (CDCL) program.
Specifies the name of the MUFplex or MUF that the Change Data Capture Listener (CDCL) tasks that are processed currently.
Indicates the output slot number 1-9.
Indicates the count of the number of CDC maintenance records processed. The MNT includes any records that might have been deleted because of a backout or records that might later be subject to backout.
Specifies the CDC DBID where the slot output is directed.
Action:
None. This message is for information only.
Reason:
DBCDSPR is starting up. This message identifies the release, SMP RMID level and the assembly date and time of the DBCDSPR module.
Action:
None. This message is for information only.
Reason:
When DBCDSPR is started through the system console with an MVS start command, the start command used to start it is displayed in this message as start_string.
Action:
None. This message is for information only.
Reason:
DBCDSPR was unable to open the SYSPRINT DD statement. Since this is a required DD statement, processing terminates.
Action:
Check the spelling of the DD statements allocated to the job step. Typically, the SYSPRINT DD is allocated as SYSOUT=*.
Reason:
DBCDSPR was unable to open the SYSIN DD statement. Since this is a required DD statement, processing terminates.
Action:
Check the spelling of the DD statements allocated to the job step. Ensure a SYSIN DD is allocated to provide control statements for DBCDSPS.
Reason:
The SYSIN DD statement has been successfully opened. DBCDSP reads the input stream and analyzes the parameters it has been given.
Action:
None. This message is for information only.
Reason:
The input stream contains control statements targeted to DBCDRPR. These are ignored. DBCDSPR only processes statements intended for it. This allows you to have control statements for both the sending and receiving components in a single file.
Action:
None. This message is for information only.
Reason:
The input contains control statements that are not properly marked as “SENDER” control statements. These are ignored.
Action:
None. This message is for information only.
Reason:
DBCDSPR has reached end of file on the SYSIN DD statement.
Action:
None. This message is for information only.
Reason:
A control statement that is marked for the sending component contains a parameter name that is not recognized.
Action:
Check the spelling of the parameter. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value in the current execution. You can also issue the MVS stop command to bring the current execution of DBCDSPR to an end. Correct the parameter, and then rerun DBCDSPR.
Reason:
A control statement that is marked for the sending component contains a parameter whose length exceeds the maximum parameter name length. Therefore, it is considered to be an invalid command.
Action:
Check the spelling of the parameter. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value. You can also issue the MVS stop command to bring the current execution of DBCDSPR to an end. Correct the parameter and then rerun DBCDSPR.
Reason:
A control statement that is marked for the sending component contains a parameter that accepts a limited number of specific values, such as “T” and “F”. The value specified is not in the list of acceptable values.
Action:
Verify the possible values that can be coded for this parameter. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value. You can also issue the MVS stop command to bring the current execution of DBCDSPR to an end. Correct the parameter and then rerun DBCDSPR.
Reason:
A control statement that is marked for the sending component contains a parameter that accepts only all numeric data. Non-numeric data was encountered.
Action:
Ensure only numeric values are specified for this parameter. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value. You can also issue the MVS stop command to bring the current execution of DBCDSPR to an end. Correct the parameter and then rerun DBCDSPR.
Reason:
A control statement that is marked for the sending component contains a parameter that accepts a numeric value within a limited range of values. The value provided is outside of that range. Message DB03313I that follows this message provides the limits of the range.
Action:
Consult the DB03313I following this message and select a value that is within the acceptable range. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value. You Ccorrect the parameter and then rerun DBCDSPR.
Reason:
The parameter value from the preceding DB03312 is outside of the valid range of acceptable values. That parameter accepts values equal to or greater than minimum and less than or equal to maximum.
Action:
Follow the action of message DB0312I.
Reason:
DBCDSPR encountered a parameter whose type is not known.
Action:
This is an internal error. Contact CA Support.
Reason:
When DBCDSPR extracted the current value of the parameter, it is either missing or so long that the end of the control statement was encountered.
Action:
Correct the parameter value. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value. You can also issue the MVS stop command to bring the current execution of DBCDSPR to an end. Correct the parameter and then rerun DBCDSPR.
Reason:
The parameter specified is allowed only during initial startup. DBCDSPR is already running so this parameter cannot be specified.
Action:
To set this parameter, issue the MVS stop command to bring the current execution of DBCDSPR to an end. Correct the parameter and then rerun DBCDSPR.
Reason:
The primary Datacom access module, DBNTRY, cannot be located.
Action:
This module has not been installed properly. The DBNRTY module must be link edited with the DBCDSPR module. Review the installation output. Also, ensure the STEPLIB contains the correct library names.
Reason:
DBCDSPR was trying to determine what release of Datacom is available. The INQIN requested failed.
Action:
Verify the environment is set up for DBCDSPR execution. It should be running in the same MVS image where the associated MUF is running.
Reason:
DBCDSPR has determined that the version of Datacom installed in the current environment does not have the level of code required to run this program. The nn is the release of Datacom that was found.
Action:
Ensure DBCDDSPR runs in a Datacom environment that supports Change Data Capture (CDC).
Reason:
DBCDSPR has determined that the version of Datacom installed in the current environment has the level of code required to run this program. The Datacom release of the associated MUF is nn.n.
Action:
None. This message is for information only.
Reason:
DBCDSPR attempted to open the URT used for access to the Change Data Capture (CDC) but the open failed. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
For return code ‘02’ make sure you have coded the CDCBASE parameter if the CDC DBID is not the default value of 2009.
For return code ‘25’, make sure that the CDC database has been defined. Also make sure the CDCDBID parameter is coded if the CDC database is not the default value of 2009.
Reason:
DBCDSPR has successfully opened the URT.
Action:
None. This message is for information only.
Reason:
DBCDSPR is connected to a MUF. The internal name of the MUF is mufname and it is using the CXX named cxxname. The MUF release is Rnn.nSPnn. The MUF is running in the MVS image named sysid as MVS job name jobname known to JES as jesname. The type of connection used is conntype which may be “local” “XCF” or “CCI”. If the connection type is “XCF”, then the XCF group clause will appear identifying the XCF group name as grpname.
Action:
None. This message is for information only.
Reason:
In the process of obtaining storage for buffers, DBCDSPR ran out of 31-bit storage. Processing terminates.
Action:
Increase the REGION size or use REGION=0M and restart DBCDSPR.
Reason:
The LOAD for MQTAIPR failed. MQTAIPR is the MQ Series API module.
Action:
Ensure the STEPLIB contains the correct library names. Also, it is possible that MQTAIPR was not installed properly. Review the installation output.
Reason:
The MQ series API module returned a non-zero return code when trying to connect to MQ series. rc is the return code, rsn is the reason code, info is the information code, and text is a brief interpretation of the failure codes. Processing terminates.
Action:
Make sure the WORKLDID identifies the correct MQ workload ID. Make sure the appropriate MQ queue manager has been started.
Reason:
DBCDSPR successfully connected to the MQ Series API.
Action:
None. This message is for information only.
Reason:
MQUSE N has been specified and the MSQOUT DD has been successfully opened.
Action:
None. This message is for information only.
Reason:
MQUSE N has been specified but the MSQOUT DD failed to open properly. Processing terminates.
Action:
Ensure the MSQOUT DD is present and defines an output file.
Reason:
The diagnostics output file has been opened successfully.
Action:
None. This message is for information only.
Reason:
The DIAGOUT DD failed to open properly. Processing continues. No diagnostic messages are written.
Action:
Ensure the DIAGOUT DD is present and defines an output file of SYSOUT=*.
Reason:
All initialization processes have completed. DBCDSPR is now considered to be up.
Action:
None. This message is for information only.
Reason:
DBCDSPR attempted to read (RDUKR) the Change Data Capture (CDC) TSN table but the read failed. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDSPR attempted to read (GSETL) the Change Data Capture (CDC) MNT table but the read did not return any rows. Processing continues. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code. This is not a normal condition. If there is a TSN row, there should be one of more corresponding MNT rows.
Action:
This condition should be reported to CA Support for review.
Reason:
DBCDSPR attempted to read (GSETL) the Change Data Capture (CDC) MNT table but received an unexpected return code. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDSPR attempted to allocate a table to manage the statistic counters for each table under the Change Data Capture facility control, but the initialization call failed. The return code is rc, the reason code is rsn, the information code is info, and the lowest level code is lowcode.
Action:
Ensure the STEPLIB contains the correct library names. Also, it is possible that DBTBLPR was not installed properly. Review the installation output.
Reason:
DBCDSPR attempted to read (GETIT) the Change Data Capture (CDC) MNT table but received an unexpected return code. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
All expected return codes are handled. Save all output and contact CA Support.
Reason:
The MNT row size plus the length of the header area is larger than can be handled with the current MQSIZE setting. Processing terminates.
Action:
Increase the MQSIZE parameter setting and restart DBCDSPR.
Reason:
A group of MNT records represents individual row updates in a CDC monitored table that were done under a single commit. DBCDSPR attempts to collect all the updates affected by a single commit into a single MQ Series buffer because the receiver module, DBCDRPR, will commit the updates in a single MQ Series buffer. At this point, DBCDSPR is forced to send the current MQ buffer. If any problems occur before all of the MNT records have been sent to the receiver module, the target database will be out of sync with the source database. When message DB03344I is issued, any concern about this partial send is over.
Action:
None. This message is for information only.
Reason:
This message accompanies DB03339I and identifies the TSN in process.
Action:
None. This message is for information only.
Reason:
DBCDSPR has completed processing for a given TSN row. It attempted to delete the Change Data Capture (CDC) TSN row but received an unexpected return code. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Processing terminates. All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDSPR has completed processing for a given MNT row and successfully deleted the MNT row. It attempted to commit the Change Data Capture (CDC) MNT row but received an unexpected return code. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Processing terminates. All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDSPR has completed processing for all MNT rows for a given TSN and successfully deleted the TSN row. It attempted to commit the Change Data Capture (CDC) TSN row but received an unexpected return code. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Processing terminates. All expected return codes are handled. Save all output and contact CA Support.
Reason:
Earlier in processing messages DB03339I and DB03340I were issued because a group of MNT rows had to be broken into one or more MQ Series buffers. The last of those buffers has now been sent.
Action:
None. This message is for information only.
Reason:
DBCDSPR had encountered an error and was attempting to roll back its updates but the roll back failed. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Processing terminates. All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDSPR had encountered an error and successfully rolled back updates for the TSN group it was processing.
Action:
None. This message is for information only.
Reason:
Earlier in processing, messages DB03339I and DB03340I were issued because a group of MNT rows had to be broken into one or more MQ Series buffers. An error was encountered as described in a previous message. Because the rest of the MNT rows for the failing group could not be sent, the target database is now out of sync with the source.
Action:
Manually synchronize the target database.
Reason:
DBCDSPR periodically checks to see if the MUF that it is connected to is trying to shut down. If it detects the MUF is attempting to shut down, it goes into a normal shut down sequence.
Action:
None. This message is for information only.
Reason:
DBCDSPR has received an EOJ command through the MVS MODIFY or MVS STOP command. DBCDSPR goes into the normal shutdown process.
Action:
None. This message is for information only.
Reason:
DBCDSPR received an MVS STOP command from the MVS system console. DBCDSPR goes into the normal shutdown process.
Action:
None. This message is for information only.
Reason:
DBCDSPR received a command via the MVS MODIFY command. The command, cmd, is echoed in this message before it is analyzed.
Action:
None. This message is for information only.
Reason:
DBCDSPR received a command via the MVS MODIFY command, but the command is not recognized. It is ignored.
Action:
Check the spelling of the command and try again.
Reason:
The MQ queue is full and will not accept any more data until the queue is cleared. The value of nbr is the retry attempt count and retry is the limit. If nbr reaches the value of retry, DBCDSPR terminates.
Action:
Ensure the MQ queue manager on the target system has been started. Make sure the receiver module, DBCDRPR has been started on the target system.
Reason:
The MQ queue is full and will not accept any more data until the queue is cleared. DBCDSPR has been in a wait/retry loop. The retry limit has been reached. DBCDSPR will go into termination processing. There is unsent data remaining.
Action:
Ensure the MQ queue manager on the target system has been started. Make sure the receiver module, DBCDRPR has been started on the target system. Once the receiver module, DBCDRPR, is up and running, restart DBCDSPR.
Reason:
While transmitting data to MQ, and unexpected return code was received. The return code is rc, the reason code is rsn, the information code is info, and text is a brief interpretation of the return and reason codes.
Action:
Once the problem has been corrected, start DBCDSPR to resume operations.
Reason:
When DBCDSPR attempted to delete a MNT row, it received an unexpected return code. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Processing terminates. All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDSPR attempted to allocate a table to manage the statistic counters for each table under the Change Data Capture facility control, but the initialization call failed. The function attempted was func, the return code is rc, the reason code is rsn, the information code is info, and the lowest level code is lowcode.
Action:
Save all the output and contact CA Support.
Reason:
There has been no maintenance activity for a while. The value of the DORMANTC parameter controls how frequently this message appears in periods of no activity. The message includes a timestamp marking the point in time this message was issued.
Action:
None. This message is for information only.
Reason:
The MQ series API module returned a non-zero return code when trying to disconnect from MQ series. rc is the return code, rsn is the reason code, info is the information code, and text is a brief interpretation of the failure codes. Processing terminates.
Action:
All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDSPR successfully disconnect from MQ Series during it shutdown sequence.
Action:
None. This message is for information only.
Reason:
During the course of DBCDSPR execution a count is kept of messages that are warning or error level. That count is displayed as nbr as execution concludes the termination sequence.
Action:
None. This message is for information only.
Reason:
DBCDSPR attempted close the URT but the close failed. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDSPR has successfully closed the URT.
Action:
None. This message is for information only.
Reason:
DBCDSPR has concluded the termination sequence. This is the final message produced during the termination sequence.
Action:
None. This message is for information only.
Reason:
DBCDSPR has received an MVS STOP command or an EOJ command through an MVS MODIFY or MVS STOP command. The MQ queue is full. DBCDSPR has been trying to send MNT/TSN updates to the target system. The unsent MQ buffer is discarded. Message DB03370I follows this message.
Action:
None. This message is for information only.
Reason:
DBCDSPR has received an MVS STOP command or an MVS MODIFY EOJ command. The MQ queue is full. DBCDSPR has been trying to send MNT/TSN updates to the target system. The unsent MQ buffer was discarded as indicated in DB03369W. To keep the source system and the target system synchronized, DBCDSPR will roll back the deletes of the TSN and MNT records.
Action:
None. This message is for information only.
Reason:
DBCDSPR has received a HELP command from the MVS system console. The output of this message contains descriptive text concerning commands DBCDSPR can be issued to DBCDSPR from the MVS system console.
Action:
None. This message is for information only.
Reason:
DBCDSPR has received a STATUS command from the MVS system console. The output of this message contains the current values of the various counters and other metrics that apply to the operation of DBCDSPR.
Action:
None. This message is for information only.
Reason:
DBCDSPR is in the process of terminating. Under normal circumstances, DBCDSPR sends a shutdown notification message to DBCDRPR. DBCDRPR uses this information to reset the expected sequence number of subsequent DBCDSPR restart. Because an MQ full condition exists, DBCDSPR does not attempt to send the shutdown notification.
Action:
DBCDSPR continues with normal shutdown, but a RC=4 is issued. Any subsequent restart of DBCDSPR results in DBCDRPR issuing a DB03458E “sequence error” message.
Reason:
DBCDSPR uses APF authorized services and must be installed into an APF authorized library.
Action:
DBCDSPR terminates. APF authorize the load library and run DBCDSPR again.
Reason:
The MUF to which DBCDSPR is connected was started with EXCTLNO set to a non-zero value. This limits the number of rows that DBCDSPR can obtain in a GSETL/GETIT block. DBCDSPR is forced to set the GBMAXR value in the URT to one less than the EXCTLNO value. If the EXCTLNO value is higher than 254, DBCDSPR sets the GBMAXR value to 254 because setting it to 255 means "no limit."
Action:
DBCDSPR continues, but using smaller GETIT blocks may impede the performance of extracting CDC data from the MUF. Coding EXCTLNO value of zero, or allowing the EXCTLNO value to default to zero will provide the maximum throughput. Changing the MUF startup parameter of EXCTLNO must be done before DBCDSPR starts.
Reason:
DBCDRPR is starting up. This message identifies the release, SMP RMID level, and the assembly date and time of the DBCDRPR module.
Action:
None. This message is for information only.
Reason:
When DBCDRPR is started through the system console with an MVS start command, the start command is displayed in this message as start_string.
Action:
None. This message is for information only.
Reason:
DBCDRPR was unable to open the SYSPRINT DD statement. Since this is a required DD statement, processing terminates.
Action:
Check the spelling of the DD statements allocated to the job step. Typically, the SYSPRINT DD is allocated as SYSOUT=*.
Reason:
DBCDRPR was unable to open the SYSIN DD statement. Since this is a required DD statement, processing terminates.
Action:
Check the spelling of the DD statements allocated to the job step. Ensure a SYSIN DD is allocated to provide control statements for DBCDSPS.
Reason:
The SYSIN DD statement has been successfully opened. DBCDSP will read the input stream and analyze the parameters it has been given.
Action:
None. This message is for information only.
Reason:
The input stream contains control statements targeted to DBCDSPR. These are ignored. DBCDRPR only processes statements intended for it. This allows you to have control statements for both the sending and receiving components in a single file.
Action:
None. This message is for information only.
Reason:
The input contains control statements that are not properly marked as “RECEIVER” control statements. These are ignored.
Action:
None. This message is for information only.
Reason:
DBCDRPR has reached end of file on the SYSIN DD statement.
Action:
None. This message is for information only.
Reason:
A control statement that is marked for the sending component contains a parameter name that is not recognized.
Action:
Check the spelling of the parameter. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value in the current execution. You can also issue the MVS stop command to bring the current execution of DBCDRPR to an end. Correct the parameter, and then rerun DBCDRPR.
Reason:
A control statement that is marked for the receiving component contains a parameter whose length exceeds the maximum parameter name length. Therefore, it is considered to be an invalid command.
Action:
Check the spelling of the parameter. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value in the current execution. You can also issue the MVS stop command to bring the current execution of DBCDRPR to an end. Correct the parameter, and then rerun DBCDRPR.
Reason:
A control statement that is marked for the receiving component contains a parameter that accepts a limited number of specific values, such as “T” and “F”. The value specified is not in the list of acceptable values.
Action:
Verify the possible values that can be coded for this parameter. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value in the current execution. You can also issue the MVS stop command to bring the current execution of DBCDRPR to an end. Correct the parameter, and then rerun DBCDRPR.
Reason:
A control statement that is marked for the receiving component contains a parameter that accepts only all numeric data. Non-numeric data was encountered.
Action:
Ensure only numeric values are specified for this parameter. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value in the current execution. You can also issue the MVS stop command to bring the current execution of DBCDRPR to an end. Correct the parameter, and then rerun DBCDRPR.
Reason:
A control statement that is marked for the receiving component contains a parameter that accepts a numeric value within a limited range of values. The value provided is outside of that range. Message DB03413I that follows this message provides the limits of the range.
Action:
Consult the DB03413I message and select a value that is within the acceptable range. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value in the current execution. You can also issue the MVS stop command to bring the current execution of DBCDRPR to an end. Correct the parameter, and then rerun DBCDRPR.
Reason:
The parameter value from the preceding DB03412 is outside of the valid range of acceptable values. That parameter accepts values equal to or greater than minimum and less than or equal to maximum.
Action:
Follow the action of message DB0312I.
Reason:
DBCDRPR encountered a parameter whose type is not known.
Action:
This is an internal error. Contact CA Support.
Reason:
When DBCDRPR was extracting the current parameter’s value, it is either missing or it is so long that the end of the control statement was encountered.
Action:
Correct the parameter value. To set this parameter in the current execution, use the MVS MODIFY command with the SET subcommand to alter the value in the current execution. You can also issue the MVS stop command to bring the current execution of DBCDRPR to an end. Correct the parameter, and then rerun DBCDRPR.
Reason:
The parameter specified is allowed only during initial startup. DBCDRPR is already running so this parameter cannot be specified.
Action:
If you need to set this parameter issue the MVS stop command to bring the current execution of DBCDRPR to an end. Correct the parameter, and then rerun DBCDRPR.
Reason:
The primary Datacom extended options access module, DBINRPR, cannot be located.
Action:
The DBINRPR module is loaded by the DBCDRPR module. DBINRPR is in the Datacom product load library. Ensure the STEPLIB contains the correct library names.
Reason:
DBCDRPR was trying to determine what release of Datacom is available. The INQIN requested failed.
Action:
Verify the environment is set up for DBCDRPR execution. It should be running in the same MVS image where the associated MUF is running.
Reason:
DBCDRPR has determined that the version of Datacom installed in the current environment does not have the level of code required to run this program. The nn is the release of Datacom that was found.
Action:
Ensure DBCDRPR runs in a Datacom environment that supports Change Data Capture (CDC).
Reason:
DBCDRPR has determined that the version of Datacom installed in the current environment has the level of code required to run this program. The Datacom release of the associated MUF is nn.n.
Action:
None. This message is for information only.
Reason:
DBCDRPR attempted to open the Dynamic System Tables URT used to access the MUF table definitions but the open failed. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
For return code ‘02’ make sure you have coded the SYSBASE parameter if the DBID of the Dynamic System Tables is not the default value of 1000.
Reason:
DBCDRPR has successfully opened the Dynamic System Tables URT.
Action:
None. This message is for information only.
Reason:
DBCDRPR is connected to a MUF. The internal name of the MUF is mufname and it is using the CXX named cxxname. The MUF release is Rnn.nSPnn. The MUF is running in the MVS image named sysid as MVS job name jobname known to JES as jesname. The type of connection used is conntype which may be “local” “XCF” or “CCI”. If the connection type is “XCF”, then the XCF group clause appears identifying the XCF group name as grpname.
Action:
None. This message is for information only.
Reason:
In the process of obtaining storage for buffers, DBCDRPR ran out of 31-bit storage. Processing terminates
Action:
Increase the REGION size or use REGION=0M and restart DBCDRPR.
Reason:
The LOAD for MQTAIPR failed. MQTAIPR is the MQ Series API module.
Action:
Ensure the STEPLIB contains the correct library names. Also, it is possible that MQTAIPR was not installed properly. Review the installation output.
Reason:
The MQ series API module returned a non-zero return code when trying to connect to MQ series. The rc is the return code, rsn is the reason code, info is the information code, and text is a brief interpretation of the failure codes. Processing terminates.
Action:
Make sure the WORKLDID identifies the correct MQ workload ID and that the appropriate MQ queue manager has been started.
Reason:
DBCDRPR successfully connected to the MQ Series API.
Action:
None. This message is for information only.
Reason:
MQUSE N has been specified and the MSQIN DD has been successfully opened.
Action:
None. This message is for information only.
Reason:
MQUSE N has been specified but the MSQIN DD failed to open properly. Processing terminates.
Action:
Ensure the MSQIN DD is present and defines an input file.
Reason:
The diagnostics output file has been opened successfully.
Action:
None. This message is for information only.
Reason:
The DIAGOUT DD failed to open properly. Processing continues. No diagnostic messages will be written.
Action:
Ensure the DIAGOUT DD is present and defines an output file of SYSOUT=*.
Reason:
All initialization processes have completed. DBCDRPR is now considered to be up.
Action:
None. This message is for information only.
Reason:
DBCDRPR attempted to read the Dynamic System Tables (DST) to obtain information about the MUF's user tables, keys, or key definitions, but the read failed. The specific table being accessed is xxx. Processing terminates. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
All expected return codes are handled. Save all output and contact CA Support.
Reason:
MQUSE N has been specified and all the captured changed data has been processed.
Action:
DBCDRPR goes into normal termination processing.
Reason:
DBCDRPR was processing the captured change data when it encountered an unknown maintenance code. The code is display as x.
Action:
If you are using MQUSE N, verify the data presented at DD MSQIN is data produced by DBCDSPR’s MSQOUT DD. Save all output and contact CA Support.
Reason:
DBCDRPR attempted to allocate a table to manage the statistic counters for each table being updated in this system, but the initialization call failed. The return code is rc, the reason code is rsn, the information code is info, and the lowest level code is lowcode.
Action:
Ensure the STEPLIB contains the correct library names. Also, it is possible that DBTBLPR was not installed properly. Review the installation output.
Reason:
DBCDRPR acquires additional storage for each table being updated in the environment. It was unable to obtain 31-bit storage for this purpose.
Action:
Increase the REGION size or code REGION=0M to allow DBCDRPR to obtain the storage it needs.
Reason:
For each table being updated, DBCDRPR creates a separate URT. DBCDRPR has encountered maintenance for a table it has not seen before. It creates a URT and other control blocks and has attempted to open it, but the open failed. The DBID and specific table experiencing the failure are nnnn and xxx, respectively. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Ensure the table is set for ACCESS MAINT.
Reason:
During termination processing, DBCDRPR closes all the URTs it has been using for maintenance activity. The close failed. The DBID and specific table experiencing the failure are nnnn and xxx, respectively. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Processing continues. Updates to the affected table are committed when all maintenance in a given buffer has been processed.
Reason:
During termination processing, DBCDRPR closes the URTs it has been using for exploring the MUF. The close failed. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Processing continues.
Reason:
The MUF to which DBCDRPR is attached does not contain the table. This table must be defined in the receiving MUF. DBCDRPR can then be restarted. The DBID and specific table experiencing the failure are nnnn and xxx, respectively.
Action:
DBCDRPR terminates.
Reason:
For an update or delete, DBCDRPR was not able to locate a record that matched the key in the CDC data. The update or delete cannot be processed.
Action:
The failing maintenance record including before and after images are dumped in the DIAGOUT log and written to ERROUT. If DB03469I is also seen immediately preceding this message, then the update was most probably completed in the previous run of this program.
Reason:
DBCDRPR has completed processing for all maintenance in the current buffer. It attempted to commit the maintenance but received an unexpected return code. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
Processing terminates. All expected return codes are handled. Save all output and contact CA Support.
Reason:
For an update or delete, DBCDRPR was not able to locate a record that matched the “before” image in the CDC data. The update or delete cannot be processed.
Action:
The failing maintenance record including before and after images are dumped in the DIAGOUT log and written to ERROUT. If DB03469I is also seen immediately preceding this message, then the update was most probably completed in the previous run of this program.
Reason:
DBCDRPR reads DRT and DRK Dynamic System Tables to determine which tables and keys may be used in maintenance activity. The MUF contains no table or key definitions.
Action:
This is an unexpected situation. Save all output and contact CA Support.
Reason:
DBCDRPR access the DRF Dynamic System Table to get information on key structure. The records describing the key named xxxxx where not found.
Action:
Processing terminates. This is an unexpected situation. Save all output and contact CA Support.
Reason:
DBCDRPR has finished analyzing the MUF Dynamic System Tables and has built or refreshed its DBID/Table control table.
Action:
None. This message is for information only.
Reason:
A maintenance record targeted to DBCDRPR processing is marked with a version of the MQ container that is higher than the version of DBCDRPR can handle. The most likely cause is that the sending module, DBCDSPR, is at a higher release level than the receiving module, DBCDRPR.
Action:
Processing terminates. Verify the STEPLIB of the DBCDRPR designates the correct load library.
Reason:
DBCDRPR periodically checks to see if the MUF that it is connected to is trying to shut down. If it detects the MUF is attempting to shut down, it goes into a normal shut down sequence.
Action:
None. This message is for information only.
Reason:
DBCDSPR has started up and sent a startup notification message. This message identifies the release, SMP RMID level and the assembly date and time of the sending DBCDSPR module.
Action:
None. This message is for information only.
Reason:
The source sender is connected to a MUF. The internal name of the MUF is mufname and it is using the CXX named cxxname. The MUF release is Rnn.nSPnn. The MUF is running in the MVS image named sysid as MVS job name jobname known to JES as jesname. The type of connection used is conntype which may be “local” “XCF” or “CCI”. If the connection type is “XCF”, then the XCF group clause appears identifying the XCF group name as grpname.
Action:
None. This message is for information only.
Reason:
The remote sender identified by the DB03450 message has sent a notification message that it is in the process of shutting down. This message is followed by a DB03475I message.
Action:
None. This message is for information only.
Reason:
DBCDRPR has received an EOJ command through the MVS MODIFY EOJ command. DBCDRPR goes into the normal shutdown process.
Action:
None. This message is for information only.
Reason:
DBCDRPR received an MVS STOP command from the MVS system console. DBCDRPR goes into the normal shutdown process.
Action:
None. This message is for information only.
Reason:
DBCDRPR received a command from the MVS MODIFY command. The command, cmd, is echoed in this message before it is analyzed.
Action:
None. This message is for information only.
Reason:
DBCDRPR received a command from the MVS MODIFY command, but the command is not recognized. It is ignored.
Action:
Check the spelling of the command and try again.
Reason:
DBCDRPR has just completed processing maintenance in a changed data buffer and is attempting to release it. The ACK call to the MQTS API module has failed. The return code is rc, the reason code is rsn, the information code is info, and text is a brief interpretation of the return and reason codes.
Action:
Ensure the MQ queue manager on the target system is still running.
Reason:
The records sent by MQ are numbered. DBCDRPR expects the next record it receives will have a sequence number one greater than the previous record it processed. The value it was expecting to see was n, but it received the value x. There may be MQ record that have been lost.
Action:
If the value of x is 1, then the most likely explanation is that the sending module, DBCDSPR was stopped and restarted or the source MUF may have been recycled. If x is greater than n, then there are records that have been lost. The target system needs to be resynchronized with the source system. If x is less than n, then it is likely that one or more records are being reprocessed and any maintenance that was previously applied may appear to be errors.
Reason:
While receiving data from MQ, and unexpected return code was received. The return code is rc, the reason code is rsn, the information code is info, and text is a brief interpretation of the return and reason codes.
Action:
Processing terminates. Once the problem has been corrected, start DBCDRPR to resume operations.
Reason:
DBCDRPR has received a buffer from MQ by the MQTS API module. The accompanying directive code is not supported. The code is displayed as n.
Action:
Processing terminates. All expected directive codes are handled. Save all output and contact CA Support.
Reason:
DBCDRPR attempted to allocate a table to manage the statistic counters for each table under the Change Data Capture facility control, but the initialization call failed. The function attempted was func, the return code is rc, the reason code is rsn, the information code is info, and the lowest level code is lowcode.
Action:
Save all the output and contact CA Support.
Reason:
There has been a failure and DBCDRPR is attempting to roll back maintenance that was being processed in the current buffer, but the ROLBK failed. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
None. This message is for information only.
Reason:
The MQ series API module returned a non-zero return code when trying to disconnect from MQ series. The rc is the return code, rsn is the reason code, info is the information code, and text is a brief interpretation of the failure codes. Processing terminates.
Action:
All expected return codes are handled. Save all output and contact CA Support.
Reason:
DBCDRPR successfully disconnected from MQ Series during its shutdown sequence.
Action:
None. This message is for information only.
Reason:
During the course of DBCDRPR execution a count is kept of messages that are warning or error level. That count is displayed as nbr as execution concludes the termination sequence.
Action:
None. This message is for information only.
Reason:
There has been a failure and DBCDRPR needed to roll back maintenance that was being processed in the current buffer. The roll back has completed successfully.
Action:
None. This message is for information only.
Reason:
DBCDRPR is processing an update or delete and has issued a read for a record with a matching key. The read failed. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
The maintenance record containing the before and after image is dumped in the DIAGOUT output file and is written to ERROUT. This maintenance activity failed. Processing continues to the next maintenance item.
Reason:
DBCDRPR has concluded the termination sequence. This is the final message produced during the termination sequence.
Action:
None. This message is for information only.
Reason:
DBCDRPR is processing an update. It has located one or more records that match the key, but it has not yet found one that matches the “before” image. However, it located one that matches the “after” image. It will continue searching through the records whose keys match.
Action:
If you are restarting DBCDRPR after an outage, this message implies that the update has been previously processed.
Reason:
DBCDRPR is processing an update. It has located a record that matches both the key and the “before” image. It attempted to update the record using the “after” image, but the update failed. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
The maintenance record containing the before and after image is dumped in the DIAGOUT output file and is written to ERROUT.
Reason:
DBCDRPR has received a HELP command from the MVS system console. The output of this message contains descriptive text concerning commands that can be issued to DBCDRPR from the MVS system console.
Action:
None. This message is for information only.
DB03472I
Reason:
DBCDRPR has received a STATUS command from the MVS system console. The message output contains the current values of the various counters and other metrics that apply to the operation of DBCDRPR. In the time stamp yyyy is the year, mm is the month, dd is the day of the month, hh:mm:ss.nnnn is the time of day.
Action:
None. This message is for information only.
Reason:
DBCDRPR is processing a delete. It has located a record that matches both the key and the “before” image. It attempted to delete, but the delete failed. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
The maintenance record containing the before image is dumped in the DIAGOUT output file and written to ERROUT.
Reason:
DBCDRPR is processing an add request. It attempted to add, but the add request failed. If it is a duplicate record condition, the duplicate counter is incremented otherwise the general error counter is incremented. The return code is xx and the extended return code is nnn. The text is a brief interpretation of the return code.
Action:
The maintenance record containing the after image is dumped in the DIAGOUT output file and written to ERROUT.
Reason:
DBCDSPR and DBCDRPR use record sequencing to ensure no record gets lost in transit. Each time DBCDSPR starts up, it begins record sequencing at 1. A termination notification message has been received from DBCDSPR, so no new records will arrive from the current instance of the remote sender. DBCDRPR resets the expected next record sequence number to 1 in case DBCDSPR is restarted on the sending end. This prevents the DB03458E “sequence error” message if DBCDSPR is restarted.
Action:
None. This message is for information only.
Reason:
The sending module, DBCDSPR, has sent a text string to be echoed in the DBCDRPR processing log. The text is displayed as text.
Action:
None. This message is for information only.
Reason:
The MQ buffer contains a record marked for some other application. It is ignored, but its contents are dumped in the diagnostic output file.
Action:
Processing continues and the final return code is unaffected.
Reason:
During normal processing, a call to the MUF received a return code 86, meaning the MUF has gone down.
Action:
DBCDRPR goes into termination processing. Rollback is not attempted, but the rollback of any in-transit update is performed when the MUF comes back up.
Reason:
DBCDRPR uses APF authorized services and must be installed into an APF authorized library.
Action:
DBCDRPR terminates. APF authorize the load library and run DBCDRPR again.
Reason:
During startup, DBCDRPR analyzes the MUF for user tables. It collects information about the primary key and the key structure. If the user creates a new table and activates CDC processing for it, DBCDRPR will go back and reanalyze the MUF for user tables. If the table is still not found, then DBCDRPR issues message DB03441E and terminates with RC=12. If the new table is detected, normal processing resumes after the DB03447I message is issued.
Action:
None. This message is for information only.
Reason:
The ERROUT file, where failed transactions area copied, was specified and is now open.
Action:
None. This message is for information only.
Reason:
The ERROUT file, where failed transactions area copied, did not open correctly. The most common cause is omitting the DD from the JCL.
Action:
DBCDRPR does not attempt to use the ERROUT file. Any failed transactions are discarded.
Reason:
A CLOSE console command was received and processed by DBCDRPR.
Action:
None. This message is for information only.
Reason:
DBCDRPR is processing a console command that requires an operand. The operand is not valid or is not appropriate for the console command.
Action:
The command is ignored and processing continues.
Reason:
DBCDRPR was calculating throughput timing. The calculations yielded a negative number which implies either the sender’s or the receiver’s system clock is not set correctly.
Action:
This message is issued only once to prevent flooding the SYSPRINT. The calculations for throughput should be considered invalid since the clocks are out of sync.
Reason:
DBCDRPR encountered more errors than the value of the ERRORCNT specified.
Action:
Processing terminates. If any transaction was in process, it is rolled back.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|