This document describes the purpose and the functions of the Natural Development Server IMS Adapter.
The following topics are covered:
The Natural Development Server IMS Adapter is designed for a Natural Single Point of Development context where it enables the use of a Natural Development Server (product code NDV), running under z/OS in batch mode, within an IMS TM environment.
See also:
Natural Single Point of Development
Natural Development Server for z/OS
The Natural Development Server IMS Adapter enables you to execute a Natural Single Point of Development session within an IMS TM environment, providing access to resources controlled by IMS TM as DB2 or DL/I databases.
In the menu, Natural Studio offers you a command named . This command enables you to open a Natural session on a remote development server.
If you configure the remote development server for use in conjunction with the Natural Development Server IMS Adapter, this Natural session is not hosted by the remote development server, but it is dispatched remotely within an MPP region using a specified transaction code.
The IMS TM support is not implemented within the front-end stub
NATRDEVS. For dispatching the Natural sessions in IMS TM, the
development server continues to run in batch mode. But it uses the remote
front-end NATISRFE that is delivered with the Natural Development
Server to dispatch the Natural sessions in IMS TM. That is, depending on the
installed front-end, a development server dispatches the sessions locally
(NATMVS for batch mode) or remotely (NATISRFE for IMS
TM).
NATISRFE in turn accepts the Natural request from
NATRDEVS and transfers it to a configured IMS TM environment,
using the IMS installation provided BMP Listener. The IMS Listener launches in
a dedicated MPP region a non conversational Natural transaction that processes
the Natural request and returns the result. Thus it is not necessary to execute
the entire development server under IMS TM. Only small working units (Natural
requests such as "save source" or "get
library list") are transferred to IMS TM for execution.
The Natural Development Server IMS Adapter comprises the following components:
NATISRFE |
The remote front-end called by the Natural Development Server to dispatch a Natural request. It is loaded into the development server address space. |
NATINRFE |
The counterpart of NATISRFE. NATINRFE
runs in an MPP region. It is launched by the IBM-provided IMS Listener (refer
also to z/OS Communications Server IP IMS Socket
Guide).
|
NATSRGND/NATLRGND |
Transmits the NDV-relevant data between Natural Development
Server and the Natural session running in IMS TM. NATSRGND must be
loaded into the Natural Development Server address space and
NATLRGND into the MPP region.
|
The following description explains the interaction between Natural Studio as a remote development client, the Natural Development Server and the IMS TM environment involved:
Natural Studio sends the remote development request to the Natural
Development Server using the port number specified with the Natural Development
Server configuration variable PORT_NUMBER.
The Natural Development Server dispatches the Natural session using
the Natural front-end you have specified with the Natural Development Server
configuration variable FRONTEND_NAME. Specify
NATISRFE in order to use the Natural Development Server IMS
Adapter.
NATISRFE transmits the request to the host/port specified
with the Natural Development Server configuration variable
RFE_IMS_TA_HOST /
RFE_IMS_TA_PORT. You must configure the IBM
provided BMP Listener to listen at this port.
The BMP Listener launches the IMS TM transaction you have specified
with the Natural Development Server configuration parameter
RFE_IMS_TA_NAME. This transaction must be specified in
the configuration of the IMS Listener.
The server transaction first retrieves the transaction initialization
message. TIM contains the necessary information to do the
TAKESOCKET and passes it to NATINRFE.
NATINRFE does the TAKESOCKET and establishes the
TCP/IP conversation with NATISRFE.
NATINRFE finally dispatches the Natural IMS front-end,
which establishes a Natural server session.
