Natural System Error Messages 8300-8349

NAT8300: Wrong protocol type, or protocol not supported.

Text
Wrong protocol type, or protocol not supported.
Explanation
Request Document needs the type of the used document as first part
of the requested URL at operand 1.
Either no protocol type or a protocol type that is not supported was
specified with operand1.
Action
Change the protocol type to a valid type, e.g. "http://",
and run the program again.

NAT8301: Wrong URL syntax.

Text
Wrong URL syntax.
Explanation
REQUEST DOCUMENT needs the correct syntax of the requested URL at
operand1. The syntax of the specified URL was not correct.
No protocol type or an unsupported protocol type was specified with
operand1.
Action
Correct the URL of operand1 and run the program again.

NAT8302: Request method :1: not supported.

Text
Request method :1: not supported.
Explanation
REQUEST DOCUMENT has been advised by a user-defined header
"REQUEST̲METHOD" to use a different request method.
The REQUEST DOCUMENT statement does not support the specified
request method.
Action
Delete the header value, or change the header "REQUEST̲METHOD" to a
valid value.

NAT8303: Internal error with REQUEST DOCUMENT statement.

Text
Internal error with REQUEST DOCUMENT statement.
Explanation
An internal error has occurred while executing a REQUEST DOCUMENT and
writing back error messages.
Action
Contact Software AG support.

NAT8304: HTTP request failed. Reason :1:.

Text
HTTP request failed. Reason :1:.
Explanation
The REQUEST DOCUMENT statement has received an error from the
transport layer.
Action
Contact Software AG support.

NAT8305: Header :1: is longer than the receiving variable.

Text
Header :1: is longer than the receiving variable.
Explanation
The REQUEST DOCUMENT statement has returned a header value which is
longer than the receiving variable.
Action
Use a GIVING clause to ignore this error, increase the length of
the receiving variable, or use a dynamic variable.

NAT8306: Return value is longer than the receiving variable.

Text
Return value is longer than the receiving variable.
Explanation
The REQUEST DOCUMENT statement has returned a value which is longer
than the receiving variable.
Action
Use a GIVING clause to ignore this error, increase the length of
the receiving variable, or use a dynamic variable.

NAT8307: Cannot convert header :1: to format :2: of receiving variable.

Text
Cannot convert header :1: to format :2: of receiving variable.
Explanation
The REQUEST DOCUMENT statement has returned a header value which is
no valid alphanumeric representation of the format of the
receiving variable.
LASTMSG shows additional information about the header value.
Action
Check the program and correct the error.
Change the format of the receiving variable.

NAT8310: Required parts of Internet Explorer missing.

Text
Required parts of Internet Explorer missing.
Explanation
Request Document relies on technology delivered with Internet
Explorer 4 or above. "wininet.dll" is particularly important.
Request Document failed because required parts of the Internet
Explorer are missing.
Action
Install at least a minimum installation package for Internet
Explorer 4 or above.

NAT8311: Error parsing XML document, line :1: col. :2:; msg. :3:.

Text
Error parsing XML document, line ... col. ...; msg. ....
Explanation
The XML parser terminated with an error.
The XML input document is syntactically invalid.
The line/column at which the error occurred and the message returned by
the parser are indicated in the error message.
Action
Correct the XML input document.

NAT8312: Error during XML parser processing, reason :1:.

Text
Error during XML parser processing, reason ....
Explanation
Possible reasons:
1: Error in parser access; XML parser not available.
2: Parser instance request failed; new instance not available.
3: Parser initialization failed.
4: XML input document is invalid.
5: Unsupported encoding is used.
6: Internal parse save-area stack overflow.
7: Resizing of parse operand failed.
8: Empty document; dynamic variable with *length = 0
Action
Check the XML parser condition or XML document.

NAT8313: GETMAIN for :1: failed; return code :2:.

Text
GETMAIN for ... failed; return code ....
Explanation
Natural for XML is not able to allocate its internal buffers.
Return code = 4 :  Not enough storage.
Return code > 4 :  Internal error.
Action
If return code = 4, increase the size of thread/region/partition/task;
otherwise contact Software AG support.

NAT8314: No Natural ICU handler available.

Text
No Natural ICU handler available.
Explanation
The Natural ICU handler is not available.
Possible reason are:
- The ICU handler module is not linked to Natural or cannot be loaded.
- The session profile parameter for ICU is set to OFF.
- An error occurred during the initialization of the Natural ICU.
The Natural ICU handler is a prerequisite for the Natural XML handler.
Action
Depends on the reason of the error. If an initialization error has
occurred, check the session initialization error messages.

NAT8315: Incompatible versions of Natural and Natural XML.

