This list of steps can be used to diagnose problems in
starting components by identifying the prerequisites.
About this task
The steps immediately preceding a step in which you are
told to start a component are required to give definitions and configuration
information that must be completed correctly before that component
can be started. The reference keys in the steps refer to the components
as shown in
Figure 1. All components
except the client sockets program belong to the server host.
- Configure TCP/IP to reserve the Listener port number.
A TCP/IP port should be reserved for the Listener to connect
to when it starts. The following is a sample profile statement to
reserve the Listener port.
PORT 4096 TCP EZAIMSLN
See z/OS Communications Server: IP IMS Sockets Guide for details about the PORT statement.
- Configure the TCP/IP network from the server host to the
client host.
For the client program to issue IMS™ transaction requests across a
socket connection, there must be a TCP/IP network defined between
the client and server hosts. Any physical network supported by IBM® MVS™ TCP/IP can be used to establish this socket connection.
See the appropriate information in z/OS Communications Server: IP Configuration Reference for details about how to configure the required
network to the server host TCP/IP.
- 2 Start the TCP/IP address
space on the server host
- Establish and verify the network connection from the client
host to the server host.
Depending on the network connection,
start or activate the required device drivers and network nodes required
to establish a TCP/IP network connection.
To verify the TCP/IP
network connection, use the PING command on the client host, using
the server host destination IP address or network name.
- Define the Listener to the IMS transaction manager.
The IMS transaction manager must be defined to expect
message queue input from the Listener. For information about how to
define the Listener to IMS, see
the Listener IMS definitions
in z/OS Communications Server: IP IMS Sockets Guide.
- 5 If the IMS transaction that is requested by the client
program is not already written, write it.
See z/OS Communications Server: IP IMS Sockets Guide for specific details about writing IMS transactions that can be requested
by a TCP/IP client program.
- Define the IMS transaction
that is requested by the client program to the IMS transaction manager.
The IMS transaction must be defined to IMS before the Listener can request
it to be scheduled on behalf of the client program. See z/OS Communications Server: IP IMS Sockets Guide for important restrictions when defining IMS transactions.
- 4 Start the IMS transaction manager and the IMS database manager.
- Complete the Listener configuration data set.
The Listener configuration data set is read when the Listener
is started. The procedure used to start the Listener (usually EZAIMSLN)
uses the ddname LSTNCFG to specify the Listener configuration data
set. Following is an example statement that specifies TCPIP.LISTENER.DATA
as the configuration data set.
LSTNCFG DD DSN=TCPIP.LISTENER.DATA,DISP=SHR
This data set must contain a minimum set of required statements
to specify the environment the Listener is started in and the list
of IMS transactions available
to client programs.
See z/OS Communications Server: IP IMS Sockets Guide for details about the format and contents
of this data set.
- 3 Start the Listener address
space.
The Listener is started as an MVS address space as described in z/OS Communications Server: IP IMS Sockets Guide. The JCL procedure required for starting
the address space is also listed in z/OS Communications Server: IP IMS Sockets Guide.
- Write the client program, if not already written.
See z/OS Communications Server: IP IMS Sockets Guide for programming details about client programs
that can request IMS transactions
over a TCP/IP network.
- 1 Start the client program.