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. |
Text |
Internal Natural VSAM error, module ... . |
Explanation |
An internal error condition has occurred. |
Action |
Contact Software AG support. |
Text |
Internal Natural ... error. |
Explanation |
Record buffer too small. |
Action |
Contact Software AG support. |
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. |
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. |
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. |
Text |
USR0100N error: .... |
Explanation |
The program that invokes the user exit USR0100N contains an error. |
Action |
Correct error in invoking program. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Text |
Internal Natural ... error. |
Explanation |
Internal Natural for VSAM, Natural for ISAM or Natural for LEASY error. |
Action |
Contact Software AG support. |
Text |
Specified ... "DE" is not a secondary one. |
Action |
Check program and correct error. |
Text |
Field in HISTOGRAM must be a descriptor. |
Explanation |
See the Natural documentation for valid HISTOGRAM syntax. |
Action |
Correct error in program. |
Text |
UPD=OFF not allowed for Natural ... .... |
Explanation |
Inconsistency between DDM and NTVSAM macro. - Natural VSAM: If the parameter UPD=OFF is set in the NTVSAM macro, logical files are not supported. - Natural ISAM: If the parameter UPD=OFF is set in the NTVSAM macro, duplicate keys in ISAM files are not supported. |
Action |
Change DDM or NTVSAM macro. |
Text |
No entry found with given command ID for Natural .... |
Explanation |
This is an internal Natural for VSAM, Natural for ISAM or Natural for LEASY error. |
Action |
Contact your Natural administrator. |
Text |
File ... not known to CICS. |
Explanation |
CICS returned a DSIDERR condition upon Natural for VSAM"s INQUIRE command. |
Action |
Contact your CICS administrator. |
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. |
Text |
Duplicate VSAM record in file .... |
Explanation |
An attempt was made to write a duplicate record to a unique-key VSAM, ISAM or LEASY dataset. |
Action |
Correct error in program. |
Text |
A Natural ... end-of-file condition has occurred. |
Action |
Contact your Natural administrator. |
Text |
... error, feedback code ..., file .... |
Action |
See IBM documentation for explanation of feedback code (RPLERRCD). |
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. |
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. |
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. |
Text |
No more space in VSAM file .... |
Explanation |
The VSAM file must be reorganized. |
Action |
Contact your Natural administrator. |
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. |
Text |
File ..., primary key must not be modified. |
Explanation |
You are not allowed to modify the primary key area. |
Action |
Correct error in program. |
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. |
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. |
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. |
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. |
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. |
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. |
Text |
Working storage for user exit ... cannot be allocated. |
Explanation |
Overflow on Natural internal buffer CFWSIZE. |
Action |
Contact Software AG support. |