Messages and Codes

Return Codes: Explanation and Recovery Information

The following return code messages are provided by Net.Data when it detects an unusual condition.

Explanation: A call to an internal function failed. This is a Net.Data internal error.

User Response: Report the problem to your software service representative.

Explanation: The server could not process a Net.Data request to allocate memory.

User Response: Ensure the server has enough memory available.

Explanation: The function requested on a function call is not a supported Net.Data built-in function.

User Response: Ensure the specified call to the built-in function doesn't have any typographical errors. Refer to the Net.Data Reference for a list of the supported built-in functions.

Explanation: An input parameter contained a NULL value.

User Response: Ensure the parameters are defined and not NULL before they are passed to the function.

Explanation: An input parameter contained a string value which consisted of the null-terminating character.

User Response: Ensure the specified parameter does not contain a NULL value.

Explanation: The number of parameters passed on a function call either exceeded the maximum number allowed, or was less than the minimum number required by the function.

User Response: Check the function syntax and ensure you pass all the required parameters and no more than the maximum specified.

Explanation: A parameter passed on a function call, required to be a Net.Data macro table variable, was of a different variable type.

User Response: Ensure the variable is defined as a TABLE variable in a DEFINE statement or block.

Explanation: A parameter passed on a function call, required to be a string variable, was of a different variable type.

User Response: Ensure the variable is defined as a string variable in a DEFINE statement or block.

Explanation: A literal string was passed on a function call for a parameter which was required to be an output parameter.

User Response: Do not specify any input values for output parameters. The parameter type might need to be changed to INOUT.

Explanation: A parameter contains a value which is not valid. One of these conditions exists:

• A value was passed which exceeded the maximum supported value.
• A value was passed which was less than the minimum supported value.
• A value was passed which was not one of the supported choices.
• A table row or column value was passed which was less than or equal to zero.

User Response: Ensure that the value is not out of range or invalid.

Explanation: A parameter is outside of table bounds. 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.
• 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.

Explanation: The syntax of the data returned by a System or Perl program is not in the correct Net.Data string format. One of these conditions exists:

• An equal sign was not found.
• A beginning quote was not found.
• An ending quote was not found.
• A space separator between values was not found.

User Response: Check the data returned by the function for syntax errors and modify the script accordingly.

Explanation: Not all of the requested data could be returned. 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.

Explanation: An flat file interface built-in function could not find the specified file.

User Response: Ensure the file is in a path specified by the FFI_PATH statement in the initialization file.

Explanation: A flat file interface built-in function could not open the specified file because it was in use by this or another process, and could not be shared in the specified mode.

User Response: Ensure another process has not locked the file.

Explanation: A flat file interface built-in function could not close the specified file because it was not opened by this macro invocation.

User Response: The file must be closed by the macro that opened it. Changes made could be lost.

Explanation: A flat file interface built-in function 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.

User Response: The table is too large for Net.Data to handle.

Explanation: A flat file interface built-in function was attempting 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, which is 4095.

User Response: Shorten the FFI_PATH statement to only those directories Net.Data needs for the current application.

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. If this problem persists, report the problem to your software service representative.

User Response: Check your configuration and try again. If problems persist, report the problem to your software service representative.

Explanation: A flat file interface built-in function could not access the specified file because it was in use by this or another process and could not be shared in the specified mode.

User Response: End the process using the file and try again. Consider specifying a RETRY value to automatically retry if the file is in use when the function is called.

Explanation: A Web registry built-in function could not create a Web registry because the specified registry already exists.

User Response: Use another name for the Web registry.

Explanation: A Web registry built-in function could not delete the specified registry. One of these conditions exists:

• The registry was in use by another process.
• The registry could not be found.

User Response: If the registry is in use by another process, try after the process has closed.

Explanation: A Web registry built-in function could not add an entry to the specified registry because the specified entry already exists.

User Response: Duplicate entries cannot be made in a Web registry. Modify the entry and resubmit the function, or use the existing entry.

Explanation: A Web registry built-in function could not remove or retrieve an entry from the specified registry because the specified entry does not exist.

