Natural System Error Messages 3800-3849

#### Search Results

Search

# Natural System Error Messages 3800-3849

#### NAT3800: Invalid segment search expression in FIND statement.

    Text
    Invalid segment search expression in FIND statement.
    Explanation
    Program error: In a segment search expression, two
    qualification statements refer to different segment types.
    Module name: NDPSSBAN
    Problem determination: Items 1 (trace parameter = (CMD,REQ,SER)), 2.
    Action
    Check program and correct error.

#### NAT3801: User-defined field not found in Natural DL/I UDF table.

    Text
    User-defined field not found in Natural DL/I UDF table.
    Explanation
    The DDM does not match the Natural DL/I description of UDFs
    (user-defined fields). The program references a field that is
    not contained in the UDF table.
    Module name: NDPSFBCS
    Problem determination: Items 2, 3, 8.
    Action
    Compare the DDM with the UDF description and make the two consistent
    with each other.

#### NAT3802: No user-defined field found in Natural DL/I UDF table.

    Text
    No user-defined field found in Natural DL/I UDF table.
    Explanation
    The DDM does not match the Natural DL/I description of UDFs
    (user-defined fields). The program references a field that is
    not contained in the UDF table.
    Module name: NDPSFBCS
    Problem determination: Items 2, 3, 8.
    Action
    Compare the DDM with the UDF description.

#### NAT3803: Invalid search criterion in FIND statement.

    Text
    Invalid search criterion in FIND statement.
    Explanation
    Program error: Two segment search expressions are connected by an
    "OR" operator in a FIND statement, but only "AND" is valid.
    Module name: NDPSSBAN
    Problem determination: Items 1 (trace parameter = (CMD,REQ,SER)), 2.
    Action
    Check program and correct error.

#### NAT3804: Internal error.

    Text
    Internal error.
    Explanation
    The format buffer was omitted in an Adabas "N1" command.
    Module name: NDPSFBBS
    Problem determination: Items 1 (trace parameter = (CMD,REQ,SER)), 2.
    Action
    Contact Software AG support.

#### NAT3805: Number of DDM fields too large.

    Text
    Number of DDM fields too large.
    Explanation
    The number of DL/I fields and UDF fields in the segment is too large.
    The GENERATE DDM function cannot contain all the DDM fields in its
    own internal area.
    Module name: NDPRLF00
    Problem determination: Items 6, 8.
    Action
    Contact Software AG support.

#### NAT3806: Not enough storage for a Natural DL/I internal area.

    Text
    Not enough storage for a Natural DL/I internal area.
    Explanation
    There is not enough storage available for the Natural DL/I work area.
    Module name: NDPSRLIN
    Problem determination: Item 1 (trace parameter = (CMD,REQ,SER)).
    Action
    Increase partition region size.

#### NAT3807: Segment name not found in NDB.

    Text
    Segment name not found in NDB.
    Explanation
    The NDB containing the segment name was modified
    after the program had been cataloged.
    Module name: NDLSDGET
    Problem determination: Items 3, 6.
    Action
    Check program and correct error.

#### NAT3808: DBID/file number not assigned to accessed segment.

    Text
    DBID/file number not assigned to accessed segment.
    Explanation
    1. The DBID/file number is not yet assigned to the accessed
       segment.
    2. The segment belongs to a LOGICAL DBD and the source segments in
       the PHYSICAL DBD do not have a DBID/file number.
    3. The system file does not contain the UDF description.
    4. The DBID has been defined as a DL/I DBID (see NTDB macro) but -
       physically - the database is not a DL/I database.
    5. The DBID/file number assigned to the DDM is different to the
       DBID/file number assigned to the segment.
    Module name: NDLSDGET
    Problem determination: Items 3, 8.
    Action
    1. Assign DBID/file number to the segment.
    2. Assign DBID/file number to the source segments.
    3. Check (with NDLBLOCK) if segment description exists in system file.

#### NAT3809: There is not enough shared storage available.

    Text
    There is not enough shared storage available.
    Explanation
    1. The maximum size of the shared storage pool, as defined in the
       Natural DL/I initialization parameters, is too small.
    2. There is not enough shared storage available for Natural DL/I
       internal blocks.
    Module name: NDPSDGET
    Problem determination: Item 1 (trace parameter = (CMD,REQ,SER)).
    Action
    1. Increase the maximum pool size.
    2. Increase the size of the partition/region/roll buffer.

#### NAT3810: DL/I status code "GE" (segment not found).

    Text
    DL/I status code "GE" (segment not found).
    Explanation
    DL/I returns status code "GE", i.e. segment not found.
    Module name: NDPSIORC
    Problem determination: Item 1 (trace parameter = (CMD,REQ,SER)).
    Action
    Refer to the respective IBM documentation for a detailed explanation
    of the status code.

