Natural System Error Messages 1500-1549

NAT1500: Open for :1: file :2: failed :3:.

Text
Open for ... file ... failed ....
Explanation
Possible reasons:
- Com-plete:    Work files: Insufficient space for SD files.
                Printers  : Message indicates PSOPEN error.
- z/OS:         Insufficient or incorrect DCB information. Please
                check for operating-system messages in the job log.
- Linux/Windows: Read/write privileges for the directory where the work
                file is located may be incorrect; or the specified path
                for the work file may be incorrect.
- Entire Connection: The RECORD option cannot be used with Entire
                Connection work files.
Action
For Entire Connection work files, omit the RECORD option. In all
other cases, contact your Natural administrator.

NAT1501: Insufficient control information for :1: file :2:.

Text
Insufficient control information for ... file ....
Explanation
Under z/OS the file cannot be opened. Neither the block size (BLKSIZE)
nor the record length (LRECL) are known when the file is opened.
Action
Ensure that a sufficient record length (LRECL) definition is available,
either from the application or from the dataset DCB or from the JCL, or
from the Natural parameter module or dynamic parameter WORK or PRINT.

NAT1502: Permanent physical I/O error for :1: file :2:.

Text
Permanent physical I/O error for ... file ....
Explanation
The work file cannot be processed because of permanent I/O errors.
Possible reason is a physical damage to the file.
Action
Check the console log for corresponding error message.

NAT1503: Work file :1: closed within READ WORK FILE loop.

Text
Work file ... closed within READ WORK FILE loop.
Explanation
Within a READ WORK FILE processing loop, another Natural program
or subprogram has caused the closing of the work file, either by an
explicit CLOSE WORKFILE statement or implicitly due to an
end-of-file condition during a READ WORK FILE processing loop. If
the work file has been closed, an open READ WORK FILE loop for the
work file must be exited with an ESCAPE BOTTOM statement.
Action
Correct error.

NAT1504: READ end-of-file reached but no AT END processing coded.

Text
READ end-of-file reached but no AT END processing coded.
Explanation
The READ WORK FILE ONCE option was specified and the file has
reached the end-of-file condition.
This condition should be checked with an AT END OF FILE clause.
Action
Correct program.

NAT1505: Invalid data for numeric input field.

Text
Invalid data for numeric input field.
Explanation
The READ WORK FILE SELECT option checks all data fields for valid
input data.
A non-numeric value was found in a field defined as numeric.
Action
Check program and correct error.

NAT1506: Packed numeric value and variable definition do not match.

Text
Packed numeric value and variable definition do not match.
Explanation
A READ WORK FILE statement without the RECORD option is attempting to
read a packed variable that is defined with an even number of
digits (e.g. P6, P5.1). However, the numeric data in the work file
does not fit into the variable, but would require an odd number
of digits where the number of digits is one more than the current
definition.
A possible reason is that the data has been written to the work file
using another variable definition or using redefinitions.
Action
Increase the number of digits in the variable definition by one so
that the number of digits is odd, or check the application that wrote
the data to the work file.

NAT1507: The :1: file :2: is full.

Text
The ... file ... is full.
Explanation
The space allocated for an output file is not large enough
to hold all the records written by the Natural program.
Action
Ask your Natural administrator to increase the size of the output
file or to reserve more storage for it.

NAT1508: The :1: file :2: is already open for another user.

Text
The ... file ... is already open for another user.
Explanation
The print or work file is being used by another user
and cannot be shared by users.
Action
Check concurrent programs to ensure that they are not using the
same file.

NAT1509: Dynamic allocation for :1: file :2: failed :3:. RC: :4:.

Text
Dynamic allocation for ... file ... failed .... RC: ....
Explanation
During the dynamic allocation of the designated file, an error occurred.
The error and info codes at the end of the message show the reason for
the failure. Refer to the IBM MVS Authorized Assembler Services manual
and see the description of dynamic allocation for a detailed description
of the error reason.
Action
Contact your Natural administrator.

NAT1510: Record too small for :1: file :2:.

Text
Record too small for ... file ....
Explanation
For z/VSE systems, this message indicates that the WLRERR
exit was entered for a reader using DTFDI or a work file
using DTFMT or DTFSD.
For z/OS systems, this message indicates that for RECFM=F the
record is shorter than the dataset record length and padding
by blanks (print files) or nulls (work files) is not allowed.
Record padding is controlled by the subparameter PAD of the
PRINT or WORK parameter.
Action
Contact your Natural administrator to ensure that the Natural JCL has
been specified correctly. For z/OS systems, start the session with
subparameter PAD=ON to allow record padding or correct your application.

