NDV CICS Adapter Frequently Asked Questions

This document contains frequently asked questions concerning the Natural Development Server CICS Adapter under z/OS.

The following topics are covered:

Under which CICS user ID does the NDV transaction run within the CICS region?

The NDV transaction (the NDV Natural session) runs under the CICS region userid.

This is the same user ID as your CICS standard listener (CSKL) uses.

I receive a NAT9940 (NAT9939) starting my NDV server

The NAT9940 message in fact should be a NAT9939 message. This will be corrected with Patch Level 01 (NDV212PL01). The NAT9939 message indicates an error in the communication between the NDV server environment and the CICS environment. The general layout of the message is a text describing the error which may be followed by a condition code (CC), if applicable.

The most important NAT9939 errors are listed below. Many errors not listed here are internal errors.

  • ConfigError: ...missing or invalid
    A mandatory configuration variable for the Natural Development Server CICS Adapter is not defined in the NDV configuration file.

  • Cannot bind Socket
    The port specified with RFE_CICS_TA_PORT is not in a listen state on the node specified with RFE_CICS_TA_HOST. Probably the CICS TCP/IP standard listener is configured to use a different port or the listener is not running.

  • Timeout at connection establishment
    The CICS transaction launched by the NDV server did not respond within the time specified in RFE_CICS_TA_INIT_TOUT. Examine CICS message log for potential messages regarding this transaction.

  • Partner closed connection
    Unexpected abort of the connection by either of the partners (NDV server or CICS transaction). Examine CICS message log and NDV server trace for preceding error messages regarding this request.

  • Invalid reply on connection establishment.
    The CICS transaction launched by the NDV server did not initialize correctly. Examine CICS message log for potential messages regarding this transaction. Possible reason: The transaction defined with RFE_CICS_TA_NAME is not defined correctly within CICS.

  • Cannot load NDV Remote Gateway DLL
    The remote gateway DLL NATSRGND/NATLRGND cannot be loaded within the NDV server/CICS region. Possible reason: Module cannot be found on load library concatenation or CICS PPT entry missing.

  • Cannot load NCI front-end
    The Natural CICS front-end specified with RFE_CICS_FE_NAME cannot be loaded. Examine CICS message log error messages regarding this program. Possible reason: Module cannot be found on load library concatenation or CICS PPT entry missing.

On this page