User Response: Net.Data cannot find the requested registry entry.

Explanation: A Web registry built-in function could not use the specified registry because it cannot be found.

User Response: Create the registry if it does not already exist.

Explanation: A Web registry built-in function could not create the specified registry because a path in the registry name does not exist.

User Response: Specify a path when you create the registry.

Explanation: A Web registry built-in function could not complete the specified operation because the requestor does not have the proper authority to the specified registry.

User Response: Change the security parameter in your Web registry functions to authorize the operation.

Explanation: A Web registry built-in function could not create the specified registry for unknown reasons.

User Response: Check your configuration and try again.

Explanation: A parameter contains an invalid whole number value. One of these conditions exists:

• An input parameter contained a value which was not a whole number.
• An input parameter contained a value which was greater than the supported maximum of 999,999,999.
• An output cannot be expressed as a whole number.

User Response: Ensure that the value is not out of range or invalid.

Explanation: A parameter contains an invalid number value. One of these conditions exists:

• An input parameter contained a value which was not a valid format for a number.
• An input parameter contained a value which specified an exponent outside the supported range of -999,999,999 to +999,999,999.

User Response: Ensure that the value is not out of range or invalid.

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 the value is within the supported range.

Explanation: The string specified in the EXEC statement of a function block contained only space characters.

User Response: Specify a string that is not all space characters.

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.

Explanation: The path in EXEC block not valid or the EXEC block is missing.

User Response: Ensure that an EXEC block is specified and that the path specified in the EXEC block references a program object.

Explanation: Incorrect attributes for the data type were specified or Net.Data does not support the data type.

User Response: Correct the parameter that is in error by using one of the following methods:

• If precision and scale were specified, ensure that scale is less or equal to precision.
• If precision or scale was specified, ensure that the precision or scale is allowed for the data type and that the specified value is within the allowed range.
• If data type is DTWTABLE, ensure that the parameter value is a Net.Data table.
• Ensure that the specified data type is one that is supported.

Explanation: A data conversion error occurred when data was converted from displayable format to internal format or from internal format to displayable format.

User Response: Ensure that the data specified is compatible with the data type of the parameter.

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.

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.

Explanation: The specified SMTP server does not support the Extended Simple Mail Transfer Protocol (ESMTP). Net.Data cannot relay e-mail messages that contain 8-bit characters (such as non-U.S. ASCII characters) to an SMTP server that supports only 7-bit characters (such as U.S. ASCII).

User Response: Either specify an SMTP server that supports ESMTP (8BITMIME) or do not use 8-bit characters in your e-mail messages.

Explanation: The cookie cannot be found. One of the following conditions exists:

• The cookie has never been set.
• The cookie has expired.
• The cookie does not have an expiration date and is not persistent; the Web browser that received the cookie exited or was killed.
• The cookie was set with a secure option, and the current HTTP request was sent over an insecure channel.
• The Web browser did not accept cookies or it did not execute JavaScript programs at the time when the set cookie request was submitted.
• The cookie has been deleted by the Web browser; the number of cookies exceeds the limitations of the browser. The limitations are described in Netscape's specification at:

  http://search.netscape.com/newsref/std
  /cookie_spec.html.
  

User Response: Determine the reason why the cookie cannot be found and correct the situation.

Explanation: A persistent built-in function was called out of sequence.

User Response: Ensure that the persistent built-in functions are correct and in sequence. For example, you cannot have a call to DTW_ACCEPT() followed by a call to DTW_TERMINATE(). To learn about the proper sequence of persistent built-in functions, see the persistent macro chapter in the Net.Data Administration and Programming Guide for OS/400.

Explanation: Persistence could not be enabled. The attempt to define a static variable failed because text prior to the variable has been written to stdout.

User Response: Ensure that persistence is enabled by defining the static variable before writing text to stdout.

Explanation: Macro persistence is not enabled. A call was made to a built-in function that requires macro persistence to be enabled.

User Response: Enable persistance within the macro or remove the function call. Refer to the Net.Data Administration and Programming Guide for OS/400 for information on enabling persistent macros.