Natural System Error Messages 3500-3549

NAT3500: FCT definition for :1: incomplete; :2: missing.

Text
FCT definition for ... incomplete; ... missing.
Explanation
Natural for VSAM requires information from the CICS file control table
to generate a CICS command; however, this information is missing.
Action
Contact your CICS administrator.

NAT3501: Internal Natural VSAM error, module :1: .

Text
Internal Natural VSAM error, module ... .
Explanation
An internal error condition has occurred.
Action
Contact Software AG support.

NAT3503: Internal Natural :1: error.

Text
Internal Natural ... error.
Explanation
Record buffer too small.
Action
Contact Software AG support.

NAT3504: File :1:, ENABLESTATUS/RESP :2:, RESP2 :3:.

Text
File ..., ENABLESTATUS/RESP ..., RESP2 ....
Explanation
Request could not be satisfied due to ENABLESTATUS problem.
If the parameters ENADIS/ENAUNE in the macro NTVSAM of the Natural
parameter module are set to "OFF", the ENABLESTATUS is indicated in the
error message.
If the parameters ENADIS/ENAUNE are set to "ON", Natural VSAM has issued
an EXEC CICS SET ENABLED command; this command failed, and CICS
has returned response codes as indicated in the error message.
Action
Contact your CICS administrator.

NAT3505: Loop reposition error occurred during ROLL-IN processing.

Text
Loop reposition error occurred during ROLL-IN processing.
Explanation
For the native AIX processing, a current base key cannot be
found for a loop repositioning. Either the alternate indexes were
destroyed or the record for this base key was deleted or
changed by another user.
Action
Contact your Natural administrator.

NAT3506: Statement invalid for Natural VSAM.

Text
Statement invalid for Natural VSAM.
Explanation
This statement is not allowed for this type of VSAM
dataset (for example, READ PHYSICAL for a KSDS type).
Action
Correct error in program.

NAT3507: USR0100N error: :1:.

Text
USR0100N error: ....
Explanation
The program that invokes the user exit USR0100N contains an error.
Action
Correct error in invoking program.

NAT3508: Logical key length is too big.

Text
Logical key length is too big.
Explanation
The sum of the logical key and prefix lengths, defined
in the corresponding DDM, is greater than the maximum  VSAM
key length.
Action
Correct error in DDM/program.

NAT3509: Complex search criteria not allowed for Natural VSAM.

Text
Complex search criteria not allowed for Natural VSAM.
Explanation
Connecting search criteria and coupling of files is
not possible for VSAM files.
See the Natural documentation, FIND statement, for valid
search criteria.
Action
Correct error in program.

NAT3510: Invalid operator in FIND statement for Natural VSAM.

Text
Invalid operator in FIND statement for Natural VSAM.
Explanation
The FIND statement contains an invalid search criterion
for VSAM files.
Action
Correct error in program.

NAT3511: Invalid search buffer.

Text
Invalid search buffer.
Explanation
Either the DDM was changed between cataloging and execution of the
program, or the FIND statement contains a clause not applicable to
VSAM.
Action
Contact your Natural administrator;
or correct error in program.

NAT3512: File :1: is not defined as path.

Text
File ... is not defined as path.
Explanation
The NTVSAM parameter PATH=ON is specified for this session,
but the file is not a path for an alternate index.
Action
Contact your system administrator.

NAT3513: Not enough storage for Natural VSAM in table :1:.

Text
Not enough storage for Natural VSAM in table ....
Explanation
One of the Natural for VSAM internal tables, defined as fixed
buffer type, is too small. The eye-catcher of the internal
table which is too small is indicated in the variable.
Action
Use the Buffer Usage Statistics function of the SYSTP utility to
ascertain which parameter has to be adjusted in the NTVSAM macro.

NAT3514: Record to be updated is not in "hold" status.

Text
Record to be updated is not in "hold" status.
Explanation
An UPDATE statement was issued for a record which was not in
"hold" status.
This may be caused, for example, by the UPDATE statement
referring to a FIND FIRST statement which found nothing.
Action
Correct program or provide other search criteria.

NAT3515: UPD table is full.

Text
UPD table is full.
Explanation
A record has been read for update. Natural for VSAM tried to save
the appropriate fields in its UPD table, but received a response
indicating that the UPD table was not large enough to contain the
fields.
Action
Contact your Natural administrator to increase UPDL size in NTVSAM
macro; or change program to reduce the amount of data held per
transaction.

NAT3516: File: :1: Cmd: :2: Cond: :3: Rc: :4:.

Text
File: ... Cmd: ... Cond: ... Rc: ....
Explanation
Natural for VSAM received an unexpected response from CICS.
File:  Name of involved dataset taken from DDM.
Cmd:   Mnemonic of CICS command issued by Natural for VSAM.
Cond:  Mnemonic of CICS condition.
Rc:    VSAM return code and error code taken from EIB (if provided by
       CICS).
