Please enable JavaScript to view this site.

SQD0001I

<message>

Generic self-described Informational message.

SQD0002E

(<#>) Invalid eye catcher found in <datastore>

Invalid eye catchers can happen when an agent reads from a datastore, but the data in the datastore does not match the expected CDC data as defined by the script. Possible causes: the agent is reading from the wrong location, or the datastore type is not correct. An input datastore can only contain records types that match the datastore type that is defined in the script. Remember to re-parse after any changes are made to the script.

SQD0003E

(<#>) Invalid parameter <name>

The specified parameter of the command being executed is invalid. Correct the parameter and try again. This message is typically accompanied by other messages indicating more details of the error.

SQD0005E

(<#>) <database> environment is not supported

The operating system on which the agent is running does not support the specified environment. For example, IMS is not supported in the UNIX operating system.

SQD0006I

(<#>) Invalid eye catcher (<eye_catcher>) found in the CDC queue <queue_name>

Invalid eye catchers can happen when an agent reads from a queue, but the data in the queue does not match the expected CDC data as defined by the script. Possible causes: the datastore type is not correct, or an unrelated process has written messages to the specified queue. A queue that is used as an input datastore can only contain records types that match the datastore type that is defined in the script. Remember to re-parse after any changes are made to the script.

SQD0006W

(<#>) Invalid eye catcher (<eye_catcher>) found in the CDC queue <queue_name>

Invalid eye catchers can happen when an agent reads from a queue, but the data in the queue does not match the expected CDC data as defined by the script. Possible causes: the datastore type is not correct, or an unrelated process has written messages to the specified queue. A queue that is used as an input datastore can only contain records types that match the datastore type that is defined in the script. Remember to re-parse after any changes are made to the script.

SQD0007E

(<#>) Error processing datastore <data_store_name>

The agent encountered an error when reading from or writing to the specified datastore. Possible causes: the datastore is opened for exclusive use by another program, the user does not have permission to access the datastore, or the access method is not allowed. For example, you cannot write to a read only file. 0n a z/OS system, ensure that the record length (LRECL), record format, and block size (BLKSIZE) are specified correctly.

SQD0009E

(<#>) Incorrect description type <description_type> is specified

The description type specified in the script does not match the description provided. For example, the description type is specified as SQLDML but the description contains relational DDL statements.

SQD0010E

(<#>) Communication IO error <error_code>

A TCP/IP communication error has occurred. Look up the specified error_code for problem determination and correction.

SQD0012I

(<#>) Record <record_alias>: <number>

This message displays the cumulative count of input messages for a specified record type. The message is produced when the REPORT EVERY threshold is reached.

SQD0013E

(<#>) Field <field_name> is not unique

Fields with the same name were found in more than one record of a datastore, or the same field name was in multiple datastores. The fields need to be further qualified. Remember to re-parse after any changes are made to the script.

SQD0014W

(<#>) Change Data Capture record contains invalid length (<value>)

The engine encountered a CDC record (IMS, DB2, or VSAM) with an invalid length value. Each CDC record contains a two-byte length value in the first two bytes of the record. This length value must be equal to the actual record length read. Possible causes: unrelated processes writing invalid data in the CDC queue, two CDC components of different releases may be writing messages of different formats to the queue, or the CDC records were altered after their original generation by another process.

SQD0015E

(<#>) Datastore alias <name> is not unique

The parse encountered more than one datastore with the same alias. Data store aliases must be unique.

SQD0016E

(<#>) Input file is parsed with a different release of the parser (<version>)

The engine tried to process a command file that was parsed by a different release of the Parser. Version denotes the release number of the Parser that parsed the command file being processed. You can determine the current release/build of the Integration Engine by viewing the run-time report of the Engine instance. Make sure that the Parser and Integration Engine are at the same release/build level. If you recently applied maintenance, make sure to re-parse your command scripts prior to running the Integration Engine.

SQD0017E

(<#>) Memory of size <value> cannot be allocated

The component could not allocate the memory required to complete processing. The size specified may be zero, or a negative number. In a z/OS system, a JCL REGION parameter may be required to ensure that the job running the component provides enough memory for use.

SQD0018E

(<#>) Data length |<length>| for < column> in < datastore > is expected to be < or = |<max_length>|.

A target field has a length that cannot hold the data being mapped to it. The target field may be improperly defined.

SQD0021E

(<#>) Data length |<length>| for <column> in <datastore> is expected to be < or = |<max_length>| (provided precision).

A target decimal field has a default or provided precision that cannot hold the data being mapped to it. The target field may be improperly defined.

SQD0022E

(<#>) Data length |<length>| for <column> in <datastore> is expected to be < or = |<max_length>| (provided scale).

A target decimal field has a default or provided scale that cannot hold the data being mapped to it. The target field may be improperly defined.

SQD0023E

(<#>) Divide by zero is not allowed

A divide by zero condition occurred when attempting to execute a divide (DIV) function. Make sure that the value(s) being used as the divisor in a DIV function is not zero. Remember to re-parse after any changes are made to the script.

SQD0025E

(<#>) No file name is specified

No datastore location is specified in the DATASTORE command. See the syntax for the DATASTORE command. Remember to re-parse after any changes are made to the script.

SQD0026E

(<#>) Invalid keyword <keyword>

An invalid keyword was used in either a parameter file, or at the command line. Consult the program’s documentation for the proper command line syntax.

SQD0027E

(<#>) Invalid value <value>

An incorrect value for a keyword was specified in either a parameter file, or at the command line. Consult the program’s documentation for the proper command line syntax.

SQD0028I

(<#>) Total number of input records processed: <number>

This is the count of the number of input records processed by the Integration Engine. The frequency of receiving this message is set by the REPORT command within the input command script.

SQD0029E

(<#>) Partner program ended prematurely

This error occurs while running across a TCP/IP communication port. One of the Integration Engine instances detected that a partner Engine instance is no longer operational. Check the message log for the partner instance that ended prematurely.

SQD0031E

(<#>) Datastore with alias <name> is not found

A reference to an unknown or undefined datastore alias name has been made. Check your script or control cards for errors.

SQD0032E

(<#>) No key column is specified for datastore <name>

A key field must be specified for the specified datastore.

SQD0033E

(<#>) Reference for segment <name> of database <name> is not found

During parse, a segment was specified in a DESCRIPTION command for a segment that could not be found in the corresponding DBD. For the integration Engine, an IMS CDC record, or an HSSR file record is found for an IMS segment that has not been referenced (mapped) in the command script.

SQD0033W

(<#>) Reference for segment <name> of database <name> is not found

During parse, a segment was specified in a DESCRIPTION command for a segment that could not be found in the corresponding DBD. For the integration Engine, an IMS CDC record, or an HSSR file record is found for an IMS segment that has not been referenced (mapped) in the command script.

SQD0035E

(<#>) Parser finished processing <file_name>

The Parser completed processing the specified command script file with error(s). Check accompanying error messages.

SQD0035I

(<#>) Parser finished processing <file_name>

The Parser successfully completed processing the command script file specified.

SQD0035W

(<#>) Parser finished processing <file_name>

The Parser completed processing the specified command script file with warning(s). Check accompanying warning messages.

SQD0036E

(<#>) Parse error in <file_name> on line <number>; token: <value>

This is the most common Parser error. The component encountered an error in the specified command script file on the specified line number. The token <token> denotes a keyword or symbol (comma, parenthesis, etc.) that caused or appears near were the error occurred. Check to make sure that there are no missing or extraneous punctuations (i.e. commas, semi-colons, or parenthesis). You may need to specify LIST=ALL to see the full parser listing with all occurrences of the specified line number. The Parser numbers each DESCRIPTION file starting at 1. It also numbers the command script from 1.

SQD0037E

(<#>) Description file is not specified

When a description is not provided in-line in the script, a physical name must be provided which indicates where the description is to be included from.

SQD0038E

(<#>) Parser terminated with errors on line <number>

The Parser encountered an error within the command script on the specified line. This message is generally issued in conjunction with another Parser message to assist with problem determination within the command script.

SQD0039E

(<#>) Unterminated string on line <number> in file <file_name>

The Parser has found a string with the starting single quote, but the ending single quote is missing. Remember to re-parse after any changes are made to the script.

SQD0040E

(<#>) Keyword <value> is not specified

The specified keyword is required. Consult the program’s documentation for the proper command line syntax.

SQD0040W

(<#>) Keyword <value> is not specified

The specified keyword is required. Consult the program’s documentation for the proper command line syntax.

SQD0041E

(<#>) Processing completed with return code <return_code>

The component finished processing with a return code indicating an error. A return code of 8 indicates a problem has occurred. Check accompanying error messages for more diagnostic information. Return codes greater than 8 indicate abnormal termination and may be followed by a series of numbers (a call-stack dump). One of the first calls should indicate which function/module that caused the abnormal termination. Contact support if a call-stack dump is generated.

SQD0041I

(<#>) Processing completed with return code <return_code>

The component issues this message to specify the processing return code. A return code of 0 indicates successful completion.

SQD0041W

(<#>) Processing completed with return code <return_code>

The component finished processing with a return code which indicates warning. A return code of 4 indicates a warning has occurred. Check accompanying warning messages for more diagnostic information.

SQD0042E

(<#>) Message too large for buffer (<number_1> bytes vs <number_2> bytes allocated)

An Integration Engine instance operating in conjunction with a partner Integration Engine using TCP/IP received more data than was expected from the partner Integration Engine. Number_1 indicates the number of bytes received and number_2 indicates the number of bytes expected. This error indicates that the description (structure) of the data being passed was not defined the same between the two (2) partner Integration Engines. Make sure that the descriptions are the same and retry the operation.

SQD0043E

(<#>) Datastore <alias> does not include description type CDCUOW

A datastore of type DB2CDC requires a description to the CDCUOW record and none was found.

SQD0044E

(<#>) Partner requested Rollback, terminating

An Integration Engine instance operating in conjunction with a partner Integration Engine using TCP/IP received a Rollback request. The data being updated by the Integration Engine is rolled back assuming the target datastore supports rollback operations. Determine why the sending partner Integration Engine issued a rollback to the datastore in which the sending partner was processing and retry the operation. If the problem persists, please contact Technical Support.

SQD0045E

(<#>) Performing user requested termination

A TERMINATE function was issued by the user during processing. All open datastores are closed and processing terminates with the return code specified as the parameter of the TERMINATE function.

SQD0045I

(<#>) Performing user requested termination

A TERMINATE function was issued by the user during processing. All open datastores are closed and processing terminates with the return code specified as the parameter of the TERMINATE function.

SQD0046E

(<#>) <Action> failed: Invalid partner response

An Integration Engine instance operating in conjunction with a partner Integration Engine using TCP/IP received the specified invalid action. Make sure that both of the Integration Engines are running and are on the same maintenance build level. If the problem persists, please contact Technical Support.

SQD0049E

(<#>) Record alias <name> is not found

Record alias not found warning message for XML, TEXT, and DELIMITED datatypes.

SQD0049W

(<#>) Record alias <name> is not found

Record alias not found error when record alias is required for the datastore type used.

SQD0052W

(<#>) No reference is found for record <name> in datastore <alias>

The Integration Engine encountered a record in a source datastore containing VSAM CDC records that it was not expecting because it had not been declared within the command script. If an exception datastore is specified, then the problem record will be written to that datastore. Otherwise, the Integration Engine will terminate with a return code of 8. Add a DESCRIPTION for this record and associate the DESCRIPTION with the source datastore (in the DATASTORE command).

SQD0053E

(<#>) Data type <type> is not supported for <column_name>

The table being accessed contains the specified column with specified data type that is not supported. If the specified data type is a valid data type, contact Support.

SQD0054E

(<#>) Key column <name> is not mapped

No data has been mapped to the specified key column field in the target datastore. Remember to re-parse after any changes are made to the script.

SQD0055E

(<#>) Parent segment <name> is not found

The DBD used for processing an IMS datastore specifies a child segment whose parent is either not specified or not found. Each parent segment up to the root must be described with the DESCRIPTION command, in order for a lower level segment to be found in the DBD. Remember to re-parse after any changes are made to the script.

SQD0056E

(<#>) File <file_name> did not open successfully

The specified file was not able to be opened. The file may be in use by another process or the process may not have permission to open the file in the mode requested (i.e. read, write, etc).

SQD0056W

(<#>) File <file_name> did not open successfully

The specified file was not able to be opened. The file may be in use by another process or the process may not have permission to open the file in the mode requested (i.e. read, write, etc).

SQD0057E

(<#>) Group item <name> cannot be mapped

Applies to the Normalization feature (NORM function). When normalizing source data records using the NORM function, a group item was mapped to the normalized target field(s). Only individual fields within the group item (repeating group or array) can be mapped to the normalized target fields. Remember to re-parse after any changes are made to the script.

SQD0061E

(<#>) Field <name> is not found

The specified field/column being referenced was not previously defined in the script. Note that a field can reference another object, such as a PROC within a function. In the latter case, since a reference cannot be found to the field, it assumes that it is a source or target field. Make sure that the field/column is spelled correctly, that you are using the correct datastore definition and the definition was specified earlier (i.e. before the reference is made) within the script.

SQD0061W

(<#>) Field <name> is not found

The specified field/column being referenced was not previously defined in the script. Note that a field can reference another object, such as a PROC within a function. In the latter case, since a reference cannot be found to the field, it assumes that it is a source or target field. Make sure that the field/column is spelled correctly, that you are using the correct datastore definition and the definition was specified earlier (i.e. before the reference is made) within the script.

SQD0062E

(<#>) Field <name> is not found in the datastore <name>

The specified field/column is not part of a DESCRIPTION that is related to a datastore through the DESCRIBED BY command. Also, make sure that the field/column is spelled correctly and that the field/column is correctly qualified.

SQD0063E

(<#>) No datastore is specified

At least two DATASTORES (source datastore and target datastore) need to be declared in the command script. For programs other than the parser, consult the program’s documentation for the proper command line/parameter file syntax.

SQD0064E

(<#>) Function <name> is not valid for datastore <name>

The specified function is not allowed for the specified datastore. Check the datastore’s type to see if it is compatible with the specified function. For example, if the function is IMSCDCOP, the datastore it references must be of IMSCDC type.

SQD0065E

(<#>) Hex number <number> does not contain enough digits

The Integration Engine attempted to execute an X2C function (hex to character) and found that the source hex field did not contain the correct number of digits to be properly converted. When using the X2C function, each hex digit expands to two character digits and the target field must be correctly sized to accept the converted string, an even number of digits. Remember to re-parse if changes are made to the script.

SQD0066E

(<#>) Hex number <number> is invalid

A hexadecimal number was found that contains characters other than 0-F (upper or lower case). This can be an indication of a corrupt source datastore or a record that is not properly aligned with the record layout specified. If an exception datastore is specified on the source datastore, the invalid record will be output in that datastore. Otherwise, the Integration Engine will terminate with a return code of 8. Check the description to make sure that it accurately represents the layout of the source datastore record. If it does, then you may have a problem with corrupt data in the source datastore that must be corrected in order to process the data.

SQD0067E

(<#>) An attempt to reposition file pointer for <datastore_name> to <position> failed

An error has occurred within the Integration Engine when processing a look-up datastore. The process unsuccessfully attempted to reposition an internal look-up pointer to a new record. The file (datastore) is probably corrupted. If after correcting the source datastore the problem persists, contact product support.

SQD0068E

(<#>) Datastore <name> does not support binary fields (column <name> is described as a binary)

Datastore type TEXT does not support binary type fields.

SQD0070E

(<#>) No PCBs found in the PSB supplied

The PSB specified for processing against an IMS datastore on z/OS does not contain any PCBs. Correct the PSB or specify another PSB that allows the correct access to the IMS database being processed.

SQD0071E

(<#>) PCB <db_name> not found in the PSB supplied

The database name specified is not present in the PSB. The database name must be the name of the PCB in the PSB. Specify a PSB that contains a PCB with the name of the IMS database being processed.

SQD0072E

(<#>) Invalid target operation type specified

The target operation (INSERT, REPLACE, etc.) specified is not valid for one of the target datastore types being processed.

SQD0073E

(<#>) Field <name> contains invalid data

A numeric field or a field specified in the EXTTYPE command contains non-numeric data. For example, a packed-decimal field may contain invalid digits. If an exception datastore is specified, the record containing this field is written to it. Otherwise, the Integration Engine terminates with return code 8. Check the record layout and insure that the correct layout is used. If the record layout is correct, added an INVALID command for this field to specify its processing (see the INVALID command for further description).

SQD0073W

(<#>) Field <name> contains invalid data

A numeric field or a field specified in the EXTTYPE command contains non-numeric data. For example, a packed-decimal field may contain invalid digits. If an exception datastore is specified, the record containing this field is written to it. Otherwise, the Integration Engine terminates with return code 8. Check the record layout and insure that the correct layout is used. If the record layout is correct, added an INVALID command for this field to specify its processing (see the INVALID command for further description).

SQD0074E

(<#>) Invalid datastore type is specified for <datastore_name>

An invalid datastore type is specified for the datastore <datastore_name>. See the DATASTORE command for a list of valid datastore types.

SQD0076E

(<#>) No field name is specified for search

A source or target field was specified in a command script, but the field is not defined for the datastore being accessed. Ensure that the field name is spelled correctly and that the field exists in the datastore description defined by the DESCRIPTION statement.

SQD0077E

(<#>) Invalid argument length <len> for < argument>

A given argument has an invalid length for its purpose.

SQD0079E

(<#>) Invalid number of parameters

The Integration Engine detected a function with the incorrect number of parameters for the function. Correct the function and re-parse the script.

SQD0081E

(<#>) IMS Error: <error_code>: Return Code = <return_code>

An IMS error occurred when issuing an IMS call. Refer to the IMS Messages and Codes manual.

SQD0084E

(<#>) Error converting character number <number> to packed or zone decimal

A character representation of a packed or zone decimal number is invalid. A decimal character number must contain digits 0 through 9. Optionally, it can contain a decimal point, and a sign character. Make sure that the record layout specified in the DESCRIPTION command is correct for the source datastore being processed. If the record layout is correct, you may need to alter the data in the source file before continuing. You can optionally use the INVALID command for the field containing the bad data to correct it.

SQD0086E

(<#>) Invalid logical value <logical>, value must be 0 or 1

A function requiring a logical/boolean parameter has encountered a value for this parameter that is not 0 or 1. Correct the function and re-parse the script.

SQD0087E

(<#>) Invalid date value <date>

Encountered an invalid date <date> passed as a parameter to one of its functions, or in one of the source fields. Make sure that the datastore definition is correct for the datastore(s) being processed, and that the correct function parameters are used.

SQD0088E

(<#>) Invalid date value <date>

Indicates an invalid date.

SQD0089E

(<#>) Invalid time value <time>

Indicates an invalid time.

SQD0090E

(<#>) Invalid month value <month>

The month value is not valid. There is a possibility that this value is non-numeric. Correct the month value and rerun the Integration Engine.

SQD0091E

(<#>) Invalid week number <number>

The week number must be within the range from 1 to 54. You can have two half weeks, one at the beginning of the year, and the other at the end of the year. Correct the week value and rerun the Integration Engine.

SQD0092E

(<#>) Invalid time <value> The value for time must be formatted as HHMMSS

The time value is not valid. Correct the time value and rerun the Integration Engine.

SQD0093E

(<#>) Invalid time <value> The value for HH must be between 0 and 23

The hour portion of the time must be between 0 and 23, inclusive. Correct the time value and rerun the Integration Engine.

SQD0094E

(<#>) Invalid time <value> The value for MM must be between 0 and 59

The minute portion of the time value must be between 0 and 59, inclusive. Correct the time value and rerun the Integration Engine.

SQD0095E

(<#>) Invalid time <value> The value for SS must be between 0 and 59

The seconds portion of the time value must be between 0 and 59, inclusive. Correct the time value and rerun the Integration Engine.

SQD0097W

(<#>) Log data for <type> ID <value> is excluded

DB2 capture has excluded data based on the correlation id or authorization id displayed.

SQD0099E

(<#>) Invalid integer number <value>

A character representation of an integer number contains invalid characters. One or more of the characters are non-numeric. Ensure that the parameters passed to the functions provide correct values to these functions.

SQD0100E

(<#>) Invalid function parameter value <parameter>

A function has encountered a parameter with an invalid value. This message is followed by the message SQD0136E stating the function in error, and the parameter number containing the invalid value. Correct the value passed to the function and rerun the Integration Engine.

SQD0101E

(<#>) Invalid decimal number <value>

There is an error in what is defined as a decimal number. There are either non-numeric bytes in the field, too many decimal points, or spaces followed by something else at the end of the field.

SQD0102E

(<#>) Invalid number <value>

There is a conflict with the way the scale (digits to the right of the decimal point) of a number was defined. The data value does not match the scale defined.

SQD0104E

(<#>) SQL Error: Return Code = <return_doe>

A SQL Error occurred while processing a relational datastore using an ODBC driver. Check the SQL return code against the messages and codes for the relational database management system being accessed, correct the error and rerun the Integration Engine.

SQD0105E

(<#>) SQL Error: <error_code>: Return Code = <return_code>

A SQL Error occurred while processing a relational datastore using the DB2 driver. This message may be followed by several diagnostic messages listing the statement in error, as well as the data that has caused the error. Correct the problem and rerun the Integration Engine.

SQD0105I

(<#>) SQL Error: <error_code>: Return Code = <return_code>

A SQL Error occurred while processing a relational datastore using the DB2 driver. This message may be followed by several diagnostic messages listing the statement in error, as well as the data that has caused the error. Correct the problem and rerun the Integration Engine.

SQD0106E

(<#>) Invalid component call

A call to one of the drivers is not valid. The driver component number is listed in the prefix portion of the message. This is an unrecoverable internally used error. Contact support.

SQD0111E

(<#>) Invalid command <command>

An invalid command is specified in the command script file. Make sure that the command was specified and spelled correctly and rerun the Parser.

SQD0112E

(<#>) COBOL item level <number> is invalid for <name>

An invalid level number in a COBOL copybook is encountered. Valid levels are 1 to 49, inclusive. Adjust the COBOL copybook to reflect the valid level(s) and re-run the Parser.

SQD0114E

(<#>) Description <name> is not specified

A datastore description specified in the DESCRIBED BY clause of a DATASTORE command was not defined. A DESCRIPTION command must be specified ahead of the DATASTORE command that defines the description alias this datastore references. Make sure that the datastore is defined using the correct description alias. Correct the error and rerun the Parser.

SQD0115W

(<#>) No target datastore is specified

A datastore description specified in the DESCRIPTION command did not find the matching DATASTORE command. Make sure the DESCRIPTION and DATASTORE commands are in sync.

SQD0116E

(<#>) COBOL item <name> is in error

There is a problem with the definition of the COBOL item listed. Review and correct the COBOL definition and reparse.

SQD0118E

(<#>) Substitution parameter for placeholder <number> is not specified

The Parser expects to have at least as many substitution parameter placeholders as there are command parameters passed to it. The command script contains a substitution variable (%nn) that does not have a corresponding parameter. Correct the error and rerun the Parser.

SQD0119E

(<#>) Column <name> does not allow NULL data

The specified column does not allow NULL data to be input. If the target definition correctly specifies NOT NULL then it may be necessary to specify an INVALID or IFNULL field specification to correct the data before the update is attempted.

SQD0120E

(<#>) Invalid number of parameters in function <name>

The Parser component detected a function with the incorrect number of parameters. Correct the function and rerun the Parser.

SQD0121E

(<#>) No identifier is specified for record number <value>

This error applies to file source datastore types that contain multiple record types. An IDENT command was not specified for one of the record types just read. Specify an IDENT command for all record types in the source datastore and try the operation again.

SQD0121W

(<#>) No identifier is specified for record number <value>

This error applies to file source datastore types that contain multiple record types. An IDENT command was not specified for one of the record types just read. Specify an IDENT command for all record types in the source datastore and try the operation again.

SQD0122E

(<#>) MQSeries function <name> ended with <return_code> for <datastore_alias>

The specified IBM MQ function ended with specified reason code for the specified datastore. The reason code is the IBM MQ reason code for the function specified. Check the IBM MQ Messages and Codes manual for more specifics.

SQD0123I

(<#>) End-of-data message is issued for queue <queue_name>

A queue term has been issued at your request.

SQD0124E

(<#>) IBM MQ function <name> ended with <value>

The specified IBM MQ function ended with specified reason code. The reason code is the IBM MQ reason code for the function specified. Check the IBM MQ Messages and Codes manual for more specifics.

SQD0125E

(<#>) Record <name> in datastore <name> contains <number> fields vs <number> fields

The specified delimited datastore described by the specified record does not have the same number of fields that were specified in the corresponding DESCRIPTION command for the file/datastore. This may occur if a delimiter character is specified that is found in the source datastore data. Correct the definition of the input datastore to match the correct number of fields. If the number of fields is correct and this error is due to the delimiter character found in a source field, change the delimiter character in the DATASTORE command for this datastore, re-parse the script and rerun the Integration Engine.

SQD0126I

(<#>) Exception datastore < datastore_name> is generated

Informational message that indicates that the specified Exception Datastore was first used at this point.

SQD0126W

(<#>) Exception datastore <name> is generated

Warning message that indicates that the specified Exception Datastore was first used at this point.

SQD0127E

(<#>) No more than <number> SQL statements can be prepared

The maximum allowable number of SQL statements has been exceeded.

SQD0128E

(<#>) Key field <value> must be a DBD field

The Parser component detected a field used as key that is not a DBD field. IMS only recognizes segment fields listed in the DBD for a segment. Since a key field is used to construct an IMS SSA, it must be a field found in the DBD for the segment being accessed. Specify a field name found in the DBD to be considered the search key.

SQD0129I

(<#>) Error message is issued for queue <queue_name>

The engine has read a message from the queue that a partner program may have written in the queue to indicate an unrecoverable error. Encountering this message causes the engine to terminate with return code 12. The partner program may have issued messages that can aid you in resolving the problem. Correct the error in the partner environment and rerun both programs.

SQD0130E

(<#>) RDBMS connect information is missing or invalid

No connect information is provided for relational databases that require it. Specify the correct connection information in the RDBMS command, re-parse the command script, and invoke the engine.

SQD0131E

(<#>) Number of log queues exceeds <number>

This message is issued if the number of log queues specified when DB2 tables are defined for propagation exceeds the number shown. See the Replication Guide for the description of DB2 CDC log queues and their use. To reduce the number of queues combine the changes for two or more DB2 table into one queue.

SQD0132W

(<#>) No active table found in <table_name> to process

Either the DB2 propagation registration table contains no rows, or none of the tables defined for propagation are activated in the registration table. See the Replication Guide for the description of DB2 CDC log queues and their use. Activate at least one table in the registration table and restart the DB2 CDC agent.

SQD0133E

(<#>) <command> completed with X'<return_code>':X'<message>'

A DB2 call ended with the specified return and reason codes. Both the return code and reason code are listed in hex. The DB2 call is also listed. See DB2 messages and codes for the description and resolution to the problem. If the return code and reason code values are zeros, no error has occurred.

SQD0133I

(<#>) <command> completed with X'<return_code>':X'<message>'

A DB2 call is found to have caused an error. Both the return code and reason code are listed in hex. The DB2 call is also listed. See DB2 messages and codes for the description and resolution to the problem. If the return code and reason code values are zeros, no error has occurred.

SQD0134E

(<#>) Unable to allocate memory for SQLDA

An error occurred when the engine attempted to allocate memory for the required SQLDA. This message is issued from the Oracle native driver. This may be a system error, or it may be caused by lack of memory at the time the engine is invoked. Check with your UNIX or Oracle administrator to correct the problem.

SQD0135W

(<#>) No reference is found for table |<name>|

The engine has encountered a table name in the Change Data Capture data whose information is not specified in the engine script. Either add ACCEPT ALL to the source Datastore to bypass CDC records for this captured source table or add a DESCRIPTION for this table to the engine script along with the control and processing logic required for your intended target. Re-parse the command script, and invoke the Integration Engine.

SQD0136E

(<#>) Error encountered in function <name>, parameter <number>

The function was passed a parameter specified by the parameter number that was invalid. Correct the parameter in the command script, re-parse the command script, and invoke the Integration Engine.

SQD0137E

(<#>) <log_datastore_name> is not registered

The asynchronous capture JCL needs two DD cards that both reference the same IMS log dataset name. Make sure SQDLOGDS and SQDLOGNM are both referencing the same dataset name.

SQD0139W

(<#>) No log data set qualifies for processing

Based on the selection criteria specified in the IMS async job there are no log datasets that meet the specified criteria to be processed.

SQD0140I

(<#>) <log_datastore_name> has already been processed

The specified log datastore is older than the current logpoint specified.

SQD0141E

(<#>) Substitution parameters must be consecutive

Substitution parameters must be specified consecutively starting with %00.

SQD0142E

(<#>) <option> requires parameter (<option>=parameter)

The specified parameter in the format shown is required for proper parsing of this command.

SQD0143E

(<#>) -<option> requires parameter (-<option> parameter)

The specified parameter in the format shown is required for proper parsing of this command.

SQD0144E

(<#>) Invalid parameter <value> for <option>

The value specified for the listed option is not valid.

SQD0145E

(<#>) Too many arguments

Too many arguments have been specified for the function executed. Correct the input and retry.

SQD0146E

(<#>) Invalid parameter -<value>

The value specified for the parameter is not valid. Correct and retry.

SQD0147E

(<#>) Not enough arguments

There have not been enough arguments specified for the function executed. Correct the input and retry.

SQD0148E

(<#>) Error in <contex>: <return_code> (<error_information>)

System error in the specified function. Ended with the specified return_code and error information.

SQD0149E

(<#>) Limit of <number> reached when processing <object>

The maximum allowable number has been exceeded for the listed object.

SQD0152E

(<#>) Restart datastore is missing for <datastore_name>

The restart datastore specified in the JCL can not be found.

SQD0153E

(<#>) JOBNAME is missing

The JOBNAME is missing from the supplied JCL.

SQD0155E

(<#>) Invalid CDC record.

One of several things could be wrong with the CDC record processed. The header information for the record does not match the CDC data itself.

SQD0157E

(<#>) Operation <operation> not supported by a datastore of type <type>.

The specified operation is not support in this context due to the specified type.

SQD0159E

(<#>) Input file is parsed with a older release of the parser.

The engine tried to process a command file that was parsed by an older release of the Parser. Reparse your script, using the version of the parser associated with the engine you are trying to execute.

SQD0160E

(<#>) Not Enough Arguments for Printf.

The format of a PRINTF or FPRINTF function call has more variables/place-holders in it than the number of arguments provided.

SQD0161E

(<#>) Invalid formatting %%<spec>.

Invalid formatting specification in Printf format.

SQD0200E

Invalid Input DS:<datastore_alias> REC:<record_alias> FLD:<field_name> (<type>) error:<error_code> (<error_string>)

SQD0200W

Invalid Input DS:<datastore_alias> REC:<record_alias> FLD:<field_name> (<type>) error:<error_code> (<error_string>)

The specified field does not conform to the user provided description.

SQD0301I

(<#>) <shutdown_level> SHUTDOWN COMPLETE RC=<reason_code>

This message is issued when the Master Engine Controller or Started Task Controller is stopped by the user. The shutdown_level will be FORCED if the stop command was issued with the force option (STOP FORCE) or when any stop command is issued from the operator’s console. Otherwise, the shutdown_level will be NORMAL.

SQD0302I

(<#>) <command> COMMAND ACCEPTED (<command_origin>)

This message is issued when a valid command is issued to and accepted by the Master Engine Controller or Started Task Controller. The origin of the command will be one of the following:

OPER - the command was entered from the operator’s console

WTOR - the command was issued by replying to the outstanding WTOR message for the Master Engine or Started Task Controller. This will apply only if WTOR=Y is specified in the start-up parameter file.

MQ - the command was received from the IBM MQ command queue identified by the CMDQUE keyword in the start-up parameter file. The MQ origin is only applicable to the Master Engine Controller.

SQD0303E

(<#>) IBM MQ ERROR REASON=<reason_code>

An IBM MQ error was encountered with the connection to the IBM MQ Queue Manager or while processing the IBM MQ queue. The IBM MQ reason code identifies the error that occurred. If the IBM MQ reason code is not connection related, the process continues. Otherwise, the process is terminated. Refer to the IBM MQ Messages and Codes documentation to determine the meaning of the reason code and correct the IBM MQ error.

SQD0304E

(<#>) PROCESS UNEXPECTED SHUTDOWN RC=<return_code>

During shutdown, it was determined that one or more of the Integration Engine sub-tasks did not terminate normally. The return_code denotes the highest return code level of the terminated Engine sub-tasks. If you are running the Master Engine Controller, message SQD0308E would have been previously issued indicating which of the Engine sub-tasks had an unexpected shutdown. Review the report output of the Engine sub task in question to determine why it did not terminate normally.

SQD0305E

(<#>) UNABLE TO OPEN STARTUP FILE <startup_file> PROCESS ENDED

During initialization, the Master Engine Controller or the Started Task Controller was not able to open the dataset specified in the startup file statement. The process is terminated. Make sure that you have the SQDPARM DD statement allocated in the JCL stream for the Master Engine Controller or the Started Task Controller. Also ensure that the dataset specified in the SQDPARM DD statement is a valid z/OS partitioned dataset with the member explicitly identified.

SQD0306E

(<#>) INVALID <keyword> KEYWORD FOUND IN PARM

During initialization, the Master Engine Controller or the Started Task Controller detected either an invalid keyword in the startup parameter file or a keyword that was out of sequence in the parameter file. The keyword indicates the invalid specification. The process is terminated. Check the startup parameter file to make sure that the keyword is spelled correctly and that all of the keywords are specified in the order expected by the Master Engine Controller or the Started Task Controller. Information regarding the startup parameter keywords can be found in the V4 Utility Reference.

SQD0307E

(<#>) STARTUP PARAMETER FILE INCOMPLETE

During initialization, the Master Engine Controller or the Started Task Controller detected that the startup parameter file was incomplete. This occurs within the Engine Sub-task Specification section of the parameter file. The process is terminated. Check the startup parameter file to make sure that the required keywords for each of the Engine sub-tasks are specified. Information regarding the startup parameter keywords can be found in the V4 Utility Reference.

SQD0308E:

AGENT <nn> <name> UNEXPECTED SHUTDOWN

This message is issued when an agent controlled by the z/OS master controller terminates unexpectedly with a non-zero return code. It will not be issued as a result of a master controller stop or purge command. It may be issued for any task controlled by that master, i.e., a capture, publisher, or an apply engine. The nn denotes the occurrence number, and name the value of the NAME keyword of the agent sub task as specified in the startup parameter file.

SQD0308I

(<#>) ENGINE <engine_name> <engine_number> STARTING

This message provides the current status of the Engine sub task(s) during initialization, when the START command is issued for an Engine, or when the DISPLAY command is entered. The engine_number denotes the occurrence of the Engine sub task as it was specified in the startup parameter file and the engine_name represents the Engine sub-task name as specified in the NAME keyword of the parameter file.

SQD0310E

(<#>) COMMAND <command> NOT RECOGNIZED

A command was issued to the Master Engine or Started Task Controller, but it was not recognized as a valid command. The command is ignored and processing continues. Reissue the command, making sure that it is spelled correctly and is valid for the component for which it is being issued.

SQD0312E

(<#>) FAIL JCL MEMBER <member_name> NOT FOUND

The JCL member name listed could not be found.

SQD0314I

MASTER ENGINE CONTROLLER INITIALIZED

Informational message to indicate that the Master Controller has been initialized.

SQD0400E

IO errorno=<number>, lastop=<number>, syscode=<number>, rc=<return_code>

Mainframe I/O issue. Use the displayed information to investigate the issue.

SQD0401E

SVC99_Info=<number>, SVC99_error=<number>

Mainframe I/O issue. Use the displayed information to investigate the issue.

SQD0402E

<message>

Mainframe I/O issue. Use the displayed information to investigate the issue.

SQD0403E

Source or target must be a Queue

The source or target specified must be a Queue.

SQD0404E

Password for datastore <datastore_name> is not specified

The password for the specified datastore has not been provided.

SQD0405E

User ID / Password for datastore <datastore_name> is not specified

The user id and password for the specified datastore has not been provided.

SQD0411E

Unclosed comment

This is a parser error. There is a multi-line ( / followed by * ) comment without a matching close ( * followed by / ).

SQD0412W

Backup registration file will be used

For some reason the primary registration file is corrupt or invalid and the backup registration file will be used.

SQD0413W

A new registration file will be generated

The registration file was found to be empty or corrupt so a new one is being created.

SQD0414W

Registration file <name> may be corrupted

Warning message indicating that the current registration file was found to be corrupt.

SQD0415W

Problem processing datastore <datastore_name>

Generic warning message indicating an ODBC driver related error.

SQD0418I

End of file is reached for <file_name> in job <job_name>

In the job listed the end of file marker was reached in the specified file.

SQD0419I

UR reference table is generated

Informational message indicating the table containing the Unit of Work in the process logfile has been created and sorted.

SQD0420I

The Queue <queue_name> appears full, will retry in 30 seconds

This message indicates that we tried to write to an MQ queue but it was full. After a few second delay the write will be retried. If it fails again then the write will be deemed unsuccessful.

SQD0421E

(<#>) Input for decimal column <colname> contains invalid data: |<data>|

An error occurred while trying to pack a string representing a packed-decimal.

SQD0422E

(<#>) Get Value for column <colno> (<colname>) of record <recname> failed with rc=<rc>

An error occurred while retrieving a value for the given column.

SQD0423E

The Datastore <ds_alias> in not an Output Datastore (<context>)

This message indicates that the given datastore is not an output datatore which is required for the given context. Some functions require an output datastore as an argument.

SQD0424E

The type of Datastore <ds_alias> in not supported in this context (<context>)

This message indicates that the type of the given datastore is not supported in the indicated context. Some functions only apply to some specific types of datastores.

SQD0500I

(<#>) <capture_agent_id> <build_level> IMS CDC INITIALIZED

This message occurs when an IMS changed data capture agent is initialized. You will see this message only if the INITMSG in the SQDXPARM control module is set to Y. The capture_agent_id is the name of the data capture agent module and the build_level denotes the current maintenance level of the data capture agent. SQD0515I will accompany this message indicating the generation date of the SQDXPARM control module.

SQD0501W

(<#>) IMS CDC DISABLED FOR: <database_name> <segment>

The IMS data capture exit was disabled due to an error writing changed IMS data into one (1) of the output CDC datastores. This is the result of the auto-disable feature being enabled (AUTODSBL = Y) in the SQDXPARM control module. SQD0512W should follow this message indicating the reason for the data capture being disabled. If this message occurs, you have lost some changed data for the IMS database/segment and you should take appropriate recovery action. You can perform a full data refresh or use the Asynchronous IMS Data Capture component to recapture the data if you are also writing changed data records to the IMS recovery log. If you want to make sure that all data changes are to be captured, even if it means that the IMS transaction terminates abnormally if there is an error, you should deactivate the auto-disable feature in the SQDXPARM control module.

SQD0502W

(<#>) CDC DISABLED DEST=<destination> SSID=<subsystem_name>

The IMS Logger exit was disabled due to an error writing changed IMS data into one (1) of the output CDC datastores. This message is followed by message SQD0513W or SQD0514W indicating the reason for the data capture being disabled. The destination is either VSAM or MQ and the subsystem_name identifies the IMS control region executing the data capture agent. Please note that the auto-disable feature for the data capture agent is always active due to the potential impact to the entire IMS subsystem in the event of an output CDC datastore write error. If this message occurs, you have lost some changed data for the IMS database/segment and you should take appropriate recovery action. You can perform a full data refresh or use the Asynchronous IMS Data Capture component to recapture the data if you are also writing changed data records to the IMS recovery log.

SQD0503I

(<#>) CDC BYPASSED FOR PROGRAM <program_name>

The IMS Data Capture Exit was instructed to ignore the capture of changed data for the specified batch program by an EXCLUDEPGM specification in the SQDXPARM control module. The batch program can be either a BMP or DL/I batch job. Please note that the auto-disable feature for the data capture agent is always active due to the potential impact to the entire IMS subsystem in the event of an output CDC datastore write error. If you want to capture data changes made by this batch program, remove the EXCLUDEPGM specification from the SQDXPARM control module.

SQD0504I

(<#>) <cdc_type> CDC RESUMED TO <destination> DESTINATION

The capture of changed data has been resumed after being previously auto-disabled due to an error in writing changed data to one (1) or more output datastores. This indicates that the error that caused the auto-disable has been resolved.

SQD0505I

(<#>) OBJ = <object_name>

This message will be accompanied by one of several other error messages. This message indicates the object (queue, file, etc.) being referenced by the other message.

SQD0506I

(<#>) <capture_agent_id> <build_level> IMS CDC ENDING

This message occurs during the IMS control region shutdown process and indicates that the IMS Logger exit has just completed its termination activities.

SQD0507E

(<#>) <capture_agent_id> <build_level> IMS DATA CAPTURE ERROR

The data capture agent was disabled because an invalid SQDXPARM control module was linked with the data capture agent. This message is accompanied by message SQD0519E with further information.

SQD0509W

(<#>) VSAM CDC DISABLED FOR FILE: <file_name>

The VSAM Data Capture agent was disabled due to an error writing changed data into one (1) of the output CDC datastores. This is a result of the auto-disable feature being enabled (AUTODSBL = Y) in the SQDXPARM control module. This message is followed by SQD0513W or SQD0514W, which indicates the reason for the data capture being disabled. The file_name identifies the DD name of the source VSAM file whose changes were not written to the output CDC datastore. If this message occurs, you have lost some changed data for the VSAM file and you should take appropriate action to recover the data such as performing a full data refresh to the target. If you want to make sure all the data changes are captured, even if it means that the IMS transaction terminates abnormally if there is an error, you should deactivate the auto-disable feature in the SQDXPARM control module.

SQD0512E

(<#>) <capture_agent_id> <build_level> VSAM DATA CAPTURE ERROR

The VSAM data capture agent was disabled because an invalid SQDXPARM control module was linked with the data capture agent. This message is accompanied by message SQD0519E with further information.

SQD0513W

(<#>) VSAM <function> ERROR DD:<ddname> RC <rc_reason>

This message provides the specific information on why the data capture agent went into auto-disable mode when trying to process changed data into the VSAM output CDC datastore. The function indicates the VSAM operation being executed such as an OPEN or WRITE. The ddname is the DD of the VSAM CDC output datastore. The rc_reason is the return and reason code of the VSAM I/O error. Refer to the DFSMS Macro Instructions for Data Sets chapter in the VSAM Macro Return and Reason Codes documentation to analyze the codes.

SQD0514W

(<#>) MQ ERROR DURING <function> RC-REASON:<reason>

This message provides the specific information on why he data capture agent went into auto-disable mode when trying to process changed data into an IBM MQ queue output CDC datastore. The function indicates the IBM MQ operation being executed such as CONNECT, OPEN or PUT. The reason is the reason code returned from the failed IBM MQ operation. Refer to the IBM MQ Messages and Codes doc to analyze the codes.

SQD0515I

(<#>) → SQDXPARM GENDATE: <date> <time>

This message provides the date YYYY-MM-DD and time HH:MM:SS that the SQDXPARM control module was generated.

SQD0516I

(<#>) → TRANSIENT <type> <name> SUCCESSFUL

This message indicates that the type (queue or file) of the name provided opened successfully.

SQD0517I

(<#>) CMIT PG: <program_name> DB: <database_name> CT: <commit_freq>

This message is issued for DL/I batch programs when auto-commit is enabled (AUTOCMIT=Y) in the SQDXPARM control module. Each occurrence of this message indicates that the auto-commit threshold (CMITFREQ) was exceeded by the batch program. The program_name is the name of the DL/I program that triggered the auto-commit event, database_name is the source IMS database being captured, and commit_freq is the number of messages written to one or more output CDC queues.

SQD0518I

(<#>) CMIT PG: <program_name> FL: <file_name> CT: <commit_freq>

This message is issued for batch programs when auto-commit is enabled (AUTOCMIT=Y) in the SQDXPARM control module. Each occurrence of this message indicates that the auto-commit threshold (CMITFREQ) was exceeded by the batch program. The program_name is the name of the program that triggered the auto-commit event, file_name is the DD name of the source VSAM file in which changed data was being captured, and commit_freq is the number of messages written to one or more output CDC queues.

SQD0519E

(<#>) → INVALID SQDXPARM MODULE DETECTED

The data capture agent was disabled because an invalid SQDXPARM control module was linked with the data capture agent. This message is accompanied by message SQD0507E or SQD0512E indicating that the data capture agent was disabled. Correct the problem, regenerate the SQDXPARM control module and relink the data capture agent. The following conditions can result in an invalid SQDXPARM control module being detected:

The version of the SQDXPARM control module generation utility was not at the release level required by the data capture agent.

The TYPE= keyword in the control module is not compatible with the data capture agent (TYPE=IMS for a VSAM data capture agent).

An error occurred in the generation of the control module and the subsequent link-edit with the data capture agent.

SQD0520I

EXIT SQDAREQC SUCCESSFULLY ENABLED

This message occurs when the CICS/VSAM data capture agent has been successfully initialized and is ready to start capturing changed VSAM data in your CICS subsystem. This message is accompanied by message SQD0515I, which indicates generation date of the SQDXPARM control module.

SQD0521E

EXIT SQDAREQC ENABLE FAILED - INVEXITREQ

This message occurs when the CICS/VSAM data capture agent did not initialize successfully due to a CICS invalid exit request. You must enable the CICS/VSAM capture agent as a CICS exit using the CECI command as follows:

CECI ENABLE PROGRAM(SQDAREQC) EXIT(XFCREQC) GAL(4096) START

SQD0522I

CDC BYPASSED FOR DLIBATCH PROGRAMS

For the IMS MQ capture agent, changed data capture was disabled for all IMS DLI/Batch programs because the DLICAP parm was set to N in the XPARM control module. If you want to capture changes made by DLI/Batch programs using the IMS MQ capture agent, set DLICAP to Y and regen the XPARM.

SQD0523I

CDC BYPASSED FOR IMS BMP REGIONS

For the IMS MQ capture agent, changed data capture was disabled for all BMP programs because the BMPCAP parm was set to N in the XPARM control module. If you want to capture changes made by BMP programs using the IMS MQ capture agent, set BMPCAP to Y and regen the XPARM.

SQD0524I

CDC BYPASSED FOR IMS MESSAGE REGIONS

For the IMS MQ capture agent, changed data capture was disabled for all transactions that originated through a dependent message region (MPR) because the MPRCAP parm was set to N in the XPARM control module. If you want to capture changes made by message region transactions using the IMS MQ capture agent, set MPRCAP to Y and regen the XPARM.

SQD0525I

CDC BYPASSED FOR IMS FASTPATH REGIONS

For the IMS MQ capture agent, changed data capture was disabled for all transactions that originated through a Fastpath region (FPR) because the FPRCAP parm was set to N in the XPARM control module. If you want to capture changes made by Fastpath transactions using the IMS MQ capture agent, set FPRCAP to Y and regen the XPARM.

SQD0526I

CDC BYPASSED: GLOBAL DISABLE SPECIFIED

The capture agent was globally disabled from capturing any changed data because the DISABLE parm was set to Y. In order to turn off global disable, set DISABLE to N and regen the XPARM.

SQD0527W

IMS CDC DISABLED - CDC DATASET BLANK

The CDC dataset was not set properly for the IMS capture process. Provide the correct dataset information and restart the process.

SQD0545E

AIB INQY ERROR 00000100 0000000C

An error occurred while processing an AIB Inquiry (INQY) call to request information regarding the IMS environment.

SQD0599I

(<#>) <user_wto_message>

This message is issued when an auto-disable event occurred in a data capture agent and there was a user specified value user_wto_message in the AUTOWTO keyword within the SQDXPARM control module.

SQD1000I

<message>

The SQD1000I message is issued by the Integration Engine when the OUTMSG function is executed.

SQD1001E

Bad 9904 record, CapD without DEH(Data Element Header) 10

Error extracting captured data from IMS log. Contact support for help.

SQD1002E

(<#>) Invalid data captured for table <table_name> at origin SCN <number>

Captured data is invalid for the given table. It is possible that the table description in the script does not match the captured data. Evaluate the table description for errors.

SQD1003E

(<#>) Invalid restart record too short (<size>) in <datestore_name>

Invalid restart record. This can happen if the restart dataset is restored improperly.

SQD1004I

Waiting for <dsname> to become available (< errno>)

Error opening the specified IMS batch-log dataset. It is presumed that this is because the batch process is not quite finished yet. The open will be retried regularly until the file becomes available.

SQD1005I

Opened <dsname>

This indicates that an IMS batch-log dataset that was at first not available for open, became available.

SQD1006E

Invalid record version for table <table_name> (ALTER TABLE since last capture start?)

A record image for the given table has a format that is not consistent with what the capture expects the table format to be. This can occur if you altered a table after the start of the capture agent, and a row with the new row format appears in the log. This can also occur if you have dropped a captured table after the capture has started and a subsequent create table has stolen the dbid, obid of the dropped table.

SQD1007E

NULL argument is not allowed

A function was given a NULL argument, and the function does not support such arguments.

SQD1008E

Function: <function_name> requires an active record being mapped

The function requires an active record and none are active.

SQD1009I

Stop-Flush received: <comment>

A Stop-flush message was received with the associated comment.

SQD1010I

Reconnected to <url>

A Reconnection requested by a capture was successful.

SQD1011I

Table <table_name> Refresh started

A Refresh request for source Db2/z table listed has been initiated.

SQD1012E

Table <table_name> from record <rec_alias> has no defined keys and no primary keys were found

The table listed requires a key and it has no primary key defined, and no KEY IS clause in the datastore or description section was found.

SQD1014I

Refresh started at <time started> end received at <time finished> Refresh for Table <table_name> Done with <number of> records sent in <number of> slices

Completed Refresh request statistics for source Db2/z table listed.

SQDA001E

Invalid option: <option>

The indicated command-line option is not valid.

SQDA001I

Job Name : <job_name>

Informational message to indicate the job name.

SQDA002E

Ambiguous option: <option>

The indicated command-line option is ambiguous, there is more than one option that is a partial match for the specified option.

SQDA002I

Parsed On : <date>

Informational message to indicate when the script was parsed.

SQDA003E

Option <option> requires an argument

The indicated option requires an argument, which is missing.

SQDA003I

Parsed on version : <parse_version>

Informational message to indicate with which version the script was parsed.

SQDA004E

Option <option> does not allow arguments

The indicated option does not take an argument, but one was specified.

SQDA004I

Parser sha1 : <parse_git>

Informational message to indicate with which version the script was parsed.

SQDA005E

Error processing argument ddn <ddname> rc=<return_code>

An error occurred while opening or loading the argument ddn.

SQDB001E

Error processing batch data into table <table>, stmt:|<statement>|

An error occurred during the asynchronous batch processing of a lot of records for the given table.

SQDB002E

Error renaming <filename> into <filename> errno:<system_error>(<system_error_string>)

An error occurred renaming work files.

SQDB003I

Recovering Staged work for <filename>

Staged work from a previous run was detected, recovering it. This is a batch of work that was queued to be processed, but the previous job terminated before it was actually applied.

SQDB004I

Recovering Staging work for <filename>

Staging work from a previous run was detected, recovering it. This is work that was pending being queued while the previous run stopped.

SQDB005I

Flushing batch tasks for <datastore>

On regular stop the engine will synchronously flush all pending batch tasks.

SQDB006I

Flushed batch tasks for <datastore>

Flushing of the batch tasks associated with the datastore is finished.

SQDC000I

<message>

Generic informational message.

SQDC001E

Invalid command line: <invalid_input>

The command line is invalid. Verify that the correct input has been given. Consult the program’s documentation for the proper command line syntax.

SQDC002E

Invalid option: <invalid_option>

The command line is invalid. Verify that the correct options and arguments have been given. Consult the program’s documentation for the proper command line syntax.

SQDC003E

Invalid parameter for option <option> : <invalid_parameter>

Invalid command line parameter. Verify that the correct parameter has been given. Consult the program’s documentation for the proper command line syntax.

SQDC004E

Fatal Error detected in module (<module>), rc=<rc>

A fatal error has occurred. Contact support for help.

SQDC005E

<error>

Generic Error. See the message itself for explanations. This is usually triggered by the grammar parser or error in exit at run-time.

SQDC006i

Starting at <filename> (<line>:<column>)

Reading the specified file starting at the specified line and column.

SQDC007i

Ending at <filename> (<number>:<number>)

Reading the specified file ending at the specified line and column.

SQDC008i

In context: … <number>

Reading the context at the specified location.

SQDC009E

In file included from <location>

In file included from the specified location.

SQDC010I

In context: … <number> … <number>

Reading the context at the specified locations.

SQDC011E

Missing configuration filename

An argument which defines the configuration filename is missing. Consult the program’s documentation for the proper command line syntax.

SQDC012E

Too many arguments

There are too many arguments present on the command line. Consult the program’s documentation for the proper command line syntax.

SQDC013E

Duplicate argument: <argument>

The same argument appears twice on the command line. Remove one instance of the argument and try again.

SQDC014E

Missing mandatory parameter: <parameter>

The parameter specified is mandatory but is missing from the command line. Consult the program’s documentation for the proper command line syntax.

SQDC015E

Invalid action: <action>

The provided action (first parameter) is invalid. Consult the program’s documentation for the proper command line syntax.

SQDC016I

<Module>(pid=<pid>) terminated with Return Code <rc>, Reason Code=<reason> (<strerror>)

Execution of the program terminated with some conditions. This message should always be accompanied by another message that details what the problem is. This message is a catch all message to provide diagnostic information and can be disregarded if there are no other messages to explain the failure. If that were to happened, please contact for support.

SQDC017I

<Module>(pid=<pid>) terminated successfully

Informational message to inform you that the program terminated successfully.

SQDC018I

Usage:<command_line_syntax>

Informational message that is followed by other messages that provide the program’s usage and/or command line syntax. Consult the program’s documentation for the proper command line syntax.

SQDC019E

Oracle Error (<error_code>):< error_information>

A call to Oracle failed with the given error code and error information.

SQDC020I

<Module>(pid=<pid>) terminated with Return Code <rc>, Reason Code=<mmmmrccc> (<error_info>)

Module terminated with a return code, reason code and error information. Reason Code identifies internal module (mmmm), SQData return code (r) and called module return code (ccc). The called module is usually identified in the <error_info> for example IXG (zOS LogStream)

SQDC024E

Error loading libraries needed for <program> (<rc>):<error_information>

Error occurred when loading libraries for the specified program. Make sure the correct libraries are installed and that the environment variables associated with the specified program are correct.

SQDC026E

I/O (<filename>) last_op=<last_op>, code=<rc> rba=<rba>

An I/O error occurred.

SQDC027E

Options <option1> and <option2> are not compatible

Two options provided at the command line were not compatible. Remove one and try again. Consult the program’s documentation for the proper command line syntax.

SQDC028E

Missing input filename

This program requires an input file. Please specify the input filename.

SQDC029W

Deprecated command line syntax: <invalid_input>

Deprecated command line. Verify that the correct options and arguments have been given. Consult the program’s documentation for the proper command line syntax.

SQDC030W

Deprecated option: <invalid_option>, ignored

Deprecated command line option. Verify that the correct options have been given. Consult the program’s documentation for the proper command line syntax.

SQDC031E

Missing argument(s)

More arguments are required on the command line. Consult the program’s documentation for the proper command line syntax.

SQDC032I

Stop request acknowledged

A stop request was received and executed.

SQDC033E

Invalid config file row #(<number>):|<invalid_content>|

An error was found in the configuration file on the specified row.

SQDC034W

Stop requested on the server side, terminate in error

A stop requested on the server side has terminated with an error.

SQDC035E

Option <option1> is not compatible with multiple instances of option <option2>

Two options provided at the command line were not compatible. Remove one and try again. Consult the program’s documentation for the proper command line syntax.

SQDC036E

The file <filename> already exists

You requested the creation of a configuration file, but a configuration file with that name already exists.

SQDC037E

Too few arguments

There is too few arguments present on the command line. Consult the program’s documentation for the proper command line syntax.

SQDC038E

DB2 UDB error (<error_code>):<error_information>

A call to DB2-UDB failed with the given error code and error information.

SQDC039E

The restart table did not identify anything to clean

The cleaner could not identify anything to monitor for cleaning in the given restart table. Make sure to start the consumer’s engine before starting the cleaner.

SQDC040E

The option(s): <option_name> require the option(s) <option_name>

The specified options cannot be specified without the other associated options as indicated.

SQDC042I

mounting/running <program_name> with arguments:

The specified program has been started with one or more arguments identified on subsequent SQDC041I message statements.

SQDC041I

args[<n>]: <argument option>

The specified argument has been specified where n=1 references the program_name and n>1 subsequent run-time options.

SQDC056E

File <filename> did not open successfully

The file associated with the filename provided did not open successfully. Check that the file exists and that the file name is spelled correctly.

SQDC057E

DB2 error (<error_code>):<error_information>

A call to DB2 failed with the given error code and error information.

SQDC058E

The key <key> for the user <user> is not an authorized key on this server

The key presented is not authorized on this server.

SQDC059E

The user <user> (as <user_as>) does not have sufficient privileges on this server

The user with the credential presented is not allowed to perform the requested task on this server.

SQDC060I

Accepted incoming connection for <user> as <user_as> with acl:<acl>

Informational message to indicated that the given user was authenticated and allowed to proceed in the name of the as user with specified acl.

SQDC061I

Accepted incoming connection for <user> with acl:<acl>

Informational message to indicate that the given user was authenticated and allowed to proceed with the specified acl.

SQDC062E

Error setting up the NACL context

We could not set-up the authentication context (NACL). Check that you did generate a NaCL private key. If on z/OS make sure that you provided a SQDPKEY ddname that point to the private key to use.

SQDC063E

Invalid Argument: |<argument>| for option <option>.

The indicated argument is invalid.

SQDC064E

ODBC Error (<error_code>):< error_information>

A call to ODBC failed with the given error code and error information.

SQDC065E

Invalid LSN:<arg>

The given argument is not a valid LSN.

SQDC066W

Ambiguous LSN:<arg>

The given argument is an ambiguous LSN, in the sense that it is valid in both hexadecimal or decimal notation. This typically occurs when a LSN is represented as nnnnnnnn:nnnnnnnn:nnnn with no leading 0 for any section and all decimal digits. By default this is understood to be a hexadecimal notation. To resolve the ambiguity as decimal notation, add a leading zero to any of the sections, i.e.: nnnnnnnn:nnnnnnnn:0nnnn. Doing that will turn the LSN into a 8:8:5 format which cannot be hexadecimal.

SQDC067W

Waiting to acquire lock for cab <arg>

The indicated cab file is already locked by another process (on z/OS that can be from another LPAR). The program will wait until that lock become available.

SQDC068I

Acquired lock for cab <arg>

The program has acquired the global lock for the give cab file.

SQDC069I

<jobname> Opened url:<url>

Information message about a url being opened.

SQDC070I

<jobname> Closed url:<url>

Information message about a url being closed.

SQDC071E

error changing workdir to <directory> errno:<errno>(<error_information>)

Information message about a url being opened.

SQDC072E

File <filename> could not be loaded (<reason_code>:<error>)

The file associated with the filename provided could not be loaded. Check that the file exists and that the file name is spelled correctly.

SQDC073E

Key <#> belongs to the primary key but is not in the description <spec>.

An attempt to retrieve the primary key at run-time for a target failed because a column that belongs to the primary key was not found in the record description.

SQDC074E

Error retrieving the current Username, using unknown instead

Attempt to retrieve the current username failed. This should not happen on non z/OS. On z/OS make sure that your user has: a RACK OMVS segment, a UID defined and a valid OMVS GID defined. This could also be due to a username length > 64 bytes.

SQDC075E

Option <option> is incompatible with < context>

The option provided at the command line is not compatible with the context it was given for.

SQDC076I

Field: (<ds_name>:<rec_name>:<fld_name>)

This is an informational message to show details on fields related to a previous error.

SQDD002E

Agent <agent_name> not defined on host <host_name>

The specified agent is not defined on the specified host. Make sure the agent is defined in the agent configuration file.

SQDD003E

Agent <agent_name> already started on host <host_name>

You requested to start an agent that is already started. The agent has been closed.

SQDD006I

Launched agent <agent_name> : <agent_information>

Informational log message to inform you that the agent has been launched.

SQDD007I

Agent <agent_name> ended normally

Informational log message to inform you that the agent ended normally.

SQDD008W

Agent <agent_name> ended with error rc = <rc>

The specified agent encountered a problem and ended with the specified return code.

SQDD009W

Agent <agent_name> ended with signal = <number>

The specified agent encountered a problem and ended with the specified signal.

SQDD010E

Error launching agent <agent_name> : <rc> (<error_information>)

The specified agent encountered a problem during launch. For more help consult the error information.

SQDD011E

Agent <agent_name> ended with error rc = <rc>

The specified agent ended with specified return code.

SQDD012E

Agent <agent_name> ended with signal = <rc>

The specified agent ended with the specified signal.

SQDD013E

Agent <agent_name> on host <host> is not a storage agent

The specified agent is not a storage agent, and the requested action applies only to storage agents.

SQDD014E

The path <path> needed for the agent <agent_name> could not be created (<reason>)

The path specified for operation of the agent could not be created.

SQDD014I

Pause requested

A Pause request was received. Note that some in-flight work may continue for a while.

SQDD015I

Resume requested

A Resume request was received. If the process was not Paused then this is a No-Op.

SQDD016E

Could not find a transfer socket. Agent:<agent> (storage agent:<storage_agent>)

The daemon try to determine the transfer socket for an agent but could not. Check your Agent's configuration, the location of the cab files, the alias of the cab files, and the file system authorizations.

SQDD017E

Cannot create a network client, Agent:<agent> Socket:<socket>

Could not create a network object to connect to the agent’s transfer socket.

SQDD018E

Cannot connect to transfer socket(rc==<error>). Agent:<agent> Socket:<socket>

Could not connect to the agent’s transfer socket.

SQDD019E

Error during handshake (rc=<error>). Agent:<agent> Socket:<socket>

Could not finish the handshake with the agent’s transfer socket.

SQDD801I

SQDAEMON(<agent_name>) started on port <host> with rc = <reason_code>

Indicates that the daemon started.

SQDD802I

SQDAEMON(<agent_name>) ended with rc = <reason_code>

Indicates that the daemon stopped.

SQDD803E

No authorized_keys were found, the service would not be usable, Aborting

SQDAEMON could not find an authorized keys file and did not have a private key of its own. A private key was dynamically generated but no incoming connection can be validated since no one can have an authorized public key. This safety is engaged even if guest users are allowed.

SQDD805E

Error loading the configuration file <configuration_file> rc=<reason_code>

An error occurred during the initial load of the configuration file specified. In case of error, during successive reload (using sqdmon reload) the original configuration is retained, the sqdmon reload command fails, and this message is not displayed.

SQDD806E

Error verifying the section <section_name> (<reason_code>)

An error occurred verifying the specified section. There may be missing parameters or the underlying object may be corrupted.

SQDDB01E

No PSB entry with integrity procop was found for database <database>

A connection request was received that referenced the given database but the PSB for this SQDIMS execution does not have an entry for this database with the required proc-op. We will not be able to process requests for this connection. The connection is terminated.

SQDDB02E

No psb with GO procop was found for database <database>*

A connection request was received that referenced the given database but the PSB for this SQDIMS execution does not have an entry for this database with the required proc-op. We will not be able to process request for this connection. The connection is terminated.

SQDDB03W

The database <database> has been paused due to excessive mismatches

The number of mismatches recorded for the specified database has exceeded the allowed limit. This database has been paused. No new checks will be performed on this database until it has been resumed.

SQDE001E

The Replication of <source_alias> could not be resolved as <target_alias> in datastore <target_datastore>

The Replicate function is trying to figure out to which target record it should replicate the source record, either by using the source table name or the optional second argument of the Replicate() function It could not find a match, and therefore does not know how to replicate the record.

SQDE001W

<nature> detected for <object> on engine <engine>

This is used to issue WTO about compensation or exception issue indicated by nature on the engine engine for the object object.

SQDE002E

A Converter between the ccsid <from_ccsid> and <to_ccsid> could not be acquired <reason_code>

A ccsid converter between the given ccsids could not be acquired.

SQDE003E

A Conversion between the ccsid <from_ccsid> and <to_ccsid> failed: <reason_code>

A conversion between the given ccsids failed.

SQDE004E

Code Label <name> could not be resolved

The given name does not resolve to a Code Label.

SQDE005E

Cannot determine the key(s) of an unqualified table : <name>

In order to fetch the keys automatically from the catalog we need a qualified name. Either provide a qualifier or use KEY IS.

SQDF001E

Configuration file <filename> cannot be opened (<rc>)

The given configuration filename could not be opened. Verify that the file exists and that you have the right to access it.

SQDF002E

Invalid configuration version, Found:<version>, Expected:<version>

The configuration file was created with a different version of the product than the one running.

SQDF006E

The Entry <table> is not defined in the configuration <filename>

You attempted to modify or remove the description of a table, but that table does not exist in the configuration file.

SQDF007E

The capture agent is in state PAUSED, it can only be resumed if it is stopped

You attempted to resume a capture agent that is in the paused state. Stop the capture agent and try again.

SQDF008E

The capture agent is already started

You attempted to start the capture agent but it is already started.

SQDF009I

The capture agent is already stopped

You attempted to stop the capture agent but it is already stopped.

SQDF010I

The capture agent is stopping

You attempted to stop the capture agent but it is already pending stop.

SQDF011I

Scanning for Metadata Changes

The Db2 Capture is performing an initial scan of the Db2 log for catalog changes that have occurred after the Safe Remine point.

SQDF012E

Cannot Apply on a started or paused capture agent

In order to apply, the capture agent must be stopped.

SQDF014E

The capture agent is not Mounted, the requested operation cannot be processed

In order to do the requested operation, the capture agent must be mounted.

SQDF015I

The capture agent is already mounted, ignoring mount request

You attempted to mount the capture agent, but the capture agent is already mounted.

SQDF016W

No table is active, the capture agent did not start

You attempted to start a capture agent, but no table in your configuration file is marked as active. The agent is now in the stopped state. Use SQDCONF’s add function to mark the desired tables as active. The default status of a table is inactive. Next use SQDCONF’s apply function. Changes made with the add function will not be used until they are applied.

SQDF017E

The capture agent is already mounted, aborting this instance

This should never be seen. This indicates that the capture agent load module was started manually while a capture agent was already mounted. The message indicates that the second instance of the capture agent detected the condition and did not attempt to start.

SQDF018I

Mounted capture agent for configuration file <filename>

This is a Log only message. It is sent to SYSLOG when the capture agent is mounted.

SQDF019E

The capture agent is started

You tried to unmount an agent that is started. You need to stop it before it can be unmounted.

SQDF020W

The capture agent is started or paused, unmount forced per request

You have requested a forced unmount for a capture agent that is in the started or paused state.

SQDF021I

Undo <n> actions to restore the initial metadata

The Db2 metadata scan found a total of <n> changes to the database catalog between the restart LSN and the current state of the catalog.

SQDF022W

The capture thread has been interrupted at Log Point:<log_point>

The capture agent was stopped, either intentionally or not. This message tells you the last log point that was processed by the capture agent before it’s demise. Note that log point is relative only to the log records associated with the object monitored by the capture agent. This does NOT represent the log point of the system at the time of failure.

SQDF023E

Capture thread was interrupted at Log Point:<log_point> for config file <filename>, rc(<rc>)

This is a Log only message. Identical in nature and purpose to SQDF022W, except that it repeats the name of the configuration file to make log based diagnostic easier.

The following message is an example of a Capture failure that requires looking at the Db2 system log for more details:

08.03.40 STC48240  SQDF023E Capture thread was interrupted at Log Point:0x00DB534666F224AA

08.03.40 STC48240  SQDF023X 0000 for config file /home/sqdata/DB2CDC.cab, rc(0x45c001:IF

08.03.40 STC48240  SQDF023X I_READS_ERROR)

 

Db2 only returned a general IFI_READS_ERROR. The Db2 system log from the same point in time pointed out that the LSN was on an inaccessible Archive Log.

SQDF023W

Capture thread was stopped at Log Point:<log_point> for config file <filename>

This is a Log only message. Identical in nature and purpose to SQDF022W, except that it repeats the name of the configuration file to make log based diagnostic easier.

SQDF024I

Started capture agent for configuration file <filename>

This is a Log oriented only message. This message is a marker in the SYSLOG of when the capture agent actually started.

SQDF025E

The Oracle Database has not been altered for minimal supplemental logging

This message indicates that the Oracle database does not meet the minimum supplemental logging requirements in order to successfully capture logs.

SQDF026E

The entry <key> is not defined in the configuration <filename>

You attempted to modify or remove the description of an entry identified by the indicated key, but that entry does not exist in the configuration file.

SQDF027F

The capture agent died following a signal <number>

The given signal occurred and caused the capture agent to terminate abnormally.

SQDF028E

The entry <key> is already defined in configuration <filename> at position #<number>

You attempted to add an entry to the configuration that is already defined in this configuration.

SQDF030W

The datastore <datastore_name> is not associated to the entry <key>

You requested a datastore url to be removed from a given entry, but that datastore is not currently associated with this entry. The request has been ignored.

SQDF031W

The datastore <datastore_name> is already associated to the entry < key>

You requested a datastore url to be added to a given entry, but that datastore is already associated with this entry. The request has been ignored.

SQDF032W

The entry <key> has no associated datastore

This message indicates that a given entry has no datastore associated with it. If this modification is applied as-is, the entry will automatically be put in a inactive state.

SQDF033E

The configuration has no active section (forgot to apply?)

This message indicates that a you probably tried to start a configuration that has never been applied, hence there is nothing defined to start. Apply the change to your configuration and start again.

SQDF034W

No archive logs are available to seed the mining process, only active logs will be used

If you are using the "committed log capture" method, our program needs access to archive logs. If you are using the "raw data capture" method, archive logs might be needed depending on the safe restart point. Note: These two methods of capture are described in the Oracle Capture agent documentation.

SQDF036E

The oldest available SCN (<log_point>) is after the selected restart point (<log_point>)

You provided a restart point that is before the oldest available log. Consider letting SQDCONF calculate the safe restart based on the transactions in-fight at the time when the capture last ran, or the current log point at the time of this start.

SQDF037I

Processing Log for CDC

The Db2 capture has completed the metadata scan phase and begun reading the Log for change data records.

SQDF038E

Old config file version: <version> (current is <version>). Use sqdconf migrate to upgrade

The capture agent configuration file that you are using is an older version. Use the Migrate action of SQDCONF to upgrade your configuration file to the new version.

SQDF039E

The safe restart margin given (<log_point>) lead to a negative restart point

You provided a relative (negative) number as the safe restart value which lead to an invalid (negative) restart point. Absolute restart points must be positive.

SQDF040E

Safe restart margin given (<log_point>) lead to a restart point prior to available logs <log_point>

You provided a relative (negative) number as the safe restart value which lead to restart point prior to the available logs. Bring more logs online or reconsider the relative safe restart number provided.

SQDF041E

Safe restart value given (<log_point>) lead to a restart point prior to available logs <log_point>

You provided a safe restart that requires more archive logs than are online. Consider letting SQDCONF calculate the safe restart based on the transactions in-fight at the time when the capture last ran, or the current log point at the time of this start.

SQDF042W

Safe restart given (<log_point>) lead to a restart point after the determined restart commit point <log_point>. Transactions with activity in the interval will be lost

You provided a safe restart value that will more than likely lead to the loss of records. Consider letting SQDCONF calculate the safe restart based on the transactions in-fight at the time when the capture last ran, or the current log point at the time of this start.

SQDF043E

Migration cannot occur on a mounted capture agent

You requested to Migrate a configuration file, but this can only occur if the capture agent is in the unmounted state. Take the necessary steps to unmount the capture agent, then try the Migrate command again.

SQDF044E

A configuration file cannot grow while the associated capture agent is started

You requested a table entry be added, but there is not enough room in the configuration file AND the agent is started. You need to stop the agent to be able to add a new table.

SQDF045I

The process for the capture agent <agent_name> has been started as process id: <process_id>

This message informs you of the Process ID of the mounted capture agent.

SQDF046W

The item <item_type> is not in the <item_value> list

You requested an item of type <item_type> to be removed from the <item_type> list, but that item is not currently in the list. The request has been ignored.

SQDF047W

The item <item_type> is already in the <item_value> list

You requested that item <item_type> to be added to the <item_value> list, but that item is already in the list. The request has been ignored.

SQDF048E

The description of table <table_name> could not be retrieved from the database

The table <table_name> could not be described within the database. The table is marked active so the capture must stop. Make sure that the table name is correct, or mark the table as inactive.

SQDF049I

Capture thread is starting with Remine Log Point:<logpoint> (<source>) for config file <filename>

This an informational message that a capture thread is starting for the given config file using the given log point as the remine log point.

SQDF050I

Capture thread stopped with Remine Log Point:<logpoint> and Restart Log Point:< logpoint>

This informational message identifies the safe_remine and safe_restart points when the capture thread stopped.

SQDF051W

The table <table_name> is not configured to allow Data Capture

The table <table_name> is not enabled for data-capture. NOTE: This message is intended to identify only tables marked active in the capture configuration .cab file. Beginning, however, with the introduction of Db2/z schema evolution in 4.0, all tables not ALTERED for capture are being reported. If you are not processing Db2/z CDC data with the Replicator Engine and taking advantage of schema evolution then these messages can be suppressed using the --no-ddl-tracking option.

SQDF052W

The table <table_name> has been Altered : <info>

An Alter to the table <table_name> has been detected. The table is marked active, and an alter to that table has been detected while processing the log. That changes the known structure of the table by the capture. This can have consequences on the processing of further change records for that table. Make sure to deploy alters to captured tables in an orderly fashion as described in the documentation.

SQDF053I

Refresh request received for table <table_name>

A request to completely refresh the content of a table as been received.

SQDF054I

Processing Refresh request for table <table_name>

A request to completely refresh a table is being processed.

SQDF055I

Committed Refresh request for table <table_name>

The pseudo commit for a refresh request is stored.

SQDF056I

Received ACK for Refresh request for table <table_name>

The refresh pseudo transaction was processed on a target.

SQDF057E

Internal Working table SQDATA.REFRESH_REQUEST_LOG is not set-up properly

The working table SQDATA.REFRESH_REQUEST_LOG was not found, cannot be accessed, or is not set to data capture. As a consequences, we cannot process refresh request.

SQDF058E

Cannot Refresh on capture agent not started

In order to do a refresh, the capture agent must be started.

SQDF059E

Cannot Refresh on Paused capture agent

In order to do a refresh, the capture agent cannot be Paused.

SQDF060E

Cannot Find Redo Log with a Dictionary Dump older than the intended restart point: <log_point>

In order to capture using tracking-ddl, a dump of the dictionary must be present in a redo log older than the required restart SCN.

SQDF061E

<action> rejected because capture is running

The given action is not allowed while a capture is running on this configuration.

SQDF062E

<action> on <target> rejected because <target> is connected

The given action on the given target is not allowed while the target is connected.

SQDF063E

<url> is not a supported url in this context

The given datastore url is not valid or supported in the context.

SQDF064E

The modify action would leave us with no input stream

The modify operation leave us with no input streams left

SQDF100E

At least 2 logfiles are needed to create a cdclog object

When you create a storage agent associated with a capture agent, at least two log files must be specified. This can be done with the create action of SQDCONF. Either specify at least two log file names or specify a base name with -n option greater than or equal to two. Consult the documentation of SQDCONF for more information.

SQDF101E

Cannot format the logfile <filename> as the file already exists

You requested that your storage agent have filename(s) that belong to files that already exists. Either delete the files that already exists or change the filename of the storage agent logfiles.

SQDF102E

The associated cdclog configuration: <filename>, could not be opened (<reason_code>)

The specified cdclog file associated with the capture agent could not be accessed. Make sure it has been created properly.

SQDF200E

Capture’s storage agent is out of space

Capture’s storage is out of space.

SQDF202E

Could not create the Unix socket <socket_path>, reason <reason_code>

The specified Unix socket could not be created. Verify that the path to that socket exists and has the proper authorizations.

SQDF203E

The storage agent is already mounted, aborting this instance of it

This should never be seen. This indicates that the storage agent associated with a capture agent that is attempting to start is already mounted. This possibly indicates that the same storage agent has been assigned to 2 different captures, the other capture already being active.

SQDF204E

The target <target_name> is already connected

This message is issued when requesting to connect a target that has already been connected.

SQDF205E

The target <target_name> is not defined in the configuration <conf_name>

An action was requested on a target name that is not defined in the given active configuration.

SQDF206E

Connect action on a CDC target <target_name> is invalid

A connect action was requested for a CDC target. CDC targets are servers, they cannot initiate a connection.

SQDF207E

Deadlock condition detected for <cab_file>

The capture is deadlocked. That indicates that it ran out of storage space, and storage cannot be freed because the next transaction to be shipped is not complete yet. You need to add more storage using SQDCCONF Modify/Add on the underlying storage agent.

SQDF208E

Disconnect Queue <queue_name> due to rc = <rc> (<strerror>)

Some operation on a cdcstore queue target failed and cause that target to be disconnected.

SQDF209E

Disconnect Queue <queue_name> due to errno:<errno> (<strerror>)

Some operation on a cdcstore queue target failed and cause that target to be disconnected.

SQDF210W

Store entry <id> (<filename>) marked invalid due to rc=<rc> or not a directory

A storage entry of a cdcstore cannot be used to allocate storage file.

SQDF211W

Clean-up of storage file <id> failed with rc=<rc>

The deletion of an existing storage files failed.

SQDF212W

Creating new storage file <id> failed with rc=<rc>

The creation of an existing storage files failed.

SQDF213W

Running out of storage file

The existing storage files are getting close to full. You may need to allocate more storage.

SQDF801I

Configuration name : <file_name>

This message begins statistics about the capture agent storage file. These statistics can be retrieved by using the display action of SQDCONF. Consult the program’s documentation for the proper command line syntax.

SQDF890I

Last Ack Time : <time>

Informational message about the engine agent. The time of the last acknowledgement.

SQDF891I

Last Ack Latency : <miliseconds>

Informational message about the engine agent. The latency in miliseconds.

SQDF892I

Comment : <comment>

Informational message about the engine agent.

SQDF893I

Last Txn rba : <rba>

Informational message about the engine agent. The last rba processed.

SQDF894I

Current Txn rba : <rba>

Informational message about the engine agent. The current transaction rba.

SQDF895I

Target flags : <flags>

Informational message about the engine agent. The target flags.

SQDF900I

Current SCN <scn>

This message begins statistics about the capture agent. These statistics can be retrieved by using the Display action of SQDCONF. Consult the program’s documentation for the proper command line syntax.

SQDF901I

Configuration file : <filename>

This message begins statistics about the capture agent. These statistics can be retrieved by using the Display action of SQDCONF. Consult the program’s documentation for the proper command line syntax.

SQDIF03E

XPARM error rc=0x0C LOAD failed

The XPARM module that contains the name of the Feed LogStream could not be found.

SQDI001I

Server Set-up on port <port>, waiting for requests

Informational message indicating that SQDIMS is initialized and waiting for an incoming connection on the specified port.

SQDI003I

Accepted source-side checker connection from <name>

An incoming connection request, as a source-side checker, was accepted from the client named in the message.

SQDI004I

Accepted target-side checker connection from <name>

An incoming connection request, as a target-side checker, was accepted from the client named in the message.

SQDI005E

Rejected checker connection from <name> rc=<reason_code>

An incoming connection request from <name> was rejected due to set-up error <reason_code>.

SQDI100I

Capture initiated for IMS <type> <name>

Capture initiated for the named IMS batch job or online subsystem.

SQDI101I

Capture terminated for IMS <type> <name>

Capture terminated for the named IMS batch job or online subsystem.

SQDI102I

Capture delayed, <reason> <variable_data>

Capture delayed for the reason given in the message text.

SQDI103E

Capture failed for IMS <type> <name>, <reason>

Capture failed for the named IMS batch job or online subsystem. The failure reason is given in the message text. More detailed messages may accompany this message in the job log or SYSLOG.

SQDI104I

Capture paused by <agent>

Capture paused by the identified agent.

SQDI105I

Capture resumed by <agent>

Capture resumed by the identified agent.

SQDI106I

Capture stopped by <agent>

Capture stopped by the identified agent.

SQDI107E

<command> rejected because the capture is <state>

The rejected command is not valid in the indicated state.

SQDI120I

Processing log for IMS <type> <name> dsn=<dataset_name>

Issued when processing commences for the named log dataset.

SQDI121I

Completed processing for IMS <type> <name> dsn=<dataset_name>

Issued when processing completes for the named log dataset.

SQDI710E

<operation> failed rc=<rc> err=<errcode> info=<infocode> dd=<ddname> dsn=<dataset_name>

Dynamic allocation or unallocated failed for the named dataset.

SQDI711E

<operation> failed rc=<rc> dd=<ddname> dsn=<dataset_name>

Open or close failed for the named dataset.

SQDI712E

Positioning error,<operation>,rc=<rc> dd=<ddname> dsn=<dataset_name>

Positioning error on the named dataset. An SQDAAIOM I/O ERROR message may accompany this message.

SQDI713E

Sequence error at lsn=<tod>.<seq> dd=<ddname> dsn=<dataset_name>

Log sequence error. The log contains a record with an invalid LSN. The log dataset may be corrupted.

SQDI714E

Subsystem <subsystem> <reason> at sequence number <seq_no>

No log with the specified sequence number was found. If the reason is "compressed PRILOG", the capture cannot continue and will terminate immediately. If the reason is "log missing", the RECON entry may have been deleted or it may be a transient condition. Capture will retry several times before terminating.

To prevent premature deletion of logs from the RECON, increase the DBRC log retention period and ensure that the capture is caught up before performing any RECON maintenance that may compress or delete log entries.

SQDI715E

<subsystem> PRIOLD dsn=<dataset> excluded from activity monitoring, <reason>

The subsystem's RECON PRIOLD includes an OLDS data set that could not be allocated. It will not be used for OLDS switch activity monitoring.

SQDI716E

<subsystem> No log in RECON for tod=<time_of_day>

The log containing the start time specified as a  is not in the RECON.

SQDI751E

IMS DBRC API error, rc=<rc>, rsn=<reason>, verify IMS SDSFRESL is in the JOBLIB or STEPLIB concatenation

An IMS DBRC API error occurred.

SQDK001E

Kafka <context> (<errno>) <errmsg>

A failure occurred interacting with kafka. The context indicates an attempted operation, result, or status. The error number and error message are from librdkafka. Possible values include:

Kafka ack in error, ktm->errno, errstr

Kafka buffer, errno, errstr

Kafka Failed to set metadata.broker.list, errno, errstr

Kafka Failed to create new producer, errno, errstr

Kafka ack in error, ktm->errno, errstr

Kafka buffer, errno, errstr

Kafka Failed to set auto.commit to false, errno, errstr

Kafka Failed to set enable.auto.offset.store to true, errno, errstr

Kafka Failed to set auto.offset.reset to earliest, errno, errstr

Kafka Failed to set metadata.broker.list, errno, errstr

Kafka Failed to create new consumer, errno, errstr

Kafka Failed to create new producer, errno, errstr)

Kafka buffer, res, WEAKAPI(kafka,rd_kafka_err2str)(res)

Kafka failed to commit consumer, res, WEAKAPI(kafka,rd_kafka_err2str)(res)

SQDMQ01E

Error connecting to the Queue Manager:(<manager_name>) MQ reason code:<MQ_reason_code>

This indicates that the capture agent had trouble connecting to the given Queue Manager. The agent did not start.

SQDMQ02E

Error opening the Queue :(<queue_name>) MQ reason code:<MQ_reason_code>

This indicates that the capture agent had trouble opening a given queue. The agent did not start.

SQDMQ03E

Error Writing into Queue :(<queue_name>) MQ reason code:<MQ_reason_code>

An error occurred while trying to write to a target queue. The capture agent stopped as a consequence. A Reason Code of 2053 indicates a Queue Full condition. See MQ Manual for more details on these reason codes.

SQDMQ04E

Error accessing the Queue :(<queue_name>) MQ reason code:<MQ_reason_code>

This indicates that the capture agent had trouble accessing a given queue. The agent did not start.

SQDMQ05E

Error accessing the Queue :(<queue_name>) rc:<MQ_reason_code>

This indicates that the capture agent had trouble connecting to or opening a given queue. The error is from the module that manages IBM MQ access and not MQ itself. The agent did not start.

SQDMQ06E

Error Writing into Queue :(<queue_name>) MQ reason code:<MQ_reason_code_value>

An error occurred while trying to write to a target queue. The capture agent stopped as a consequence. A Reason Code of 2053 indicates a Queue Full condition. See IBM MQ Manual for more details on these reason codes.

SQDMQ07E

Error Writing into Queue :(<queue_name>) reason code:<reason_code>

An error occurred while trying to write to a target queue. The capture agent stopped as a consequence. The error is not directly from IBM MQ and the reason_code given is a reason_code.

SQDP001I

Included From <file_name>:<line_number>

Informational message to indicate what file was included and at what line number.

SQDP002I

At <file_name>:<line_number>

Informational message to indicate file_name and line_number. This message should be followed by another message that indicates what the problem is at the specified location.

SQDP003W

The variable <variable_name> is undefined and has not been substituted

A substitution variable exists in the script, but its value has not been specified at the command line/JCL. The substitution variable will remain in the script. This message is a warning as this may be the intended behavior.

SQDP004E

Too many levels of includes

There are too many nested includes. Reevaluate the number of nested includes in your script.

SQDP005E

Missing Closing ) for preprocessor variable

A %(… preprocessor variable is missing a closing parentheses.

SQDP006E

Left-Value <left_value> is not declared

An assignment is being done where the left value is not declared. Search for the specified value in the script and make alterations as needed.

SQDP007E

NORM() is applied to the field <field_name> which is not a repeating group

The function NORM() can only be preformed on a repeating group. Check the datastore description which includes the specified field for errors.

SQDP008E

MAP_BEFORE is only supported for Key columns (<field_name>)

The MAP_BEFORE function has been used on a non-keyed column. Change the key column used in the MAP_BEFORE function.

SQDP009E

Datastore <datastore_name> is declared relational but does not have a Key defined

Relational datastores must have a key defined. Consult the program’s documentation to determine how a relational datastore should be defined and what syntax should be used.

SQDP010E

The second argument of ABCBS_ISO_DATE must be a Variable

The second argument of ABCBS_ISO_DATE must be a declared Variable.

SQDP011E

The second argument of ABCBS_ISO_DATE, <date>, must be at least 10 bytes long

The second argument of ABCBS_ISO_DATE must be a Variable of at least 10 characters long.

SQDP012I

The Field <ds_alias>.<recname>.<fldname> is unused and was removed from the description

The indicated field was removed from the description because if was not needed to perform the script.

SQDP013E

Input Datastore <ds_alias> must have an exception Datastore due to the requested ATOMIC UOW option

The indicated datastore does not have an associated Exception Datastore, but the option ATOMIC UOW is set, which makes an exception datastore mandatory.

SQDP014E

The option ATOMIC_UOW is incompatible with the statement COMMIT EVERY <n>

The option ATOMIC_UOW is incompatible with setting COMMIT EVERY <n>. In Atomic UOW mode, the engine is not allowed to trigger commits. Commits are driven by the input CDC.

SQDP015E

Cannot include <filename>, reason < reson_code> (< explanation>)

The file listed cannot be included for the reason and text shown.

SQDP016E

<datastore> is designated as Exception Datastore, but its <type>, is not valid for an Exception Datastore

Exception datastores cannot be RELATIONAL, IMS or VSAM.

SQDP017E

Ambiguous Left-Value <left_value>

An assignment is being done where the left value is ambiguous. That is there is more than one left-value that match the specified name.

SQDP018E

Datastore <datastore_name> has no record description

The given datastore does not have any description attached to it. This can occurs for instance if you use describe by group with a group that is empty.

SQDP019E

Too few arguments for function <function_name>

The given function requires more arguments than given.

SQDP020E

Entry <entry_name> redefines % but is not of the same level

Redefines must be at the same level.

SQDP021E

Entry <entry_name> is level 1, It cannot be a redefine

Redefines of level 1 is not allowed.

SQDP022E

Entry <entry_name> redefines an unknown entry < redefined_entry>

The entry redefines a unknown entry.

SQDP023E

Entry <entry_name> redefines < redefined_entry> which is already a redefine

A redefine cannot redefine another redefines.

SQDP024E

Entry <entry_name> redefines < redefined_entry> which has an OCCURS clause

A redefine cannot redefine an occurs.

SQDP025E

Entry <entry_name> has subordinates items but is not a GROUPITEM

Only Group-items should have subordinate items.

SQDP026E

Entry <entry_name> is Level 1 but also a FILLER

Level 1 entries cannot be FILLER.

SQDP027E

Function <function> requires <want_params> arguments, but <have_params> were provided

A call to a function does not have the right number of arguments.

SQDP028E

Scalar argument required

An argument needs to be a scalar but is not.

SQDP029E

Left-Value Required

Left-Value required.

SQDP030E

<context_id>) Record Alias <rec_alias> does not exist in Datastore <ds_alias>

The specified record alias is not a description of the given Datastore.

SQDP031E

<context>) Datastore <ds_alias> cannot be FOR CHANGE

The specified datastore type is not compatible with FOR CHANGE.

SQDP032E

<context>) Description <description>'s type is invalid for Datastore <ds_alias>

The specified description type is not compatible with the datastore specified.

SQDP033E

<context>) Duplicate declaration of <name>

The specified object was declared twice.

SQDP034W

Using a generic DDL description <rec_alias> with Oracle Datastore <ds_alias>

Using a generic DDL description with an Oracle datastore. Some column types may be altered to compensate. Use ORADDL description instead if possible.

SQDP035E

The RDBMS based datastore <ds_alias> require SQL-based descriptions (< rec_alias>)

RDBMS input or output require SQL-based descriptions.

SQDR001E

Recname <datastore> not found for datastore <recname>

The given recname is not a known record for the given datastore.

SQDR002E

Error mapping field <recname>.<fieldname> rc=<reason_code>

An error occurred mapping the specified field input data.

SQDRI01I

Processing log:<logfile>

Information message indicating that the specified logfile has been processed.

SQDRI02I

Scrubbed <scrubbed> records, pushed <pushed> records in <commit> committed transactions

Information message indicating that the specified logfile has been processed and reporting on the content found in that log.

SQDRI03I

Total. pushed <scrubbed_count> records in <pushed_count> committed transactions

Information message reporting execution statistics.

SQDSY01E

Missing SYNCHER statement

The control file used is missing the mandatory SYNCHER <name> statement.

SQDSY02E

Missing declaration for a <statment_type> statement named <name>

The control file used is missing the declaration statement of the specified name. A previous SQDY000I message indicates which part of the syntax required that statement.

SQDSY03E

The <statemnt_type> statement named <name> is already attached to a statement

The described statement is already used by a previous statement. This is followed by the position of the statement that used it.

SQDSY04E

The segment <segment_name> does not exist in the associated database <database_name>

The specified segment is not part of the database definition. This is followed by the position of the statement that declared the DBD to use for the database definition.

SQDU002I

<origin> table <tbname>, column pos: <index> name:<colname>

Informational message to provide context for a subsequent error message.

SQDU003E

Columns have different Nullability attribute

A remote and local description of a column are incompatible because one is null-able and the other is not details of the columns are given in a SQDU002I message prior.

SQDU004E

Columns have different internal size

A remote and local description of a column are incompatible because they are different internal size details of the columns are given in a SQDU002I message prior.

SQDU005W

The remote source can provide records for <remote_table>, unknown in <datastore_alias>

A remote source is susceptible to provide CDC record for the given table, but that table cannot be resolved to a local record description for the given input datastore alias

SQDUR01E

Invalid url (<url>)

The url provided at the command line or in a configuration is invalid. Consult the program’s documentation for the proper url syntax.

SQDUR02E

Invalid url (<url>), missing nature

The url provided at the command line or in a configuration is invalid. A url must begin with <nature>:// where the possible natures are enumerated in the program’s documentation.

SQDUR03E

Invalid url (<url>), unknown nature: <invalid_nature>

The url provided at the command line or in a configuration is invalid. A url must begin with <nature>:// where the possible natures are enumerated in the program’s documentation. The specified nature is not a valid nature for this program.

SQDUR04E

Unsupported url (<url>)

The given url is not supported.

SQDUR05E

Error opening url <url> : <rc> (<strerror>)

Trying to open this url for read failed with the given return code.

SQDUR06E

Error opening url <url> : errno:<errno> (<strerror>)

Trying to open this url for read failed with the given system error.

SQDUR07E

Error reading message on url <url> : error:<errno> (<strerror>)

Trying to open this url for read failed with the given system error.

SQDUR08E

Error writing to url <url> : x_<rc> (<strerror>_)

Trying to write to url failed with the given return code.

SQDUR09E

Error writing to url <url> : error:<errno> (<strerror>)

Trying to write to url failed with the given system error.

SQDUR10I

Max In-flight uows reached: <url>

Trying to write to url failed with the given system error.

SQDUT01E

The file <filename> already exists, use --force to overwrite

The indicated key file already exists. By default, keygen will not overwrite the file unless explicitly instructed to do so with the --force command line argument.

SQDUT02E

The key location <filename> exists and is not a file

The indicated key file location already exists and is not a regular file. KEYGEN cannot generate a key at this location.

SQDUT03E

Error writing the key file <filename>

An I/O error occurred while attempting to write the specified key file.

SQDUT04I

Generating a private key in file <filename>

Information message indicating the location where the private key will be generated.

SQDUT05E

The specified operation is not supported on this platform

Some operations/options are platform specific. The operation/option you requested is not supported on the current platform.

SQDUT06E

The Registry update failed

An attempt to update the Registry with log event information failed.

SQDUT07I

Installed the event log dll: <dll_name>

The Registry was successfully updated with log event information.

SQDX001E

Access to the Before Image on a record that does not have one

An attempt is being made to map a field from the Before Image of a record, for instance using the CDCBEFORE() function. However, the record is an insert, a delete or not a CDC record at all. This is not supported as such value is undefined.

SQDX002E

Error Uncompressing Data using CSRCESRV-COMPRESS: rc=<rc>

IMS log records have possibly been corrupted. Contact Support for help.

SQDX003E

Truncated Physical Log Record (<rc>/<rc>)

You may receive this message when reading from a queue. The length of the message does not match the length of the total log message. Example: Putting CDCRAW records into a queue without the datastore being of type IMSCDC/DB2CDC/etc. Consider changing the datastore type. Consult the program’s script documentation for acceptable datastore types.

SQDX004E

IMS <operation> failed on db <dbname> for segment <segname> with code <rc>

An Apply operation on IMS failed. This message provides details about the nature of the failure. This message is followed by a SQDX005I message that contains the Full Key of the segment involved in the failure.

SQDX005I

FullKey:<fullkey>

This message follows a warning or error on an IMS apply operation. It provides details on the Full Key associated with that error or warning. Non-displayable characters are substituted by dot. If any character needed to be substituted, this message is followed by a hexadecimal dump of the full key.

SQDX006I

Compensated a <operation> on db <dname> for segment <segname>

An Apply operation conflicted and needed compensation. This message provides details about the nature of the compensation. This message is followed by a SQDX005I message that contains the Full Key of the segment involved in the compensation.

SQDX007W

IMS <operation> failed on db <dbname> for segment <segname> with code <rc>

An Apply operation on IMS failed and had been sent to an exception datastore. This message provides details about the nature of the failure. This message is followed by a SQDX005I message that contains the Full Key of the segment involved in the failure.

SQDX008I

Segment:

This message follows a warning or error on an IMS apply operation. It provides the dump of the segment implicated in the error/warning.

SQDX009I

Associated CDC clock : <store_clock>

This message follows a warning or error on an IMS Apply operation, or a informational message about IMS compensation. It provides the store clock of the captured change that trigger the previous message.

SQDX010E

Before Image Mismatch <operation>, db <dbname>,segment <segname>

An Apply operation on IMS was rejected because the before image did not match the target. This message is followed by a SQDX005I message that contains the Full Key of the segment involved in the failure.

SQDX011I

Current Segment:

This message is followed by a warning or error on an IMS Apply operation. It provides the dump of the segment currently in the IMS database implicated in the error/warning.

SQDX012I

CDC Before Segment:

This message is followed by a warning or error on an IMS Apply operation. It provide the dump of the before image of the segment implicated in the error/warning.

SQDX013I

Before Image Mismatch <operation>, db <dname>,segment <segname>

An Apply operation on IMS was compensated because the before image did not match the target. This message is preceded by SQDX011I and SQDX0012I messages that contain the current and the before image version of the segment that conflict.

SQDX014E

Attempt to use field:|<field_name>| from unmapped record:|<record_alias>|

A field has been referenced that does exist in the source record. In the context of a IMS input, this could be due to the attempt to use a non-key field of a parent record without the current segment being marked as PATH data.

SQDX015E

Before Image Mismatch <operation>, file <dname>

An Apply operation on VSAM was rejected because the before image did not match the target. This message is followed by a SQDX016I message that contains the key of the record involved in the failure.

SQDX016I

Key:<key>

This message follows a warning or error on a VSAM Apply operation. It provides details on the key associated with that error or warning. Non-displayable characters are substituted by dot. If any character needed to be substituted, this message is followed by a hexadecimal dump of the key.

SQDX017E

VSAM <operation> failed on file <ddname> with rc: <rc> reason: <rs>

An Apply operation on VSAM failed. This message provides details about the nature of the failure. This message is followed by a SQDX016I message that contains the Key of the record involved in the failure.

SQDX018W

VSAM <operation> failed on file <ddname> with rc: <rc> reason: <rs>

An Apply operation on VSAM failed. This message provides details about the nature of the failure. This message is followed by a SQDX016I message that contains the Key of the record involved in the failure.

SQDX019I

Record:

This message follows a warning or error on a VSAM Apply operation. It provides the dump of the record implicated in the error/warning.

SQDX020I

Compensated a VSAM <operation> on file <ddname>

An Apply operation conflicted and needed compensation. This message provides details about the nature of the compensation. This message is followed by a SQDX016I message that contains the Key of the record involved in the compensation.

SQDX021I

Current Record:

This message is followed by a warning or error on a VSAM apply operation. It provides the dump of the record currently in the VSAM file implicated in the error/warning.

SQDX022I

CDC Before Record:

This message is followed by a warning or error on a VSAM Apply operation. It provides the dump of the before image of the record implicated in the error/warning.

SQDX023I

VSAM Before Image Mismatch for <operation> on file <ddname>

An Apply operation on VSAM was compensated because the before image did not match the target. This message is preceded by SQDX021I and SQDX0022I messages that contain the current and the before image versions of the segment that conflicts.

SQDX024E

FLDCHG can not be used on this input record

FLDCHG uses a field’s offset and length to access a record’s raw data stream to determine if a field has changed. For this reason, FLDCHG can only be used on record that have a deterministic offset for the data of each column, like IMS or VSAM records. Consider using the function CDCBEFORE instead. This message will only be produced if FLDCHG is trying to process an update. By definition, inserts and deletes will always return true.

SQDX025I

Compensated <operation> for table <table_name>

An Apply operation conflicted and needed compensation. This message provides details about the nature of the compensation. This message is followed by a SQDX026I message that contains the SQL statement involved in the compensation.

SQDX026I

Associated log point : <store_clock>

This message follows a warning or error on a Relational Apply operation, or a informational message about Relational compensation. It provides the store log point of the captured change that trigger the previous message.

SQDX027I

SQL : <fullkey>

This message follows a warning or error on an IMS Apply operation. It provides details on the Full Key associated with that error or warning. Non-displayable characters are substituted by dot. If any character needed to be substituted, this message is followed by a hexadecimal dump of the full key.

SQDX028E

Apply error on <operation> for table <table_name> rc=<rc> <msg>

An Apply operation was in error. This message provides details about the nature of the compensation. This message is followed by a SQDX026I message that contains the SQL statement involved in the error.

SQDX028W

Apply error on <operation> for table <table_name> rc=<rc> <msg>

An Apply operation was in error but was sent to an exception datastore. This message provides details about the nature of the compensation. This message is followed by a SQDX026I message that contains the SQL statement involved in the error.

SQDX029E

Error retrieving dsname for a VSAM file <file> (<rc>:<cics_rc>:<cics_rs>)

An inquiry to determine the dsname associated with a CICS file failed.

SQDX030E

Error retrieving the CI of file <ddn> dsn:<dsname>

An inquiry to determine the CI of a CICS file has failed.

SQDX031E

Error Starting the CICS transaction <txn_name> (<rc>:<cics_rc>:<cics_rs>)

Starting the CICS Apply transaction failed.

SQDX032E

Error Committing CICS (<rc>:<cics_rc>:<cics_rs>)

Starting the CICS Commit transaction failed.

SQDX033E

Error Starting the subtask for a CICS transaction <txn_name> (<rc>:<reason_code>)

Starting the subtask for a CICS Apply transaction failed.

SQDXBA1I

Transaction Information:

Announces the be genning of a series of messages describing the details of an IMS transaction involved in a compensation, warning, or a replication error.

SQDXBA2I

User: <user> Region Type: <region> Program: <program>

Indicates the user, region type, and program name associated with an IMS transaction.

SQDXBA3I

PSB: <psb> TXN Name: <txn_name>

Indicates the PSB name and transaction name of an IMS transaction.

SQDXBA4I

UOW:

Indicate the transaction ID (unit of work ID) of an IMS transaction. This is displayed in hexadecimal.

SQDXP01E

The area <area_name> of dbd <database_name> has no route defined

The specified area does not have any route associated with it.

SQDXP02E

The database <database_name> is not compatible with AREA routing

The specified database is not a DEDB database, it cannot be used with AREA routing.

SQDXP03E

The DBD for database <database_name> is not found or could not be parsed

The DBD for the specified database could not be found or could not be parsed.

SQDXP04E

No Routes specified

The XPARM configuration did not specify any routes.

SQDXP05E

The database <database_name> is not compatible with PARTITION routing

The specified database is not a PARTITIONED database, it cannot be used with PARTITION routing.

SQDXP06E

The partition <part_name> of dbd <database_name> has no route defined

The specified partition does not have any route associated with it.

SQDXP07W

The partition <part> of dbd <database> has non-default randomizer, must specify USE INDEX for IMS check

The specified partition has a non-default randomizer. Must specify USE INDEX for IMS checker.

SQDY000I

At <filename> (<line>:<column>)

Indicates a position by providing a filename, row, and column number. This message is normally used to provide context information for a subsequent message.

SQDY001E

Syntax Error: Missing <lexeme>

A syntax error was detected. The indicated lexeme appears to be missing at the location indicated by a message SQDY000I, prior to this message.

SQDY002I

<context>

Indicates the chain of includes that lead to a location. This is used to provide context information for a subsequent message.

SQDY003E

Syntax Error

A syntax error was detected at or around the location indicated by a message SQDY000I, prior to this message.

SQDY004E

Could not open file: <filename>

The specified file could not be opened.

SQDY005E

Duplicate instance of a <statement_type> statement

The specified statement occurs more than once. A message SQDY000I above this message indicates the location of the duplicate instance. A Message SQDY006I follows to indicate the first instance of this statement.

SQDY006I

First instance is located at

Follows a SQDY005E, introduced by a SQDY000I message that indicates the location of the first instance of the statement.

SQDY007E

Duplicate instance of a <statement_type> statement named < name>

The specified statement is specified more than once with the same name. A message SQDY000I above this message indicates the location of the duplicate instance. A Message SQDY006I follows to indicate the first instance of this statement.

SQDY008W

Orphan <statement_type> statement named < name>

The specified statement appears more than once with the same name. A message SQDY000I above this message indicates the location of the duplicate instance. A Message SQDY006I follows to indicate the first instance of this statement.

SQDY009E

Missing clause <clause_name> in <statement_type> statement named <statment_named>

The designated clause is missing in the indicated statement.

SQDY010E

Could not determine clause <clause_name> from <statement_type> statement named <statement_named>

The designated clause is missing in the indicated statement and from every one of its parent statements.

SQDY011I

From <filename> (<line>:<column>)

Indicates the beginning of an element, providing a filename, line and column numbers. This message is followed by a message SQDY012I, that indicates the end position of the element. This message is normally used to provide context information for a subsequent message.

SQDY012I

To <filename> (<line>:<column>)

Indicates the end of an element, providing a filename, line and column numbers. This message is preceded by a message SQDY011I, that indicates the beginning of the element. This message is normally used to provide context information for a subsequent message.

SQDY013E

Clause or attribute <clause_name> above conflict with clause <clause_name> below

The indicated clauses or attributes that conflict with each other, are exclusive of one another, or are duplicate.

SQDY014E

Clause <clause> is invalid or unsupported

The indicated clause is invalid or unsupported.

SQDY015E

Duplicate <clause> <name>

The indicated variable or parameter is non-unique.

SQDZ001W

Out of order commit record in stream <stream> by <#> micro-sec

We were about to publish out-of-order from the indicated stream. This message occurs when we are about to publish a commit that has a storeclock associated with it that is lower than a preceding commit we have already pushed in that same session. This is preceded by a pair of SQDZ002I messages that give details on the two commits involved.

SQDZ002I

txn id:<trans_id> stck:<store_clock> (<timestamp>)

This message is paired with a SQDZ001W message giving details of the out-of-order commits.

SQDZ003E

Error while processing stream <stream> to target <target> : <rc>

The thread capturing data to queue(s) was stopped due to the indicated error.

SQDZ004E

Error while processing stream <stream> to target <target>, errno:<errno> (<strerror>)

The thread capturing data to queue(s) was stopped due to the indicated error.

SQDZ005W

Latency for <stream> ( <latency> sec.) is high

The latency (in second) for the specified log stream rose above the high threshold. The latency is calculated based on the storeclock of the most recent record in the stream and the oldest one that cannot be deleted. This can rise due to the downstream consumer not consuming fast enough compared to the rate of capture, or it can be because of poor transaction pattern, since the latency is at least equal to the longest running transaction being captured.

SQDZ006I

Latency for <stream> is back to normal

Indicates that the latency for the given stream has fallen back below the low threshold for that stream. This follow a SQDZ005W message that indicated a problem with a high latency.

SQDZ007I

Target <target> disconnected from stream capture <stream> at <stck> (<timestamp>)

The thread capturing data to queue(s) was stopped due to a target disconnection.

SQDZ008I

Target <target> is connected

Indicates the start of a target connection thread.

SQDZ009I

Target <target> disconnected

The thread capturing data to queue(s) was stopped due to a target disconnection.

SQDZ010W

Target <target> stream <stream>

Indicates the target and stream associated with the following message.

SQDZ011W

Stall txn id <hexid> → <txnid> no record for <duration> seconds

An in-flight transaction is stall. It has not seen a new record for the given number of seconds.

SQDZ012I

Starting Cleaner with safe restart stck:<bid> (<stck>)

The zLOGC cleaner is starting.

SQDZ013I

Ending Cleaner with safe bid: <bid> safe restart stck:<stck> (<tst>)

The zLOGC cleaner is ending.

SQDZ014I

Ending Receive Proc for target <name> safe bid: <bid>

The zlogc target receive proc is ending.

SQDZ015I

Stall txn head bid:<bid> head_stck:<stck> flags:<flags>

An in-flight transaction is stalled at the given head bid and head stck.

SQDZ016W

Possible stream overclean for <stream> (<local_ack>:<safe_stck>) (<local_ack>:<safe_stck>

First zlog delete issued.

SQDZ017E

Error connecting to stream <stream> IGXCONN reason code:<reason_code>

An error occurred while connecting to the specified stream. See the IGXCONN reason_code for more details.

SQDZ018I

Target <target> pausing at <stck>

Publishing to the specified target will pause once it reach the indicated storeclock.

SQDZ019I

Target <target> is paused at <stck>

Publishing to the specified target has paused from the indicated storeclock.

SQDZ020I

Target <target> has resumed

Publishing to the specified target has resumed.

SQDZ021I

Target <target> connected as paused

The target was connected to but it’s last status was paused so it restarted as paused.

SQDZ022I

Target <target> skipped from <old_stck> to <new_stck> due to resume --at

The target was connected and a previous resume --at triggered a jump forward in the log. All transactions that committed between the two specified log point are skipped.

SQDZ023I

Publisher Pause request

The publisher has received a requested to globally pause.

SQDZ024I

Publisher Resume request

The publisher has received a request to globally resume.

SQDZ025I

Setup zlog <stream> for target <target> restarting at:<stck> (<timestamp>)

Starting zlog browsing at specified point for the target indicated.

SQDZ026I

Setup zlog <stream> for target <target> restarting at start active. requested was <stck> (<timestamp>)

Starting zlog browsing at the beginning of the active log for target indicated. due to a required restart stck not in range

SQDZ027I

Setup zlog <stream> for target <target> restarting at start active.

Starting zlog browsing at the beginning of the active log for target indicated.

SQDZ028I

Disconnect zlog <stream> for target <target> current stck:<stck> (<timestamp>)

Disconnect stream for the giver target

SQDZ029I

<name> safe restart stck:<stck> (<timestamp>) last ack stck = <stck> (<timestamp>)

The zlogc target receive proc is ending.

SQDZ900I

Write pacing not active for zlog <stream>. <reason>

Write pacing is not in effect for the log stream for the indicated reason.