Text
Incompatible versions of Natural and Natural XML.
Explanation
Version 4.2 of Natural XML can only be used with
Natural Version 4.2.1 or above.
Action
Use a compatible Natural version.

NAT8316: Unsupported operating/TP system.

Text
Unsupported operating/TP system.
Explanation
Currently, Natural XML does not support BS2/UTM.
Action
Use a supported environment.

NAT8317: Natural OS/TP driver is not LE/CRTE enabled.

Text
Natural OS/TP driver is not LE/CRTE enabled.
Explanation
To use the REQUEST DOCUMENT statement, the OS/TP driver used must be
enabled to support the IBM Language Environment or CRTE for BS2000.
Action
Install a driver with the required option.

NAT8318: Module :1: is missing in link-edit.

Text
Module ... is missing in link-edit.
Explanation
A module is missing in the link-edit of the Natural front-end
stub.
Action
Include the module in the link-edit.

NAT8319: Natural statements REQUEST DOCUMENT and PARSE disabled.

Text
Natural statements REQUEST DOCUMENT and PARSE disabled.
Explanation
The profile parameter XML was set to "OFF".
Action
Set the XML profile parameter or at least one of the
subparameters RDOC or PARSE to "ON".

NAT8320: Natural XML initialization failed.

Text
Natural XML initialization failed.
Explanation
The reason for this failure is explained by the more detailed
error message issued together with this error message.
Action
See explanation of detailed message.

NAT8321: Natural statement PARSE is disabled.

Text
Natural statement PARSE is disabled.
Explanation
The subparameter PARSE of the Natural profile parameter XML is set
to "OFF".
Action
Change the PARSE subparameter value to "ON".

NAT8322: Natural statement REQUEST DOCUMENT is disabled.

Text
Natural statement REQUEST DOCUMENT is disabled.
Explanation
The subparameter RDOC of the Natural profile parameter XML is set
to "OFF".
Action
Change the RDOC subparameter value to "ON".

NAT8323: Nested parse XML loop not allowed.

Text
Nested parse XML loops not allowed.
Explanation
Natural detected a recursive call to the XML parser.
Action
Correct program.

NAT8324: No IPv6 stack available on local host.

Text
No IPv6 stack available on local host.
Explanation
If the profile parameter RDIPV6 is set to "ON", a check for the
availability of IPv6 on the local host is performed at session start.
If this check fails, error NAT8324 is issued as a warning.
Action
Either set the RDIPV6 parameter to "OFF", or ask your system or network
administrators to set up an IPv6 stack on your local host.

NAT8331: Error parsing JSON document, line :1: col. :2:; reason :3:.

Text
Error parsing JSON document, line ... col. ...; reason ....
Explanation
The JSON input document is syntactically invalid.
The line/column at which the error occurred, and the message returned by
the parser are indicated in the error message.
If a GIVING Operand is specified, NAT8331 will be suppressed and
the response code is supplied in SUBCODE operand.
Possible reason codes:
Please refer to section "JSON-Related Reason Codes for Error NAT8331"
under "Messages and Codes" in Natural documentation.
These reason codes are shown in SUBCODE operand when supplied.
Action
These reason codes are shown in SUBCODE operand when supplied.
Correct the JSON input document.

NAT8332: Error during JSON parser processing, reason :1:

Text
Error during JSON parser processing, reason :1:
Explanation
Possible reasons:
1: Error in parser access; JSON parser not available.
2: Parser termination failed.
3: Parser initialization failed.
4: Internal parse save-area stack overflow.
5: Resizing of parse operand failed.
These reason codes are populated in SUBCODE operand when supplied.
Action
For reason  1   : Use NATXML from NAT Version 9.2.3 or above.
For reason  2-5 : Contact Software AG Support.

NAT8333: GETMAIN for :1: failed; return code :2:.

Text
GETMAIN for ... failed; return code ....
Explanation
Natural for JSON is not able to allocate its internal buffers.
Return code = 4 :  Not enough storage.
Return code > 4 :  Internal error.
Action
If return code = 4, increase the size of thread/region/partition/task;
otherwise contact Software AG support.

NAT8334: Incompatible versions of Natural and Natural JSON.

Text
Incompatible versions of Natural and Natural JSON.
Explanation
Version 9.2 of Natural JSON can only be used with
Natural Version 9.2.3 or above.
Action
Use a compatible Natural version.

NAT8335: Nested parse JSON loop not allowed.

Text
Nested parse JSON loop not allowed.
Explanation
Natural detected a recursive call to the JSON parser.
Action
Correct program.

NAT8336: Nested PARSE JSON / XML loop not allowed.

Text
Nested PARSE JSON / XML loop not allowed.
Explanation
Natural detected a recursive call to the JSON / XML parser.
It applies only to a z/OS environment.
Action
Correct program.