Net.Data Messages

Return Code Messages: Explanation and Recovery Information

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

-1002 function <function>. Unable to allocate memory.

Explanation: The server could not process a request for storage from Net.Data.

User Response: Ensure the server has enough memory.

-1001 function <function>. Internal code <code>.

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.

1000 function <function>. Function not found.

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

User Response: Make sure the specified function is in the macro file where it was called. The function name must be the name you used to call the function. Check the syntax of the FUNCTION block.

1001 Function <function_name>. Parameter <parm_name> contains a null value.

Explanation: An input parameter contained a NULL value.

User Response: Ensure the parameters is defined and not null before it is passed to the function.

1002 function <function_name>. Parameter <parm_name> contains a null string.

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

User Response: Ensure the specified parameter contains a non-null value.

1003 function <function>. The number of parameters passed is not correct.

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 being called.

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

1004 function <function>. Parameter <parm_name> is not a table.

Explanation: A parameter was passed on a function call which was required to be a Net.Data macro table variable, but was instead a string variable.

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

1005 function <function>. Parameter <parm_name> is not a string.

Explanation: A parameter was passed on a function call which was required to be a Web macro string variable, but was instead a table variable.

User Response: Make sure you do not have the variable defined as a TABLE variable in a DEFINE statement.

1006 function <function>. Parameter <parm_name> is not an output parameter.

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.

1007 function <function>. Parameter <parm_name> contains a value which is not valid.

Explanation: 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.

1008 function <function>. Value <parm_value> is outside of table bounds.

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.
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.

1009 function <function>. Variable string <string> is not in the correct format.

Explanation: The syntax of the data returned by a System or Perl program is not correct. 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.

1010 function <function>. Not all requested data could be returned.

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.

2000 function <function>. The requested file <filename> was not found.

Explanation: A flat file interface built-in function could not find the specified file in the directories it was allowed to search.

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

2001 function <function>. The requested file <filename> could not be opened in the specified mode.

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.

2002 function <function>. The requested file <filename> was not opened.

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.

2003 function <function>. Attempted to read a row of data that exceeded the maximum supported number of bytes.

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.

2004 function <function>. A path specified in FFI_PATH exceeded the maximum supported number of bytes.

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 bytes.

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

2005 function <function>.<System error>

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.

2006 function <function>. The requested file <filename> could not be accessed in the specified mode.

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.

3001 function <function>. Registry <registry_name> already exists.

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

User Response: Use another name for the Web registry.

3002 function <function>. Registry <registry_name> is in use by another process or does not exist.

Explanation: A Web registry built-in function could not delete the specified registry because one of these conditions:

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.

3003 function <function>. Registry entry <registry_entry> already exists.

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

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

3004 function <function>. Registry entry <registry_entry> cannot be found.

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

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

3005 function <function>. Registry <registry_name> cannot be found.

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

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

3006 function <function>. Path in registry <registry_name> does not exist.

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

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

3007 function <function>. You are not authorized to perform the requested registry operation.

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

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

3008 function <function>. Registry <registry_name> failed to create.

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

User Response: Check your configuration and try again.

4000 function <function>. Parameter <parm_name> is not a whole number or is too large.

Explanation: 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.

4001 function <function>. Parameter <parm_name> is not a valid number.

Explanation: 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.

4002 function <function>. Arithmetic overflow or underflow.

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.

5000 function <function>. EXEC statement is empty.

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.

6000 function <function>. EXEC was not specified in the function section.

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.

[ Top of Page | Previous Page | Next Page | Table of Contents ]