The following error messages are generated by Net.Data when it it completes an operation or detects an error.
| DTWA000E | Net.Data detected an internal error <error_type>. |
Explanation: Net.Data has detected the specified internal error.
User Response: Correct the specified error and try again. Contact your Net.Data administrator for assistance.
| DTWA001E | Net.Data detected an invalid or missing value for the variable <variable_name>. |
Explanation: Net.Data has detected an invalid or missing value for the specified variable.
User Response: Specify a valid value for the specified variable and try again. See the Net.Data Reference for more information about valid variable values.
| DTWA002E | Net.Data is unable to locate the function <function_name>. |
Explanation: Net.Data was unable to locate the specified function.
User Response: The specified function does not exist in the macro file. Specify a valid function and try again.
| DTWA003E | Net.Data detected a null value in parameter <parameter_name>. |
Explanation: Net.Data has detected a null value in the specified parameter.
User Response: Ensure that the specified parameter contains a non-null value and try again.
| DTWA004E | Net.Data detected an invalid number of parameters <paramemter_names>. |
Explanation: Net.Data has detected an invalid number of parameters specified.
User Response: Ensure that the correct number of parameters are specified and try again.
| DTWA005E | Net.Data is unable to process the file <file_name>. |
Explanation: Net.Data was unable to process the specified file because the file does not exist or Net.Data was not able to open it.
User Response: Ensure the specified file exists and that Net.Data has the proper authority and try again.
| DTWA006E | The Net.Data evaluation license has expired. |
Explanation: A valid license is needed to use Net.Data.
User Response: Purchase and install a valid Net.Data license and try again.
| DTWA007E | The syntax of the QUERY_STRING variable for the URL is invalid. |
Explanation: The syntax of the QUERY_STRING variable for the URL is invalid.
User Response: Correct the QUERY_STRING variable and try again.
| DTWA008E | The content type of the input data in the HTML POST method is not correct. |
Explanation: The content type of the input data in the HTML POST method should be "application/x-www-form-urlencode", but is not.
User Response: Please check your browser MIME types to correct the content type and try again.
| DTWA009E | Net.Data is unable to allocate memory from the operating system. |
Explanation: The system is out of memory so that Net.Data is unable to allocate the space needed.
User Response: Check your operating system status, specifically the virtual memory. If the virtual memory is too low, increase the available memory space.
| DTWA010E | The CGI variable <variable_name> has an invalid value of <variable_string>. |
Explanation: The specified CGI variable has an invalid value.
User Response: Check that the web server is specifying a correct value for the specified CGI variable and try again.
| DTWA014E | Net.Data detected an invalid number of parameters at line number <number>. |
Explanation: Net.Data has detected an invalid number of parameters were specified.
User Response: Ensure that the correct number of parameters are specified and try again.
| DTWA016E | LicDemo: Error creating license control file. |
Explanation: Net.Data could not establish a try-and-buy license for the evaluation period.
User Response: This may be an internal Net.Data Error. Make sure you have at least 2KB free space on the hard drive where Net.Data is installed. If so, then contact IBM technical support.
| DTWA017I | This site is using a temporary license for Net.Data. There are <days_remaining_value> days remaining in the evaluation period, starting from <date>. |
Explanation: Your trial period for Net.Data has begun. You will be able to use Net.Data for a certain number of days after which, you must enroll a production license for Net.Data or it will stop functioning.
User Response: A production license can be obtained from IBM or the supplier where you got this evaluation copy of Net.Data. To perform this operation please refer to the documentation in the Installing Net.Data Licenses section.
| DTWA018I | This site is using a temporary license for Net.Data. There are <days_remaining_value> days remaining in the evaluation period. |
Explanation: This message will appear on the first day of your trial period and infrequently on certain days during your trial period. You will be able to use Net.Data for the specified number of days after which, you must enroll a production license for Net.Data or it will stop functioning.
User Response: A production license can be obtained from IBM or the supplier where you got this evaluation copy of Net.Data. To perform this operation please refer to the documentation in the Installing Net.Data Licenses section.
| DTWA019E | The trial period for Net.Data has expired. You must enroll Net.Data with a production license for it to run. |
Explanation: This message will appear when the trial period for Net.Data has expired.
User Response: A production license can be obtained from IBM or the supplier where you got this evaluation copy of Net.Data. To perform this operation please refer to the documentation in the Installing Net.Data Licenses section.
| DTWA020E | No valid Net.Data license control file found. Net.Data will end. |
Explanation: This message will appear when Net.Data is unable to locate and verify the Net.Data license control file.
User Response: A production license can be obtained from IBM or the supplier where you got this evaluation copy of Net.Data. To perform this operation please refer to the documentation in the Installing Net.Data Licenses section.
| DTWA021W | Net.Data is unable to open a codepage converter from <codepage1_name> to <codepage2_name>. Net.Data is switching to default processing. |
Explanation: An invalid codepage was specified for one or more of the variables DefaultNetCp, DefaultFsCp, or DefaultDBCp. The default processing is as follows:
User Response: Verify that the codepages specified in the Web server's configuration file for DefaultNetCp and DefaultFsCp, and the codepage specified in the Net.Data initialization file for DefaultDBCp are correct.
| DTWC000E | Live Connection Manager detected an error in its internal protocol. Live Connection Manager expected message <expected_message> but received message <received_message>. |
Explanation: Live Connection Manager has detected an internal communication protocol error.
User Response: Report the problem to your system administrator.
| DTWC001E | The Live Connection internal function <function_name> failed with code <return_code>. |
Explanation: Live Connection has detected an internal function failure.
User Response: Report the problem to your system administrator.
| DTWC002E | The Live Connection internal function <function_name> failed with code <return_code_value>. |
Explanation: Live Connection has detected an internal function failure.
User Response: Report the problem to your system administrator.
| DTWC003E | Live Connection unable to start all cliettes for cliette group <cliette_group_name>. |
Explanation: Live Connection was unable to start all cliettes for the specified cliette group.
User Response: Report the problem to your system administrator.
| DTWC004W | Live Connection unable to locate a cliette to handle request for cliette group <cliette_group_name>. |
Explanation: Live Connection was unable to find a cliette to handle request for the specified cliette group.
User Response: Check that the cliette group was properly configured in the Live Connection configuration file.
| DTWC005E | Live Connection Manager could not read configuration file <file_name>. |
Explanation: Live Connection Manager was unable to read the specified configuration file.
User Response: The specified configuration file could not be correctly read. Check that the file can be accessed and that the configuration statements inside the file are correct.
| DTWC006E | The Live Connection cliette detected an error in its internal protocol. The cliette expected message <expected_message> but received message <received_message>. |
Explanation: The Live Connection cliette detected an internal communication protocol error.
User Response: Report the problem to your system administrator.
| DTWC007E | The Live Connection internal function <function_name> failed. The operating system returned the following error message: <system_error>. |
Explanation: Live Connection has detected an internal function failure.
User Response: Report the problem to your system administrator.
| DTWF000E | Net.Data is unable to locate the configuration path variable <variable_name>. |
Explanation: The specified path variable must be defined in order for Net.Data to execute.
User Response: Define the specified variable and try again.
| DTWF004E | Net.Data detected a cyclic variable definition <var_def_name>. |
Explanation: Net.Data variable definitions cannot be self-referencing.
User Response: Check the specified variable definition in the defined section in your macro file and try again.
| DTWF005E | Net.Data has detected an undefined table name <table_name>. |
Explanation: A Net.Data table variable should be defined as x=Table(number).
User Response: Check your macro file to make sure your table variable is defined and try again.
| DTWF006E | Net.Data has exceeded the maximum string length. |
Explanation: The maximum string length that Net.Data can handle is 320,000 characters.
User Response: Check your macro file for the length of variable name or function name, correct the length, and try again.
| DTWF007E | Net.Data has detected an invalid form data entry. |
Explanation: An entry in the form data has no name and a variable name was expected. For example, the form data may look like &;=field.
User Response: Check the form data and provide a name in the illegal entry and try again.
| DTWF008E | Net.Data detected a missing equal sign (=) in the form data. |
Explanation: Form data requires the format variable_name=variable_value.
User Response: Provide an equal sign (=) in the invalid form data and try again.
| DTWF010E | Net.Data has encountered a missing database name in the form data. |
Explanation: The database language environment entry must have a database name.
User Response: Check the form data, provide a database name in the database language environment entry, and try again.
| DTWF011E | Net.Data has detected that a language environment was not specified. |
Explanation: The language environment entry in the form data must have a language environment entry.
User Response: Check the form data, provide a language environment entry, and try again.
| DTWF012E | Net.Data has detected that a query was not specified. |
Explanation: The form data contains a database language environment, but the query is missing.
User Response: Check the form data, provide a query, and try again.
| DTWF013E | Net.Data has detected that a function was not specified. |
Explanation: The form data must have a function specification.
User Response: Check the form data and provide a function specification and try again.
| DTWF014E | Net.Data has detected that the form data does not define the variable <variable_name>. |
Explanation: The form data referenced a variable that is not defined.
User Response: Check the form data, define the corresponding variable, and try again.
| DTWF015E | The system command failed at line number <number> with return code <return_code> |
Explanation: After running the system command, Net.Data obtained the non-zero system error code. This usually implies the failure of the execution.
User Response: Check the syntax of the system command at the specified line. Try running the system command from the command line to verify there is an error.
| DTWF016E | Net.Data is unable to open the configuration file <file_name>. |
Explanation: Net.Data is unable to find or open the configuration file.
User Response: Make sure that the Net.Data configuration file is in the server's HTML root directory and ensure that the access permission for the file is read and write.
| DTWF017E | Net.Data is unable to read the configuration file <file_name>. |
Explanation: Net.Data is able to find the configuration file but unable to read it.
User Response: Ensure that the access permission for the file is read.
| DTWF018E | Net.Data detected an SQL statement that exceeds the maximum length. |
Explanation: The maximum character length for an SQL statement is 32000 bytes.
User Response: Rewrite the SQL statement to make it shorter, such as breaking it down into shorter SQL statements and then combining the results, and try again.
| DTWF019E | Net.Data failed to connect to the language environment <lang_envir_name>. |
Explanation: Net.Data has failed to connect to the specified language environment.
User Response: If Live Connection Manager is used, make sure that the Live Connection Manager is configured and running correctly. If a database language environment is used, check with your database administrator.
| DTWF021E | Net.Data replaced the value of the built-in variable <variable_name>. |
Explanation: Net.Data has overridden the user set value of the specified built-in variable.
User Response: Ensure that the built-in variable is not overridden inadvertently, as built-in variables are usually designed for read-only, and try again.
| DTWF022E | Net.Data detected an invalid table name <table_name>. |
Explanation: The value of the variable DTW_SAVE_TABLE_IN is an invalid table name.
User Response: Ensure that the variable DTW_SAVE_TABLE_IN contains a valid table name and try again.
| DTWF023E | Net.Data is unable to execute the SQL statement <SQL_stmt>. |
Explanation: Net.Data was unable to execute the specified SQL statement.
User Response: Check the SQL statement, along with any database error messages, and try again.
| DTWF031E | Net.Data encountered a missing variable definition. |
Explanation: Net.Data has attempted to delete a cycle variable from a temporary cycle table. However, this variable does not exist or has already been removed.
User Response: Report the problem to your system administrator.
| DTWF032E | Net.Data is unable to load DLL <DLL_name>. |
Explanation: Net.Data has encountered an internal failure due to a possible lack of memory. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWF033E | Net.Data is unable to find the execute process address for DLL <DLL_name>. |
Explanation: Net.Data has attempted to find address for the specified DLL to load. Either the memory is corrupted or the pointer contains an invalid address.
User Response: Report the problem to your system administrator.
| DTWF034E | Net.Data is unable to close database connection. |
Explanation: The database might not exist or it has already been closed.
User Response: Report the problem to your system administrator.
| DTWF036E | The database ROLLBACK failed. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error. For example, the application tries to insert 10 rows in the database table and commit if success. For some reasons, it cannot fulfill to insert all and try rolling back to undo the job, and it cannot.
User Response: Report the problem to your system administrator.
| DTWF037E | Net.Data encountered an unexpected NULL command for execution. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWF038E | Net.Data detected a NULL pointer in <name>. |
Explanation: Net.Data has encountered an internal failure. The new operator might have returned a NULL value, or there might not be enough memory.
User Response: Report the problem to your system administrator.
| DTWF039E | Net.Data failed to fetch the next record from the database: <error_trace_info>. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWF040E | Net.Data failed to close the database cursor: <error_trace_info>. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWF041E | Net.Data did not find the global alias table. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWF043E | The Net.Data function, process_output, did not find the RETURN_CODE variable. A null string is used as the return code of the function. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWF045E | Net.Data is unable to find the execute process address for DLL <DLL_name>:<error_info>. |
Explanation: Net.Data has attempted to find address for the specified DLL to load. Either memory is corrupted or the pointer contains an invalid address.
User Response: Report the problem to your system administrator.
| DTWF046E | Net.Data detected an invalid language environment <lang_envir_name> at line number <number>. |
Explanation: Net.Data has detected an invalid language environment statement in the INI file.
User Response: See Net.Data Language Environment Reference for more information. Specify a valid language environment and try again.
| DTWF047E | Net.Data failed to run a function in a language environment of type <lang_envir_name> at line number <number>. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWF048E | Net.Data encountered a missing variable definition for variable <variable_name>. |
Explanation: Net.Data has attempted to delete the specified cycle variable from a temporary cycle table. However, this variable does not exist or it has already been removed.
User Response: Report the problem to your system administrator.
| DTWF049E | Net.Data detected an invalid input in a conditional statement. |
Explanation: Net.Data has determined that the input contained in a %IF or %ELSEIF conditional statement is incorrect..
User Response: See Net.Data Reference for syntax information. Correct the conditional statement and try again.
| DTWF050E | Net.Data is unable to locate the HTML block specification in the URL. |
Explanation: No HTML block was specified in the URL.
User Response: Specify a valid HTML block and try again.
| DTWF051E | Net.Data has detected an incorrect parameter passing specification in the stored procedure parameter list for the form data. The parameter passing specification <parameter_passing_specification> must be IN, OUT, or INOUT. |
Explanation: Usage in stored procedure parameter list must be one of the key words IN, OUT, or INOUT.
User Response: Correct the usage specification.
| DTWF052E | Net.Data has encountered a missing type specification in the stored procedure parameter list in the form data |
Explanation: Stored procedure parameter has to contain a specification of the data type.
User Response: Correct the stored procedure parameter, provide a data type.
| DTWF053E | Net.Data has encountered a missing parameter value in the stored procedure parameter list in the form data |
Explanation: The value for a stored procedure input parameter is missing.
User Response: Correct the stored procedure parameter, provide the value.
| DTWF054E | Net.Data has encountered a missing quote at the end of a parameter value in the stored procedure parameter list in the form data |
Explanation: The parameter value started but did not end with a quote.
User Response: Correct the parameter value, put a quote at its end.
| DTWF055E | Net.Data has detected an invalid parameter list in the form data. |
Explanation: The parameter list for a function call is invalid.
User Response: Correct the parameter list.
| DTWF056E | Net.Data has detected that the SQL or FUNC entry in the form data is empty |
Explanation: Entry FUNC or SQL must specify a function call or a SQL query.
User Response: Provide a function call or a SQL query for entry FUNC or SQL in the form data.
| DTWF057E | Net.Data failed to retrieve the next result set from the database: <error_trace_info>. |
Explanation: Net.Data encountered an error while attempting to retrieve the next result set from the database.
User Response: Check the database error message. Also verify that the SQL statement returns the correct number of result sets.
| DTWF058E | Net.Data detected a table as a IN parameter in the parameter list of function <function_name>. |
Explanation: Net.Data tables cannot be passed into a Net.Data function if this function connects to a database language environment.
User Response: Change the function parameter list.
| DTWF059I | Net.Data is unable to execute this request because Direct Request is not available |
Explanation: Direct Request has been disabled.
User Response: If the URL was not in error, set DTW_DIRECT_REQUEST to "yes" in the Net.Data initialization file
| DTWG000E | Net.Data found an existing registry <registry_name>, in function <function_name>. |
Explanation: The specified registry name has already been used to define an existing registry name. The specified registry name must be unique.
User Response: Remove the specified registry variable first or specify a unique registry name and try again.
| DTWG001E | Net.Data is unable to locate the registry <name> in function <name>. |
Explanation: Net.Data was unable to locate the specified registry.
User Response: The specified registry does not exist or it is in use by another process. Specify a valid registry and try again.
| DTWG005E | Net.Data is unable to perform the requested registry operation <operation_name> in function <function_name>. |
Explanation: The registry operation failed because your user ID lacks the proper authorization to perform the requested registry operation.
User Response: Obtain the proper authorization and try again.
| DTWH000E | Net.Data detected an internal error in the cache manager interface. |
Explanation: Net.Data detected an internal error in the cache manager interface.
User Response: Report the problem to your system administrator.
| DTWH001E | Net.Data detected an invalid cache name <name>. |
Explanation: Net.Data was unable to locate the specified cache name.
User Response: Check the macro file and correct the cache name and try again.
| DTWH002E | Net.Data detected an insufficient number of parameters to the cache function. |
Explanation: Not enough parameters were used when calling the Net.Data cache function.
User Response: Check the macro file and correct the function call and try again.
| DTWH003E | Net.Data detected too many parameters supplied to the cache function. |
Explanation: Too many parameters were supplied when calling the Net.Data cache function.
User Response: Check the macro file and correct the function call and try again.
| DTWL000E | Net.Data detected an invalid value in the parameter <parameter_name> in function <function_name>. |
Explanation: Net.Data has detected an invalid data type value in the specified parameter.
User Response: Ensure that the specified parameter contains a valid data type and try again.
| DTWL001E | Net.Data detected an invalid value in the variable <name> in function <name>. |
Explanation: Net.Data has detected an invalid value in the specified variable.
User Response: Ensure that the specified variable contains a valid data type and try again.
| DTWL002E | Net.Data detected different parameter lists for the same functions at line number <number>. |
Explanation: Net.Data has detected that the specified functions have different parameter lists. The specified functions are required to have identical parameter lists.
User Response: Correct the specified functions parameter lists and try again.
| DTWL003E | Net.Data detected that a data type parameter is missing on the %FUNCTION statement <name>. |
Explanation: Net.Data could not find a required data type parameter in a macro used to call an SQL stored procedure.
User Response: Check the %FUNCTION(DTW_SQL) statements in your macro file. Ensure that each variable to be passed to an SQL stored procedure has a data type defined for it.
| DTWL004E | Net.Data detected that the parameter value <parameter_name> is outside of the table bounds in function <function_name>. |
Explanation: One of these conditions exists: A program attempted to modify a table's row or column value, but the row or column value received was less than 0 or greater than the maximum number of rows allowed in the table. Or, A row or column value was received as input to a built-in function, but the value received was less than 0 or greater than the current number of rows or columns in the table.
User Response: Ensure the specified value is not less than 0 or greater than the current number of rows in the table.
| DTWL005E | Net.Data is unable to return all requested data in the table variable <variable_name> in function <variable_name>. |
Explanation: A table was specified as an output parameter, but the number of rows of data returned by the language environment was greater than the maximum number of rows allowed for the table. Data was written to the table until it was full, and the remainder of the data was discarded.
User Response: You can ignore the discarded data, or increase the table size and run the function again.
| DTWL006E | Net.Data attempted to read a row of data that exceeded the maximum supported number of bytes in function <function_name>. |
Explanation: A built-in function for the flat file interface could not read a row of data into a table variable because the number of bytes in the row exceeded the maximum supported number of bytes. The table is too large for Net.Data to handle.
User Response: Correct the error and try again.
| DTWL007E | Net.Data encountered a path specified in FFI_PATH exceeded the maximum supported number of bytes in function <function_name>. |
Explanation: A built-in function for the flat file interface attempted to find a file, but encountered a path in the FFI_PATH configuration file variable that was longer than the maximum supported number of bytes of 4095.
User Response: Shorten the FFI_PATH statement to only those directories Net.Data needs for the current application.
| DTWL008E | Net.Data detected an arithmetic overflow or underflow in function block <block_name>. |
Explanation: The result of an arithmetic operation had an exponent that was outside the supported range of -999,999,999 to +999,999,999.
User Response: Ensure that your calculated values stay within the supported range.
| DTWL009E | Net.Data detected an empty EXEC statement in function block <block_name>. |
Explanation: The string specified in the EXEC statement of a function block contains only space characters.
User Response: Specify a string that is not all space characters and try again.
| DTWL010E | Net.Data detected a missing EXEC statement in a function block <block_name>. |
Explanation: A EXEC statement was not specified in the function block for the function being called.
User Response: Add the EXEC statement in the FUNCTION block and try again.
| DTWL011E | Net.Data detected an invalid language environment type or DLL <DLL_name>. |
Explanation: The Net.Data specified language environment type or DLL name in macro file must be defined in the Net.Data configuration file.
User Response: Check your macro file and Net.Data configuration file db2www.ini and try again.
| DTWL012E | Net.Data encountered an internal failure in the function <function_name>, failure code <failure_code_value>. |
Explanation: Net.Data has encountered an internal failure in the specified function. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWL013E | Net.Data is unable to allocate memory for the function <function_name>. |
Explanation: The server could not process a request for storage from Net.Data.
User Response: This might be a temporary condition in your server. If this problem persists, you may need to purchase more memory.
| DTWL015E | Net.Data detected an invalid table parameter <parameter_name> in function <function_name>. |
Explanation: Net.Data has detected that the specified parameter is not valid for a table.
User Response: See Net.Data Reference for more information about table parameter values. Ensure that the correct parameter type is specified and try again.
| DTWL016E | Net.Data detected an invalid string parameter <parameter_name> in function <function_name>. |
Explanation: Net.Data has detected that the specified parameter is not a valid string.
User Response: Ensure that the correct string parameter is specified and try again.
| DTWL017E | Net.Data detected an invalid output parameter <parameter_name> in function <function_name>. |
Explanation: Net.Data has detected that the specified parameter is not a valid output parameter.
User Response: Ensure that the correct output parameter is specified and try again.
| DTWL018E | Net.Data detected a null value in parameter <parameter_name> in function <function_name>. |
Explanation: Net.Data has detected a null value in the specified parameter.
User Response: Ensure that the specified parameter contains a non-null value and try again.
| DTWL019E | Net.Data detected an invalid output parameter at line number <number>. |
Explanation: Net.Data has detected that the specified parameter is not a valid output parameter.
User Response: Ensure that the correct output parameter is specified and try again.
| DTWL021E | Net.Data encountered an internal error in function <function_name>: <additional_information>. |
Explanation: A call to a system function failed. This is an internal error reported to Net.Data that may require user interaction or it may be a temporary system error that is not appropriate for Net.Data to handle.
User Response: Check your configuration and try again. If this problem persists, report the problem to your system administrator.
| DTWL022E | Net.Data is unable to process the function <function_name> in file <file_name>. |
Explanation: Net.Data was unable to process the specified file because the file does not exist or Net.Data was not able to open, possibly due to incorrect read permissions.
User Response: Ensure the specified file exists and that Net.Data has the proper authority and try again.
| DTWL023E | Net.Data detected an invalid number of parameters in function <function_name>. |
Explanation: Net.Data has detected an invalid number of parameters specified.
User Response: Ensure that the correct number of parameters are specified and try again.
| DTWL024E | Net.Data is unable to return all requested data in function <function_name>. |
Explanation: A table was specified as an output parameter, but the number of rows of data returned by the language environment was greater than the maximum number of rows allowed for the table. Data was written to the table until it was full, and the remainder of the data was discarded.
User Response: You can ignore the discarded data, or increase the table size and run the function again.
| DTWL025E | Net.Data detected an invalid value in function <function_name>. |
Explanation: Net.Data has detected an invalid value in the specified function.
User Response: Ensure that the specified variable contains a valid data type and try again.
| DTWL026E | Net.Data detected a null value in function <function_name>. |
Explanation: Net.Data has detected a null value in the specified function.
User Response: Ensure that the specified parameter contains a non-null value and try again.
| DTWL027E | Net.Data detected an invalid string parameter in function <function_name>. |
Explanation: Net.Data has detected that the specified parameter is not a valid string.
User Response: Ensure that the correct string parameter is specified and try again.
| DTWL028E | Net.Data detected an invalid table parameter in function <function_name>. |
Explanation: Net.Data has detected that the specified parameter is not a valid table.
User Response: Ensure that the correct table parameter is specified and try again.
| DTWL029E | Net.Data detected an invalid output parameter in function <function_name>. |
Explanation: Net.Data has detected that parameter is not a valid output parameter.
User Response: Ensure that the correct output parameter is specified and try again.
| DTWL031E | The specified SMTP server <SMTP_server> cannot be reached. |
Explanation: Net.Data is unable to connect to the specified SMTP server.
User Response: Make sure that you have specified the correct hostname or IP number. An SMTP server must be running on port 25 on the specified host.
| DTWL032E | While communicating with the specified SMTP server, the SMTP server returned the following error message: <SMTP_error_message>. |
Explanation: An SMTP error occurred while Net.Data tried to relay the e-mail message to the specified SMTP server.
User Response: Make sure that you call DTW_SENDMAIL with valid parameters.
| DTWL033E | The connection to the specified SMTP server has been lost. |
Explanation: The TCP/IP connection to the specified SMTP server was lost while Net.Data tried to relay the e-mail message to the SMTP server.
User Response: Make sure that the specified SMTP server is up and running and try again.
| DTWL034E | The specified SMTP server does not support the Extended Simple Mail Transfer Protocol (ESMTP), but the specified e-mail message contains non-U.S. ASCII characters. |
Explanation: Net.Data cannot relay e-mail messages that contain 8-bit characters to an SMTP server that supports 7-bit characters only.
User Response: Either specify an SMTP server that supports ESMTP (8BITMIME) or do not use non-U.S. ASCII characters in your e-mail messages.
| DTWL035I | The Net.Data function DTW_GETCOOKIE attempted to retrieve a nonexistent cookie: <cookie name>. |
Explanation: The cookie cannot be found for one of the following reasons:
http://home.netscape.com
User Response: Use a MESSAGE block to handle the cookie-not-found condition (RETURN_CODE 8000), or make sure that the cookie name is correctly specified.
| DTWP000E | Net.Data detected a LIST definition error <file>. |
Explanation: Net.Data was unable to define the specified %LIST as it was previously declared.
User Response: Change the specified %LIST name to a unique name and try again.
| DTWP001E | Net.Data is unable to locate the macro file <macro_name>. |
Explanation: Net.Data was unable to locate the specified macro file because the specified macro file does not exist or Net.Data was not able to open it.
User Response: Specify a valid macro path and macro file name and try again.
| DTWP003E | Net.Data detected a duplicate HTML block name <block_name> <file>. |
Explanation: Net.Data was unable to continue processing as a duplicate specified HTML block exists.
User Response: Change the specified duplicate HTML block name to a unique name and try again.
| DTWP005E | Net.Data detected an illegal symbol <symbol_name> <file>. |
Explanation: Net.Data was unable to continue processing because it detected the specified illegal symbol.
User Response: Remove the specified illegal symbol from the macro file and try again.
| DTWP006E | Net.Data detected an unexpected end of macro file <macro_name>. |
Explanation: Net.Data was unable to continue processing because it detected an unexpected end of file.
User Response: Ensure that all Net.Data blocks end with %}. Correct the specified error and try again.
| DTWP007E | Net.Data is unable to process the %INCLUDE_URL address <URL_address>. |
Explanation: Net.Data was unable to include the %INCLUDE_URL address specified URL because the URL was unreachable or invalid.
User Response: Ensure that the specified %INCLUDE_URL exists and that the Web server is running. Correct the specified error and try again.
| DTWP009E | Net.Data detected a quoted string, <string_name> that crosses multiple lines. |
Explanation: A quoted string cannot exceed more than one line.
User Response: Ensure that the string both begins with and ends with quotes on the same line. Correct the specified error and try again.
| DTWP010E | Net.Data is unable to process the %INCLUDE statement for the file <file_name>. |
Explanation: Net.Data was unable to process the %INCLUDE statement because the specified file does not exist or Net.Data was not able to open it.
User Response: Ensure that the specified file exists and that Net.Data has read authority. Correct the specified error and try again.
| DTWP011E | Net.Data is unable to process the %INCLUDE or %INCLUDE_URL statement for the file or URL <file_or_URL_name> because it is nested too deeply. |
Explanation: Net.Data was unable to process the %INCLUDE or %INCLUDE_URL statement because the file or URL because it is nested too deeply. The maximum number of nested %INCLUDE statements or blocks is 10.
User Response: Ensure that the specified %INCLUDE file or %INCLUDE_URL does not include other files to a nested depth of 10 or greater. Correct the specified error and try again.
| DTWP013E | Net.Data encountered an exception in D2Wtable_ErrRange, <exception_name> |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWP014E | Net.Data encountered an exception in D2Wtable_ErrNoMemory, <exception_name>. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWP015E | Net.Data encountered an exception in D2Wtable_ErrInvalid, <exception_name>. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWP016E | Net.Data encountered an exception in D2Wtable_ErrTooBig, <exception_name> |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWP018E | Net.Data detected the invalid use of the EXEC variable in an SQL command at line number <number>. |
Explanation: Net.Data has detected the invalid use of the specified EXEC variable and is unable to continue processing.
User Response: Ensure that the specified EXEC variable is not in an SQL command. Correct the specified error and try again.
| DTWP019E | Net.Data detected the invalid use of the EXEC variable in a Net.Data system variable at line number <number>. |
Explanation: Net.Data has detected the invalid use of the specified EXEC variable and is unable to continue processing.
User Response: Ensure that the specified EXEC variable is not in a Net.Data system variable. Correct the specified error and try again.
| DTWP020E | Net.Data detected the invalid use of the EXEC variable in an other EXEC variable definition at line number <number>. |
Explanation: Net.Data has detected the invalid use of the specified EXEC variable and is unable to continue processing.
User Response: Ensure that the specified EXEC variable is not in another EXEC variable definition. Correct the specified error and try again.
| DTWP021E | Net.Data detected the invalid use of the EXEC variable in a conditional string at line number <number>. |
Explanation: Net.Data has detected the invalid use of the specified EXEC variable and is unable to continue processing.
User Response: Ensure that the specified EXEC variable is not in a conditional string. Correct the specified error and try again.
| DTWP022E | Net.Data detected the invalid use of the EXEC variable in a List variable at line number <number>. |
Explanation: Net.Data has detected the invalid use of the specified EXEC variable and is unable to continue processing.
User Response: Ensure that the specified EXEC variable is not in a list variable. Correct the specified error and try again.
| DTWP023E | Net.Data detected the invalid use of the EXEC variable in an EXEC_SQL statement at line number <number>. |
Explanation: Net.Data has detected the invalid use of the specified EXEC variable and is unable to continue processing.
User Response: Ensure that the specified EXEC variable is not in a EXEC_SQL statement name. Correct the specified error and try again.
| DTWP025E | Net.Data expected ELSEIF/ELSE/ELIF and found IF <name>. |
Explanation: The nested %IF structure is invalid.
User Response: Check the nested IF structure in the macro file.
| DTWP026E | Net.Data detected IF statements nested too deeply <name>. |
Explanation: No more than 1024 IF statements can be nested within each other.
User Response: Check the nested IF structure in the macro file.
| DTWP027E | Net.Data detected an unmatched ELSEIF/ELSE/ELIF <name>. |
Explanation: There is an ELSEIF/ELSE/ELIF part without corresponding IF part.
User Response: Check the nested IF structure in the macro file.
| DTWP028E | Net.Data detected an unmatched ENDIF <name>. |
Explanation: There is an ENDIF statement without corresponding IF statement.
User Response: Check the nested IF structure in the macro file.
| DTWP029E | Net.Data is unable to locate the HTML block <block_name> in file <file>. |
Explanation: Either the specified HTML block does not exist in the macro file or no HTML block was specified.
User Response: Specify a valid HTML block and try again.
| DTWP030E | Net.Data detected multiple %REPORT blocks in function <function_name>. |
Explanation: Release 2 of Net.Data supports multiple %REPORT blocks only for DB2.
User Response: Use only one %REPORT block in the function.
| DTWP031E | Net.Data detected a variable reference, <string_name> that spans multiple lines. |
Explanation: A variable reference cannot exceed more than one line.
User Response: Ensure that the variable reference both begins with and ends on the same line. Correct the specified error and try again.
| DTWQ000E | Net.Data detected an error while allocating DB2 resources to run the specified plan: <plan_name> with SSID=<subsystem_id>, return code=<return_code>, reason=<addition_information>. |
Explanation: Net.Data has detected an error while processing an OPEN command. Please refer to the DB2 Messages and Codes guide for further explanation.
User Response: Please validate that your DB2 plan name and subsystem id are correct.
| DTWQ001E | Net.Data detected an error while deallocating DB2 resources: return code=<return_code>, reason=<additional_information>. |
Explanation: Net.Data has detected an error while processing a CLOSE command. Please refer to the DB2 Messages and Codes guide for further explanation.
User Response: Please notify the system programmer.
| DTWQ002E | Net.Data is unable to allocate SQLDA in function exec_start. |
Explanation: Net.Data has run out of memory and is unable to allocate SQLDA in function exec_start.
User Response: Free sufficient memory and try again.
| DTWQ003E | Net.Data is unable to allocate SQLDA host variables in function exec_start. |
Explanation: Net.Data has run out of memory and is unable to allocate SQLDA host variables in function exec_start.
User Response: Free sufficient memory and try again.
| DTWQ004E | Net.Data detected that a bind file is missing from the Net.Data initialization file. |
Explanation: Net.Data has determined that the value of the variable BIND_FILE is not set in db2www.ini.
User Response: Check db2www.ini to make sure that the variable BIND_FILE is set to the path and file name of the bind file and try again.
| DTWQ005E | The Net.Data ODBC language environment could not allocate the environment handle. |
Explanation: The Net.Data ODBC language environment could not allocate specified handle.
User Response: Verify the ODBC configuration and try again.
| DTWQ006E | The Net.Data ODBC language environment could not allocate the connection handle. |
Explanation: The Net.Data ODBC language environment could not allocate specified handle.
User Response: Verify the ODBC configuration and try again.
| DTWQ007E | The Net.Data ODBC language environment could not allocate the statement handle. |
Explanation: The Net.Data ODBC language environment could not allocate specified handle.
User Response: Verify the ODBC configuration and try again.
| DTWQ008E | The Net.Data ODBC language environment encountered an error loading the CLI initialization file: return_code=<return_code>, error_code=<error_code>, info_code=<info_code> |
Explanation: An invalid data set was specified in the Net.Data configuration file for the variable DSNAOINI.
User Response: Verify that the data set specified is a sequential data set, or a member of a partitioned data set. Verify that it points to a valid CLI initialization file, and the user has the proper READ authority.
| DTWQ009E | The Net.Data ODBC language environment encountered an error running DSNAOTRC: return_code=<return_code>, error_code=<error_code>, info_code=<info_code> |
Explanation: An invalid data set was specified in the Net.Data configuration file for the variable DSNAOTRC
User Response: Verify that the data set specified is a sequential data set, and the user has the proper UPDATE authority.
| DTWQ010E | Net.Data detected an invalid SQL Data Type: <sql_typ_name>. |
Explanation: Net.Data has detected an invalid SQL Data Type.
User Response: Specify a valid SQL Data Type and try again. See Appendix C. Net.Data Operating System Reference for a list of valid SQL Data Types with respect to your operating system.
| DTWQ011E | Net.Data encountered an error while initializing a connection to DB2 with the SSID <ssid_name>: return_code=<return_code_name>, reason_code=<reason_code_name>. |
Explanation: Net.Data encountered an error while processing an IDENTIFY to initialize a DB2 connection. Please refer to the DB2 Messages and Codes guide for further explanation.
User Response: Please validate that your DB2 subsystem id is correct and active.
| DTWQ012E | Net.Data encountered an error while assigning user <user_name> to a DB2 connection with the SSID <ssid_name>: return_code=<return_code_name>, reason_code=<reason_code_name> |
Explanation: Net.Data encountered an error while processing a SIGNON to assign a new authorization ID to a DB2 connection. Please refer to the DB2 Messages and Codes guide for further explanation.
User Response: Please validate that the user is authorized to connect to DB2.
| DTWQ013E | Net.Data encountered an error while allocating DB2 resources with the plan <plan_name> and SSID <ssid_name>: return_code=<return_code_name>, reason_code=<reason_code_name> |
Explanation: Net.Data encountered an error while processing a CREATE THREAD to allocate DB2 resources which is required to issue SQL. Please refer to the DB2 Messages and Codes guide for further explanation.
User Response: Please validate that the DB2 plan name is correct and that the correct DBRM is bound into the plan.
| DTWQ014E | Net.Data encountered an error while updating a connection to DB2 with the SSID <ssid_name>: return_code=<return_code>, reason_code=<reason_code> |
Explanation: Net.Data encountered an error while attempting to switch to the specified subsystem ID.
User Response: Verify that the DB2 subsystem is still active.
| DTWQ015E | Net.Data encountered a DB2 error: SQL code = <SQL_code>, reason code = <reason_code>. |
Explanation: Maybe new operator returns NULL because of not enough memory.
User Response: Report the problem to your system administrator.
| DTWQ016E | Net.Data detected an invalid SQL handle in the SQL or ODBC language environment |
Explanation: Net.Data has detected that the SQL or ODBC language environment has an invalid SQL handle.
User Response: Check the database or ODBC connection.
| DTWQ017E | Net.Data detected an invalid stored procedure call in function <function_name>. |
Explanation: The stored procedure call is syntactically incorrect.
User Response: Verify that the stored procedure CALL statement is syntactically correct.
| DTWQ018E | Net.Data detected an invalid parameter list in the stored procedure call in function <function_name>. |
Explanation: The parameter list in the stored procedure call is syntactically incorrect.
User Response: Verify that parameter list in the stored procedure CALL statement is syntactically correct.
| DTWQ019E | Net.Data encountered an input table as stored procedure output table in function <function_name>. |
Explanation: Net.Data cannot write into an input parameter table.
User Response: Declare the table parameter in the function parameter list as OUT parameter.
| DTWQ020E | Net.Data encountered a missing stored procedure name in function <function_name>. |
Explanation: Net.Data cannot find the stored procedure name in the stored procedure call.
User Response: Verify that the stored procedure CALL statement has a name.
| DTWQ021E | Net.Data detected too many result sets in the stored procedure call in function <function_name>. |
Explanation: The number of result sets in a stored procedure call is limited to 32.
User Response: Modify the stored procedure call.
| DTWQ022E | Net.Data detected that a table is attached to more than one %REPORT block in function <function_name>. |
Explanation: Only one %REPORT block is allowed per table in a Net.Data function.
User Response: Use only one %REPORT block per table.
| DTWQ023E | Net.Data encountered a result set that was not specified in the stored procedure call in function <function_name> |
Explanation: Net.Data encountered a %REPORT block with a table name that does not match a table listed on the stored procedure call statement.
User Response: Verify the table name on the %REPORT block with the tables listed on the stored procedure call statement.
| DTWQ024E | Net.Data encountered multiple %REPORT blocks in function <function_name> where at least one %REPORT block specified a table name and another did not |
Explanation: For multiple %REPORT blocks, if the first %REPORT block specifies a table name, then the rest must also. If the first %REPORT block does not specify a table name, then none of the blocks should specify a table name.
User Response: Verify that all of the %REPORT blocks in the function have table names, or that none do
| DTWR000E | Net.Data is unable to access the Oracle message for SQL code <sql_code_value>, <additional_information>. |
Explanation: Net.Data was unable to access the specified Oracle message. The Oracle environment may not be set correctly or the error message file cannot be accessed.
User Response: Correct the specified error and try again. Contact your Oracle administrator for assistance.
| DTWR001E | The DTW_ORA language environment does not support multiple result sets |
Explanation: The DTW_ORA language environment does not support multiple result sets.
User Response: Remove any SQL statements from DTW_ORA language environment function blocks that generate multiple result sets.
| DTWU000E | Net.Data is unable to get the environment variable from the server through the API: <variable_name>. |
Explanation: Net.Data is unable to get the environment variable from the server through the API. Check your server's configuration file to make sure that you enabled the Net.Data API plug-in correctly.
User Response: When you run Net.Data in the API plug-in mode, you must specify it correctly in server's configuration file. Please refer to the "Administration and Programming Guide" and try again.
| DTWU001E | Net.Data is unable to allocate the memory space from the Netscape Server through the NSAPI. |
Explanation: When you run Net.Data in the NSAPI plug-in mode, Net.Data allocates the memory through the memory management routine of the NSAPI from the Netscape server. The server is unable to allocate more memory space to Net.Data.
User Response: Stop the server and restart it.
| DTWU003E | Net.Data is unable to get the environment variable from the server through the API. |
Explanation: Net.Data is unable to get the environment variable from the server through the API. Check your server's configuration file to make sure that you enabled the Net.Data API plug-in correctly.
User Response: When you run Net.Data in the API plug-in mode, you must specify it correctly in server's configuration file. Please refer to the "Administration and Programming Guide" and try again.
| DTWV000E | The Net.Data macro servlet detected an invalid macro name. |
Explanation: The Net.Data macro servlet macro name specified is either null, blank, or missing. The Net.Data macro servlet requires that a valid, fully qualified Net.Data macro name be specified.
User Response: Specify a valid macro name using the <MACRO> parameter and try again.
| DTWV001E | The Net.Data macro servlet detected an invalid HTML block name. |
Explanation: The HTML block name specified in the Net.Data macro servlet is either null or blank. The Net.Data macro servlet requires a valid HTML block name to execute in the specified Net.Data macro.
User Response: Specify a valid HTML block name in the specified Net.Data macro using the <BLOCK> parameter and try again.
| DTWV007E | The Net.Data function servlet detected an invalid language environment. |
Explanation: The Net.Data function servlet language environment specified is either null, blank, or missing. The Net.Data function servlet requires that a valid Net.Data language environment be specified.
User Response: Specify a valid language environment using the <LANGENV> parameter and try again.
| DTWV008E | The Net.Data function servlet detected an invalid function name or SQL statement or stored procedure name. |
Explanation: The Net.Data function servlet function name or SQL statement or stored procedure name specified is either null, blank, or missing. The Net.Data function servlet requires that a valid function name or SQL statement or stored procedure name be specified.
User Response: Specify either a valid function name using the <FUNC> parameter or a valid SQL statement/stored procedure name using the <SQL> parameter and try again.
| DTWV011E | The Net.Data servlet detected an invalid HTML path. |
Explanation: The Net.Data servlet HTML path specified is either null, blank, or missing. The Net.Data servlet requires that a valid, fully-qualified Web server HTML path be specified (such as: "e:\ibmwww\html").
User Response: Specify a valid HTML path using the <HTMLPATH> parameter and try again.
| DTWV012E | The output buffer passed to Net.Data by Net.Commerce or the Net.Data macro servlet native method is too small. Pass in a bigger buffer. |
Explanation: Net.Data has encountered an internal failure. This is a Net.Data internal error.
User Response: Report the problem to your system administrator.
| DTWX000E | The Net.Data REXX language environment encountered an error executing the REXX statement |
Explanation: An invalid REXX statement was found in the DTW_REXX inline function or in the external REXX script.
User Response: Verify that all REXX statement in the DTW_REXX inline function or in the external REXX script are valid.
| DTWX001E | The Net.Data REXX language environment encountered an error processing the result file. |
Explanation: Net.Data detected an unexpected token in the result file, which was generated by DTWGENOU module.
User Response: Please report this error to your system administrator.
| DTWX002E | The Net.Data REXX language environment encountered an error when establishing an OpenEdition MVS REXX environment. |
Explanation: Net.Data could not fetch the module BPXWRBLD to create an OE MVS REXX environment.
User Response: Verify that the module BPXWRBLD is available in your environment.
| DTWX003E | The Net.Data REXX language environment encountered an error when creating an OpenEdition MVS REXX environment: return_code=<return_code>. |
Explanation: Net.Data could not create an OpenEdition MVS REXX environment.
User Response: Please report this error to your system administrator.
| DTWX004E | The Net.Data REXX language environment was unable to allocate memory for the function. |
Explanation: Net.Data could not allocate memory for all REXX variables. There are too many variables in the DTW_REXX inline function or in the external REXX script.
User Response: Please report this error to your system administrator.
| DTWY000E | Net.Data is unable to access the Sybase message for SQL code <sql_code_value>, <additional_information>. |
Explanation: Net.Data was unable to access the specified Sybase message. The Sybase environment may not be set correctly or the error message file cannot be accessed.
User Response: Correct the specified error and try again. Contact your Sybase administrator for assistance.
| DTWY001E | The DTW_SYB language environment does not support multiple result sets |
Explanation: The DTW_SYB language environment does not support multiple result sets.
User Response: Remove any SQL statements from DTW_SYB language environment function blocks that generate multiple result sets.
| DTWZ000E | Access to the macro file has been forbidden because it does not appear in the ACL file. |
Explanation: The macro file is not listed in the ACL file and therefore access has been forbidden.
User Response: Add the file to ACL file and try again.
| DTWZ001E | Authentication has failed for user <user_name>. |
Explanation: Authentication has failed for the specified user because the user ID or password are incorrect.
User Response: Specify a valid user ID and password and try again.
| DTWZ002E | ACL file does not grant the necessary rights to access the macro file: ACL file: <ACL_name>, macro file: <macro_name>, user ID: <user_ID>, host IP address: <ip_address>, host name: <host_name>, HTTP-method: <method>, HTML block name: <block_name>. |
Explanation: Authentication has failed for the specified macro file, section, and user.
User Response: Correct the error and try again.
| DTWZ003E | Net.Data is unable to process the ACL file <file_name>. |
Explanation: Net.Data was unable to process the specified file because the file does not appear to be in the correct format.
User Response: Ensure the specified file exists and that it is in the correct format.
| DTWZ004E | Net.Data has detected an invalid MACRO_PATH. |
Explanation: The Net.Data db2www.ini file contains an invalid or missing MACRO_PATH statement.
User Response: Specify a valid MACRO_PATH and try again.