NAT1511: WRITE WORK FILE issued after READ WORK FILE.

Text
WRITE WORK FILE issued after READ WORK FILE.
Explanation
A work file can be created within a Natural program and
subsequently read within it, but not vice versa.
If a work file has been opened as a result of executing a
READ WORK FILE statement, the execution of a WRITE WORK FILE
statement will generate a runtime error.
Action
Check program and correct error.

NAT1512: Record too large for :1: file :2:.

Text
Record too large for ... file ....
Explanation
The length of the record to be written exceeds the output dataset
record length and truncation by blanks (print files) or nulls
(work files) is not allowed.
Record truncation is controlled by the subparameter TRUNC of the
PRINT or WORK profile parameter.
Action
Start the session with subparameter TRUNC=ON to allow record truncation
or correct your application program or correct the output dataset record
length, e.g. by profile subparameter LRECL.

NAT1513: Error occurred when closing :1: file :2:.

Text
Error occurred when closing ... file ....
Explanation
An error has occurred during CLOSE of the specified print or work file.
If a DEFINE or a READ WORK statement failed, the opened file cannot be
closed because the profile subparameter CLOSE=FIN was specified for
the file.
Action
Check the job log protocol for operating system error messages. In
case of CLOSE=FIN, change your application program or use another
value for the CLOSE subparameter for the file.

NAT1514: Not supported file organization for :1: file :2:.

Text
Not supported file organization for ... file ....
Explanation
Currently, Natural only supports sequential files as work files.
Action
Check file organization of the file to be processed and correct it.

NAT1515: Too many work files open in parallel.

Text
Too many work files open in parallel.
Explanation
This Natural version is active under Com-plete.
Com-plete has the restriction that not more than 5 work files
(SD-files) can be processed in parallel by one transaction.
Therefore, Natural checks to ensure that not more than 5 are
opened at the same time.
It is possible that in a set of subsequent transactions
more than 5 work files can be processed, but not more than 5
at a time.
Action
Reduce number of work files in use.

NAT1516: GETMAIN error on open for :1: file :2:.

Text
GETMAIN error on open for ... file ....
Explanation
There is not enough main storage to satisfy a GETMAIN request that is
issued when the specified file is opened.
Action
Increase the size of the storage thread. For non-thread environments
increase the available region or partition size.

NAT1517: FREEMAIN error on close for :1: file :2:.

Text
FREEMAIN error on close for ... file ....
Explanation
A FREEMAIN request failed when closing the specified file.
Action
Contact your Natural administrator.

NAT1518: GET or PUT to not opened :1: file :2:.

Text
GET or PUT to not opened ... file ....
Explanation
An internal error condition may have occurred.
Action
Contact your Natural administrator.

NAT1519: Invalid device type for :1: file :2:.

Text
Invalid device type for ... file ....
Explanation
The device type for a printer is not a printer, or
the device type for a work file is neither a tape nor a disk.
Action
Check JCL and correct error; if necessary, contact your
Natural administrator.

NAT1520: :1: file :2: not available.

Text
... file ... not available.
Explanation
The specified print or work file is not available. Either the file is
not defined in Natural, neither by JCL nor profile parameters or the
file access method is not available.
Action
Check using the SYSFILE utility, whether the file is defined with
the correct file name and access method. Check JCL and the PRINT or
WORK parameter and correct the error.

NAT1521: Invalid variable record.

Text
Invalid variable record.
Explanation
The first 4 bytes of a variable input-work-file record do not
constitute a valid record descriptor-word.
The setting of the Natural parameter BWORKD may be incorrect.
Action
Check JCL or file and correct error,
or contact your Natural administrator.

NAT1522: NATAMUSR: Access method exit NATAM9EX not installed.

Text
NATAMUSR: Access method exit NATAM9EX not installed.
Explanation
The User Access Method exit entry point NATAM9EX is not
resolved in User Access Method module NATAMUSR.
Action
Check if the exit has an entry point NATAM9EX.
Check if the exit is linked to module NATAMUSR.

NAT1523: NATAMUSR: Access method buffer not allocated.

Text
NATAMUSR: Access method buffer not allocated.
Explanation
The User Access Method is not operational because
its buffer is not allocated.
a) The GETMAIN for the buffer might have failed.
b) The buffer has been released, because no
.  Natural print or work file is managed by
.  the User Access Method.

