Natural System Error Messages 1150-1199

NAT1150: Attribute buffer overflow.

Text
Attribute buffer overflow.
Explanation
An overflow of the attribute buffer is caused by too many
attributes for one logical page.
Action
Reduce the number of fields on one page.

NAT1151: Invalid access to Natural system function.

Text
Invalid access to Natural system function.
Explanation
An invalid access to a Natural system function was attempted.
For example, an attempt was made to assign a value to a
read-only function.
Action
Check program and correct error.

NAT1152: Invalid function in screen paging.

Text
Invalid function in screen paging.
Explanation
An invalid function code was entered during screen-page processing.
Action
Enter a valid function code.

NAT1153: Requested screen pages are not available.

Text
Requested screen pages are not available.
Explanation
Screen pages were requested during screen paging,
but these pages are not available.
Action
Correct error.

NAT1154: Help function not possible during help processing.

Text
Help function not possible during help processing.
Explanation
A help key was pressed or the help character was entered
while the help system was already active.

NAT1155: Reporting mode not permitted.

Text
Reporting mode not permitted.
Explanation
Switching to reporting mode is not permitted if Natural was started
with structured mode (parameter SM=ON).
Switching to reporting mode can be done via the GLOBALS command.
Action
Make sure you are using the correct programming mode.

NAT1156: Statement not possible within TOP OF PAGE or END OF PAGE.

Text
Statement not possible within TOP OF PAGE or END OF PAGE.
Explanation
The specified statement must not be specified within an
AT TOP OF PAGE or AT END OF PAGE statement block.
Action
Correct error in program.

NAT1157: Invalid format of operand.

Text
Invalid format of operand.
Explanation
During runtime, the format of an operand is not contained in the list
of valid formats.
Action
Contact SAG support.

NAT1160: Error in "Recording" activation.

Text
Error in "Recording" activation.
Explanation
This error is caused by one of the following:
- The requested recording has not been found.
- You have specified no recording name.
- For a new recording, you have specified the name of an already
  existing recording.
Action
Make sure you use the right recording name in the right library.

NAT1161: DBCS: Invalid SO/SI pair in line :1: column :2:.

Text
DBCS: Invalid SO/SI pair in line ... column ....
Explanation
Natural checks the correct pairing of SO/SI for
DBCS (double-byte character set) terminals.
Action
Check program logic and generate correct SO/SI pairs.

NAT1162: Invalid character or shift character in DBCS-only field.

Text
Invalid character or shift character in DBCS-only field.
Explanation
A DBCS-only field is an alphanumeric field for which the session
parameter PM=D is set. It must contain only valid DBCS characters;
shift-out/shift-in characters (SO/SI) are not allowed within such
a field.
If either
- a shift-out/shift-in character (SO/SI) or
- a character code that is not a valid DBCS character
is detected, this error is issued.

Shift-out/shift-in characters (SO/SI) are always detected. Because
the detection of non-DBCS characters requires ICU, it will not be
performed if ICU is not available (that is, if the profile parameter
CFICU=OFF has been set).
Action
Correct the content of the DBCS-only field.

NAT1165: The WINDOW statements are no longer consistent.

Text
The WINDOW statements are no longer consistent.
Explanation
Natural tried to execute the internal reference to the DEFINE WINDOW
statement during the execution of an INPUT WINDOW=window-name or
SET WINDOW window-name. The reference is not the correct statement
anymore. Probably the generated program has been destroyed.
Action
Clear the buffer pool and restart Natural.
Recatalog the program.

NAT1166: Invalid window width specified in SIZE clause.

Text
Invalid window width specified in SIZE clause.
Explanation
The value for the number of columns in the SIZE clause of the DEFINE
WINDOW statement is outside the valid range.
The minimum number of columns if the FRAME clause is used is 13.
The minimum number of columns if the FRAME clause is not used is 10.
The maximum number of columns is the physical screen size.
Action
Correct program.

NAT1167: Invalid window length specified in SIZE clause.

Text
Invalid window length specified in SIZE clause.
Explanation
The value for the number of lines in the SIZE clause of the DEFINE
WINDOW statement is outside the valid range.
The minimum number of lines if the FRAME clause is used is 4.
The minimum number of lines if the FRAME clause is not used is 2.
The maximum number of lines is the physical screen size.
Action
Correct program.

NAT1168: Invalid window start line (:1:).

Text
Invalid window start line (...).
Explanation
The current size of the window inhibits the position of the
window at the specified line in the screen.
Action
Reduce the size of the window, or use a smaller line value.

NAT1169: Invalid window start column (:1:).

Text
Invalid window start column (...).
Explanation
The current window size is too large to start the window at the
specified column on the screen.
Action
Reduce the window size, or use a smaller column value.

NAT1170: PC access method not available.

Text
PC access method not available.
Explanation
Natural checks to see if the terminal command "%+" is valid
in the current environment. The PC access method is not linked
to the Natural nucleus.
Action
Do not use "%+", or contact your Natural administrator.

NAT1171: The required terminal converter module is missing.

Text
The required terminal converter module is missing.
Explanation
This error occurs if the terminal command "%T=nnnn" has been entered,
but the specified terminal type is not defined by the macro NTDVCE in
source module NATCONFG, or the required converter module has not been
linked to the Natural nucleus.
Action
Specify a correct terminal type; or link the required converter
module to the Natural nucleus.

NAT1172: PC connection already active.

Text
PC connection already active.
Explanation
The terminal command "%+" has been entered, but PC connection
was already active.
Action
No action required.