Action
See IBM"s CICS and VSAM documentation for further information.

NAT3517: UPDATE loop for path :1: to ESDS file :2: not supported.

Text
UPDATE loop for path ... to ESDS file ... not supported.
Explanation
CICS only supports path access to an ESDS file with restricted
options. The related RBA for the ESDS base record is not
returned from the READNEXT/READPREV path call by CICS,
and an UPDATE is therefore not possible.
Action
In this case, use native AIX file processing.

NAT3518: Error in format buffer for Natural VSAM.

Text
Error in format buffer for Natural VSAM.
Explanation
The DDM was changed between cataloging and executing the Natural
program.
Action
Contact your Natural administrator.

NAT3519: Error in format buffer for INSERT, base key omitted.

Text
Error in format buffer for INSERT, base key omitted.
Explanation
The base key was not specified for a KSDS file in the STORE statement.
Action
Correct error in program.

NAT3520: Held VSAM record modified by another transaction.

Text
Held VSAM record modified by another transaction.
Explanation
The record held by a previous READ/FIND for UPDATE was modified by
another transaction.
Action
Check your application"s handling of concurrency control problems;
or issue the RETRY statement in an ON ERROR clause to ignore the
error situation.

NAT3521: Direction changed for an active READ in variable sequence.

Text
Direction changed for an active READ in variable sequence.
Explanation
For an active READ loop, the ascending/descending direction
was changed to descending/ascending sequence.
Action
Correct error in program.

NAT3522: DD/DLBL name for file :1: is not defined in the JCL stream.

Text
DD/DLBL name for file ... is not defined in the JCL stream.
Explanation
The NTVSAM parameter PATH=CHECK is specified and the file
is not defined in the system (no FCT entry for CICS, no UFILE
entry for Com-plete, or no JCL card for any other environment).
Action
Contact your system administrator.

NAT3523: Insertion of :1: "LA" record without "LB" field.

Text
Insertion of ... "LA" record without "LB" field.
Explanation
Insertion of LA record into system file with LB field having been
omitted (internal error).
Action
Contact your Natural administrator.
If necessary, contact Software AG technical support.

NAT3524: Maximum VSAM record length exceeded at insertion/update.

Text
Maximum VSAM record length exceeded at insertion/update.
Explanation
Insertion/updating was requested for a record which is longer than the
permitted maximum; or an attempt was made to increase the length of a
"fixed length" record.
Action
Check record-length definition in VSAM cluster and in the DDM.

NAT3525: OPEN utility is active, specify OPSUPP=ON in NVSPARM.

Text
OPEN utility is active, specify OPSUPP=ON in NTVSAM macro.
Explanation
The user exit USR2008P is active, but the NTVSAM parameter
OPSUPP=OFF is specified.
Action
Contact your Natural administrator.

NAT3526: Read on :1: "LB" subfile with other "DE" specified.

Text
Read on ... "LB" subfile with other "DE" specified.
Explanation
This is an internal Natural for VSAM, Natural for ISAM or
Natural for LEASY error.
Action
Contact your Natural administrator.
If necessary, contact Software AG technical support.

NAT3527: MDM VSAM file organization and VSAM type are not compatible.

Text
DDM VSAM file organization and VSAM type are not compatible.
Explanation
Either the DDM VSAM file organization is "extended" and the actual
VSAM file is not of extended format, or vice versa.
Action
Correct the combination of the DDM VSAM file organization and the
VSAM file format.

NAT3528: Specified :1: "DE" is not a secondary one.

Text
Specified ... "DE" is not a secondary one.
Action
Check program and correct error.

NAT3529: Field in HISTOGRAM must be a descriptor.

Text
Field in HISTOGRAM must be a descriptor.
Explanation
See the Natural documentation for valid HISTOGRAM syntax.
Action
Correct error in program.

NAT3530: UPD=OFF not allowed for Natural :1: :2:.

Text
UPD=OFF not allowed for Natural ... ....
Explanation
Inconsistency between DDM and NTVSAM macro.
If the parameter UPD=OFF is set in the NTVSAM macro,
logical files are not supported.
Action
Change DDM or NTVSAM macro.

NAT3531: No entry found with given command ID for Natural :1:.

Text
No entry found with given command ID for Natural ....
Explanation
This is an internal error.
Action
Contact your Natural administrator.

NAT3532: File :1: not known to CICS.

Text
File ... not known to CICS.
Explanation
CICS returned a DSIDERR condition upon Natural for VSAM"s
INQUIRE command.
Action
Contact your CICS administrator.

NAT3533: File :1:, VSAM record deleted from another terminal.

Text
File ..., VSAM record deleted from another terminal.
Explanation
While UPDATE waited for a response, another terminal or
batch user deleted the record in question; or the alternate index
is destroyed.
Action
Check your application logic or the file structure.