NAT1524: NATAMUSR: :1: file :2: exit :3: error rtc :4: reason :5:.

Text
NATAMUSR: ... file ... exit ... error rtc ... reason ....
Explanation
An error occurred in the User Access Method exit.
Action
See User Access Method exit handler for error and
reason code and appropriate actions.

NAT1525: This work file cannot be accessed with dynamic variables.

Text
This work file cannot be accessed with dynamic variables.
Explanation
Dynamic variables are only allowed in a READ WORK ... ONCE statement
for a TYPE=STREAM work file.
Action
Do not use dynamic variables with this type of work file.

NAT1526: OFFSET keyword not allowed for an UNFORMATTED work file.

Text
OFFSET keyword not allowed for an UNFORMATTED work file.
Explanation
OFFSET specifies a read position relative to the start of a work-file
record. In an UNFORMATTED work file, however, there is no concept of
records, therefore the OFFSET keyword is not allowed.
To position forward relative to the end of the field processed last,
use the FILLER keyword.
Action
Correct error in program.

NAT1527: TYPE=UNFORMATTED work files not supported for this object.

Text
TYPE=UNFORMATTED work files not supported for this object.
Explanation
Work files of TYPE=UNFORMATTED can only be read and written by
Natural programs that are compiled (CATALOGed, STOWed) under Natural
Version 4 and above.

NAT1528: Invalid TYPE specified in DEFINE WORK statement.

Text
Invalid TYPE specified in DEFINE WORK statement.
Explanation
Valid work-file types are:
"FORMATTED" for a regular, record-oriented work file.
"UNFORMATTED" for a work file to be read or written as a byte stream.
Action
Specify a valid work-file type.

NAT1529: Name in DEFINE WORK not allowed for this work file.

Text
Name in DEFINE WORK not allowed for this work file.
Explanation
The work-file access method specified for this work file does not
accept a name operand. The name operand is optional and can be
omitted if the work file TYPE is specified.
Action
Correct error in program.

NAT1530: Invalid ASA control character for print file :1:.

Text
Invalid ASA control character for print file ....
Explanation
An invalid ASA control character has been found in the output record
for the print file indicated in the error message.
This occurs most likely with ASA=OFF in the Natural print-file
definition, in which case it is the user"s responsibility to set a
valid ASA control character.
Action
Check program and correct error.

NAT1531: Smarts access method: :1:.

Text
Smarts access method: ....
Explanation
Problems with the Smarts access method for print and work files.
Possible reasons:
- The driver NCFWFAPS was not found.
- The driver NCFWFAPS was not loaded into resident page.
- The Smarts initialization failed.
Action
Contact your Natural administrator.

NAT1532: NAT error :1: flushing PWC: :2: :3: :4:.

Text
NAT error ... flushing PWC: ... ... ....
Explanation
An error occurred during the flush of the print/workfile cache.
The flush was triggered by the statement on the 1st given line number.
The error occurred at the statement on the 2nd given line number.
You can find this statement in the indicated library/program.
Action
Correct the error.

NAT1533: Invalid attribute value :1: in DEFINE WORK statement.

Text
Invalid attribute value ... in DEFINE WORK statement.
Explanation
One of the attribute values specified for the ATTRIBUTES clause
of the DEFINE WORK statement is invalid.
Action
Specify a valid attribute value.

NAT1534: Event error :1:.

Text
Event error ....
Explanation
Eventing between Natural and the print/work file server failed.
The print/work file server must have been started before the
Natural server is started.
Action
Make sure that the print/work file server has been started.

NAT1536: Shift value (:1:) too high for line size (:2:).

Text
Shift value (...) too high for line size (...).
Explanation
With the given line size, the current shift value of (NT)PRINT
results in empty report lines.
Action
Either decreaze the value of the SHIFT subparameter of (NT)PRINT
or increase the line size.

NAT1548: TPS spool request failure.

Text
TPS spool request failure.
Explanation
A non-zero return code on a TPS spool request has occurred.
Action
See the appropriate TPS documentation for details.

NAT1549: TPS spooling interface not available.

Text
TPS spooling interface not available.
Explanation
For online environments:
    Module TPSSPINO is not available in the TP environment.
For batch environments:
    TPSSPINB is not linked to NSITPS.
Action
Depending on your environment, either make TPSSPINO available,
or link TPSSPINB to NSITPS.