#### NAT3811: DL/I status code :1:.

    Text
    DL/I status code ....
    Explanation
    DL/I returns status code ....
    Module name: NDLSIORC
    Problem determination: Item 1 (trace parameter = (CMD,REQ,SER)).
    Action
    Refer to the respective IBM documentation for a detailed explanation
    of the status code.

#### NAT3812: DL/I is not active.

    Text
    DL/I is not active.
    Explanation
    CICS returns a "DL/I not active" condition (DLINA).
    Module name: NDPSIOCX
    Action
    Contact your CICS system programmer.

#### NAT3813: A DL/I request was issued, but no PSB has been scheduled.

    Text
    A DL/I request was issued, but no PSB has been scheduled.
    Explanation
    CICS has returned a FUNCNS condition.
    Module name: NDLSIOCX
    Problem determination: Item 1 (trace parameter = (CMD,REQ,SER)).
    Action
    Retry PSB schedule.

#### NAT3814: Invalid request to CICS-DL/I interface.

    Text
    Invalid request to CICS-DL/I interface.
    Explanation
    CICS returns an INVREQ condition.
    PSB may not be defined correctly to CICS.
    Module name: NDPSIOCX
    Action
    Contact your CICS system programmer.

#### NAT3815: The PSB language is not Assembler.

    Text
    The PSB language is not Assembler.
    Explanation
    CICS returns a language-conflict condition (LANGCON).
    Module name: NDPSIOCX
    Problem determination: Item 5.
    Action
    Make sure that the PSB language is Assembler and that it is defined
    correctly to CICS.

#### NAT3816: The database is not open.

    Text
    The database is not open.
    Explanation
    CICS returns a "database not open" condition (NOTOPEN).
    Module name: NDPSIOCX
    Action
    Check if the database is open. Contact your CICS system programmer.

#### NAT3817: PSB initialization failed.

    Text
    PSB initialization failed.
    Explanation
    CICS returns a PSBFAIL condition (PSB initialization failed).
    Among other reasons, this error occurs if the setting of the ENQL,
    DMBPL, PSBPL parameters in the CICS System Initialization Table
    (SIT) is too small.
    Module name: NDPSIOCX
    Action
    Contact your CICS system programmer.

#### NAT3818: The use of this PSB is not allowed.

    Text
    The use of this PSB is not allowed.
    Explanation
    A request was issued to an unauthorized PSB.
    CICS returns a "PSB not authorized" condition (PSBNA).
    Module name:  NDPSIOCX
    Action
    Check the CICS ACT table.

#### NAT3819: NSB found on FDIC, but PSB not found in CICS.

    Text
    NSB found on FDIC, but PSB not found in CICS.
    Explanation
    The NSB is present on FDIC, but CICS returned a "PSB not found"
    condition (PSBNF) when trying to schedule the corresponding PSB.
    Module name: NDLSIOCX
    Action
    Check the CICS PSB table.

#### NAT3820: PSB schedule request issued with a PSB already scheduled.

    Text
    PSB schedule request issued with a PSB already scheduled.
    Explanation
    A PSB schedule request was issued, but this or another PSB has
    already been scheduled. Only one PSB at a time can be active.
    Module name: NDPSIOCX
    Problem determination: Item 1 (trace parameter = (CMD,REQ,SER)).
    Action
    Issue a DL/I TERM call (NATPSB OFF).

#### NAT3821: The task is not authorized to access a DL/I database.

    Text
    The task is not authorized to access a DL/I database.
    Explanation
    CICS return a TASKNA condition.
    Module name: NDPSIOCX
    Action
    Contact your CICS system programmer.

#### NAT3822: No PSB scheduled.

    Text
    No PSB scheduled.
    Explanation
    A termination request was issued with no PSB being scheduled.
    Module name: NDPSIOCX
    Problem determination: Item 1 (trace parameter = (CMD,REQ,SER)).
    Action
    Contact Software AG support.

#### NAT3823: GETMAIN for I/O area failed.

    Text
    GETMAIN for I/O area failed.
    Explanation
    There is not enough storage available for the I/O area.
    Module names: NDPSIOCX and NDPSIOBA
    Problem determination: Item 1 (trace parameter = (CMD,REQ,SER)).
    Action
    Increase size of partition/region.

#### NAT3824: No NSB found for checkpoint processing.

    Text
    No NSB found for checkpoint processing.
    Explanation
    In a "Db2 DL/I batch support" environment, Natural for Db2
    issues its checkpoints via Natural for DL/I. However, no
    NSB was found because the NATPSB ON command was not
    issued by the user.
    Module name: NDLSIOBA
    Action
    Issue NATPSB ON with a valid PSB name.

#### NAT3825: DBD names in NCB and PCB do not match.

    Text
    DBD names in NCB and PCB do not match.
    Explanation
    A free NCB has been selected (from the NSB). However, the
    DBD name in this NCB does not match the DBD name in the
    corresponding PCB.
    Module name: NDLSPALL
    Action
    Execute NATPSB procedure to correct NSB/PSB mismatch.