NAT3534: Duplicate VSAM record in file :1:.

Text
Duplicate VSAM record in file ....
Explanation
An attempt was made to write a duplicate record to a unique-key
VSAM dataset.
Action
Correct error in program.

NAT3535: A Natural :1: end-of-file condition has occurred.

Text
A Natural ... end-of-file condition has occurred.
Action
Contact your Natural administrator.

NAT3536: :1: error, feedback code :2:, file :3:.

Text
... error, feedback code ..., file ....
Action
See IBM documentation for explanation of feedback code (RPLERRCD).

NAT3537: :1: failed, return/reason code :2:/:3:.

Text
... failed, return/reason code .../....
Explanation
Natural for VSAM needed a temporary storage area outside
VSIZE (for example, as I/O area); the appropriate GETMAIN
or FREEMAIN request failed.
The return code comes from NATGETM ,the reason code from the
system.
Action
Increase available storage.

NAT3538: Response from CICS: INVREQ.

Text
Response from CICS: INVREQ.
Explanation
The statement is not allowed according to the dataset entry
specification in the CICS File Control Table (FCT).
If the Natural session runs with DU=ON, a NV63 ABEND with a
transaction dump is forced in instead of NAT3538.
Action
Use CEDF to examine the cause of this problem, or start your session
with DU=ON and analyze the trace table in the dump.

NAT3539: File :1: not :2:, :3:.

Text
File ... not ..., ....
Explanation
Open/close error. If available to Natural for VSAM, the original
return code is indicated in the error message. For an explanation
of the return code, see the corresponding IBM documentation.
Action
Contact your Natural administrator.

NAT3540: No more space in VSAM file :1:.

Text
No more space in VSAM file ....
Explanation
The VSAM file must be reorganized.
Action
Contact your Natural administrator.

NAT3541: File :1:, control interval/record held by another user.

Text
File ..., control interval/record held by another user.
Action
Check your application"s transaction logic or issue a
RETRY in an ON ERROR clause to ignore the error condition.

NAT3542: File :1:, primary key must not be modified.

Text
File ..., primary key must not be modified.
Explanation
You are not allowed to modify the primary key area.
Action
Correct error in program.

NAT3543: File :1: invalid record length or length defined as fixed.

Text
File ... invalid record length or length defined as fixed.
Explanation
The length of a record exceeds the maximum record size or is shorter
than the minimum record size.
For an AIX file, the record length was not sufficient to contain the new
alternate index key pointer.
Action
Check DDM and VSAM file definitions.
If the file is a member of an UPGRADE set, increase the max. CI size
or enlarge the file.

NAT3544: END of TRANSACTION not successful, RC: :1:.

Text
END of TRANSACTION not successful, RC: ....
Explanation
Under CICS, this error may be caused, for example, by a failure in the
synchronization of remote systems.
In DFSMStvs, a program or environmental error has occurred, or the
Resource Recovery Service (RRS) is not available.
Action
Under CICS, use CEDF to determine the cause of this error.
In DFSMStvs, refer to the IBM documentation on Callable RRS.

NAT3545: BACKOUT TRANSACTION not successful, RC: :1:.

Text
BACKOUT TRANSACTION not successful, RC: ....
Explanation
Under CICS, this error may be caused, for example, by a failure in the
synchronization of remote systems.
In DFSMStvs, a program or environmental error has occurred, or the
Resource Recovery Service (RRS) is not available.
Action
Under CICS, use CEDF to determine the cause of this error.
In DFSMStvs, refer to the IBM documentation on Callable RRS.

NAT3546: File :1: opened for input, :2: not allowed.

Text
File ... opened for input, ... not allowed.
Action
Either set the OPRB parameter to "O" (for output) for this database,
or omit the OPRB parameter.
Check the NTDB setting in the Natural parameter module.

NAT3547: Overflow of FCT table.

Text
Overflow of FCT table.
Explanation
Natural for VSAM"s internal file control table is full.
Action
Increase parameter TAFE in the NTVSAM macro of the Natural parameter
module.

NAT3548: Now it is too late for BACKOUT TRANSACTION.

Text
Now it is too late for BACKOUT TRANSACTION.
Explanation
The program contains a design error: it attempts to backout updates
which have already been committed.
The most likely reason is that a terminal I/O has forced the end of
the logical transaction; that is, internally a SYNCPOINT command has
already been executed by the TP monitor at the time when the BACKOUT
TRANSACTION statement is executed.
Nevertheless, Natural VSAM has executed a BACKOUT TRANSACTION. This
means that the actual scope of the BACKOUT TRANSACTION is different
from the expected one.
Action
Correct error in program.

NAT3549: Working storage for user exit :1: cannot be allocated.

Text
Working storage for user exit ... cannot be allocated.
Explanation
Overflow on Natural internal buffer CFWSIZE.
Action
Contact Software AG support.