NAT1173: PC connection not active.

Text
PC connection not active.
Explanation
The terminal command "%-" has been entered, but the
PC connection was not active or had already been
de-activated.
Action
No action required.

NAT1174: Not in lower case for upload.

Text
Not in lower case for upload.
Explanation
For uploads, Natural has to be in lower case to be able to compute
the right check sum and to upload binary data.
Action
Set lower case on and try again.

NAT1175: Upload aborted due to check sum errors.

Text
Upload aborted due to check sum errors.
Explanation
The sent check sum is different from the one computed by Natural.
Action
Try upload again later.

NAT1176: Terminal type :1: cannot be used in this environment.

Text
Terminal type ... cannot be used in this environment.
Explanation
The terminal type specified by the TTYPE profile parameter or by
the terminal command %T= cannot be used in this environment.
For example, an online terminal type cannot be used in a batch
environment.
The terminal type specified by the terminal command %T= or in a
SET CONTROL "T=" statement does not support MBCS code pages.
Action
Specify a correct terminal type for this environment.

NAT1177: Unsupported format type found.

Text
Unsupported format type found.
Explanation
Supported format types for the old PC access method are alphanumeric
and numeric.
Supported format types for the new PC access method are:
    - alphanumeric
    - numeric
    - packed
    - logical
    - floating point
    - integer
    - binary.
Action
Correct your program and retry.

NAT1178: Uploaded data are not a DDM or Natural 2 source/object.

Text
Uploaded data are not a DDM or Natural 2 source/object.
Explanation
The data used when uploading a DDM or a source binary or an
object are not of the appropriate type.
The used file on the PC does not hold a binary downloaded DDM or
source or object.
Action
Use an appropriate file and retry.

NAT1179: Used work file number not assigned to PC or PCNEW.

Text
Used work file number not assigned to PC or PCNEW.
Explanation
The work file number used in the subprogram for the current up-/download
is either not assigned to PCNEW if up/downloading binary
or not assigned to PC or PCNEW if up-/downloading as source.
Use SYSFILE to check which work files are assigned to PC and PCNEW.
Action
Use correct work file number and retry.

NAT1180: Invalid type entered for "Upload from PC".

Text
Invalid type entered for "Upload from PC".
Explanation
Valid types for "Upload from PC" are: P, N, S, H, C, K, T, M, 4.
Action
Use appropriate type.

NAT1181: Source or object for download does not exist.

Text
Source or object for download does not exist.
Explanation
An attempt was made to download a non-existing source or object.
Action
Check the name and the library of the source or object you want to
download and retry.

NAT1182: Source to download is of invalid type.

Text
Source to download is of invalid type.
Explanation
An attempt was made to download a data area as source.
Sources of data areas can only be downloaded binary.
Action
Download source of data area binary.

NAT1183: Specified work file cannot be used for COMMAND download.

Text
Specified work file cannot be used for COMMAND download.
Explanation
The specified work file cannot be used for a
WRITE/DOWNLOAD PC/WORK 5 COMMAND statement,
for one of the following reasons:
- The work file is not defined for the new PC access method.
- The work file is already being used.
Action
Define the work file correctly, or use a different work file.

NAT1184: Downloaded command rejected by PC.

Text
Downloaded command rejected by PC.
Explanation
The command that was downloaded has been rejected by the PC,
because the command is not valid.
See the Natural Connection documentation for
information on which commands can be downloaded.
Action
Correct program and retry download.

NAT1185: Catalog the object before you download/upload it.

Text
Catalog the object before you download/upload it.
Explanation
The object contains an error or inconsistency which prevents
its being downloaded/uploaded.
Action
Catalog the object to be downloaded/uploaded;
then try again to download/upload it.

NAT1186: Buffer overflow due to too many or too long field names.

Text
Buffer overflow due to too many or too long field names.
Explanation
While downloading/uploading data with field names, a buffer
overflow has occurred. The reason that the field names do not
fit into the corresponding buffer, either because too many
fields are sent or because the field names are too long.
Action
Upload/download the data without field names (see PC profile parameter),
or reduce the number of fields to be uploaded/downloaded.

NAT1187: GETMAIN for PC Connection work area failed.

Text
GETMAIN for PC Connection work area failed.
Explanation
During upload or download processing the transferred data are stored
intermediately in the PC Connection work area. An increase of this
buffer failed.
Action
Contact your database administrator.

NAT1188: Maximum record length (32 KB) for PC file access exceeded.

Text
Maximum record length (32 KB) for PC file access exceeded.
Explanation
The maximum allowed record length for an access to a PC file is 32 KB.
Action
Reduce the number or size of the operands in the appropriate
READ/WRITE WORK FILE statement.

NAT1189: Increase of work area for work file :1: failed.

Text
Increase of work area for work file ... failed.
Explanation
Natural needs to increase the size of the work-file area to process
an access to the appropriate work file. The GETMAIN request for this
buffer increase failed.
Action
Increase the Natural thread size, or decrease the record length of
the work-file access.

NAT1190: Type "unformatted" is not supported for PC work files.

Text
Type "unformatted" is not supported for PC work files.
Explanation
Unformatted file transfer between PC and mainframe is currently not
supported.
Action
Use a different type of file transfer.

NAT1191: Option ADJUST is not supported for PC work files.

Text
Option ADJUST is not supported for PC work files.
Explanation
The option ADJUST is currently not supported with the READ WORK FILE
statement for PC work files.
Action
Use a different type of file transfer.