This document describes how to configure the IMS connection for a Natural Development Server running on z/OS.
The following topics are covered:
After the installation of the Natural Development Server IMS Adapter is complete, the configuration of the Natural Development Server IMS Adapter has to be done in the Natural Development Server configuration file of the corresponding Natural Development Server.
To enable the Natural Development Server IMS Adapter, specify the remote
front-end module in the NDV configuration parameter
FRONTEND_NAME
:
FRONTEND_NAME=NATISRFE
.
The following IMS-relevant configuration parameters exist:
This configuration parameter specifies the IMS transaction to be used
for starting the remote front-end in IMS TM. This transaction must be defined
in IMS TM and must refer to the program NATINRFE
. See also
Customizing the IMS TM Environment in Installing
the NDV IMS Adapter in the Installation for z/OS
documentation.
Default Value | none |
---|---|
Example | RFE_IMS_TA_NAME=NATvrsAD |
This configuration parameter specifies the TCP/IP address of the host the desired IMS TM is running. This parameter can be omitted if the development server and IMS TM are running on the same TCP/IP node.
Default Value | The host address of the development server. |
---|---|
Example | RFE_IMS_TA_HOST=node1
or
|
This configuration parameter specifies the TCP/IP port of the IMS supplied listener.
Note:
This port number is not used in Natural Studio or NaturalONE to map
to a remote development server. This port number (and the
RFE_IMS_TA_HOST
definition) is used internally by the
development server to communicate with the IMS region.
Possible Values | 1 - 65535 |
---|---|
Default Value | none |
Example | RFE_IMS_TA_PORT=3020 |
This configuration parameter specifies the trace level for the remote front-end.
The trace level is similar to the trace implemented for the development server. It is a bit string, where each bit is responsible for a certain trace information:
Bit 31 | Trace main events (transaction initialization/termination, request processing). |
Bit 30 | Detailed functions. |
Bit 29 | Dump internal storage areas. |
Bit 27 | Dump buffer header exchanged between development server and IMS TM. |
Bit 26 | Dump entire buffer exchanged between development server and IMS. |
Bit 25 | Dump the Natural Development Server relevant buffer only (remote gateway buffer). |
Bit 23 | Trace error situations only. |
Bit 07 | Activate trace in the development server region. |
Bit 06 | Activate trace in the IMS MPP region. |
Bit 00 | Reserved for trace-level extension. |
The trace destination is the data set defined for
STDOUT
.
Default Value | 0 |
---|---|
Example | RFE_IMS_TRACE=31+27+7
Dump main events and buffer header in the IMS MPP region (Bits 31 + 27 + 7). |
The following is a sample development server configuration file using the Natural Development Server IMS Adapter:
# The development server parameter SESSION_PARAMETER=PROFILE=(NDV,10,930) FRONTEND_NAME=NATISRFE # Use the IMS Adapter front-end. PORT_NUMBER=4711 # The port number used by Natural Studio. # The IMS Adapter parameter RFE_IMS_TA_NAME=NATvrsAD # The IMS transaction for remote front-end. RFE_IMS_TA_PORT=3020 # The port of the IMS listener. # No RFE_IMS_TA_HOST is defined. This requires # that IMS runs on the same node as the # development server.
Note:
The development server parameters
THREAD_NUMBER
and THREAD_SIZE
are
obsolete when the Natural Development Server IMS Adapter is used.