Quick Start
InfoSpeed communication support for TSM lets session traffic flow through a
logical port address using a minimal system resources. InfoSpeed
provides an alternative path that is logically and physically separate from
the host TCP/IP configuration.
For installations configured with a VTAM infrastructure, InfoSpeed
communication supports TSM server-prompted scheduling, which is not available
with APPC. InfoSpeed lets any TSM client platform connect with a TSM
MVS server through a network attached InfoSpeed exPress Data Mover (PDM)
node. Moreover, the server can contact these client platforms by using
IBM TCP/IP to notify client schedulers when scheduled operations should
start. This means that you can configure a TSM client platform with
network connectivity to a PDM node into existing TSM Central Scheduling
schedules and contact them in prompted-scheduling mode.
This new communication path lets non-MVS TSM clients and servers conduct
sessions with an TSM for MVS server over InfoSpeed using their existing TCP/IP
communication method. Instead of connecting directly to TSM over
TCP/IP, the request is routed to a UNIX or Windows NT InfoSpeed PDM Node
Socket Server (NSS). The PDM NSS accepts the connection request and
proxies the TSM session by logically connecting to TSM for MVS server over the
InfoSpeed PDM connection.
To adjust the target address of the TCP/IP request, change the a Domain
Name Service (DNS) or the TCPSERVERADDRESS client option. The
TCPSERVERPORT client option, should match the port number specified in the
PDMPORT server option. A non-MVS TSM client or server uses TCP/IP to
establish a proxy connection with PDM NSS. The TSM request should
originate on the same physical node where the PDM NSS is running.
To use InfoSpeed communication support the following server options are
required.
- PDMName
- Specifies the MVS PDM subsystem identifier. The recommended
identifier is DMES. Check with your InfoSpeed SMP/E programmer for the
PDM subsystem identifier.
- PDMPort
- Specifies the logical port address on which TSM listens for incoming
InfoSpeed connections. This port number is not a TCP/IP port on
MVS. It is a logical port number used exclusively by PDM on MVS and
would not interfere with the same TCP/IP port number on TCP/IP MVS.
Note: | PDM NSS on the workstation node will bind to this port using
platform-specific TCP/IP services. This action may affect other TCP/IP
applications running on that workstation. Check with the administrators
on all platforms making up the PDM InfoSpeed network to ensure the PDMPORT
number will not interfere with existing or future TCP/IP applications.
|
- PDMCONNECT
- This option allows flexibility with the method TSM uses to contact clients
for scheduled operations. The default setting, PDM, forces TSM to use
PDM for outbound connection requests. TSM starts inbound connection
requests to contact TSM clients for scheduled operations using the same
communication method used to field the incoming client scheduler
connection. If your MVS system has IBM TCP/IP installed and the
scheduled TSM client can be reached over the TCP/IP network, you could
consider using TCP for the PDMCONNECT option. This will cause TSM to
first try routing the outbound connect request over TCP/IP. If the
client cannot be reached, the request is retried over PDM. By using
PDMCONNECT TCP, the overhead of setting up a short duration conversation is
less than that of InfoSpeed. There is significant PDM system overhead
involved when establishing a connection over InfoSpeed. Once this
connection is established, the system overhead required to conduct a session
is minimal compared to TCP/IP. Consider the following before deciding
whether to specify PDM or TCP for the PDMCONNECT option:
- Specify PDMCONNECT TCP when both of the following are true:
- The scheduled client is using the TCPCLIENTADDRESS and TCPCLIENTPORT
options (which implies the use of prompted scheduling)
- The TCPCLIENTADDRESS specifies a different IP address from the one at
which the PDM DMENSS process is listening,
- Specify PDMCONNECT TCP and the TCPCLIENTADDRESS and TCPCLIENTPORT client
options when the scheduled client does not reside on the same physical node
where PDM is running and prompted scheduling is used.
Note: | TCP/IP is used only for the server to client scheduler conversation and
notifies the client of a scheduled operation. When the client in turn
establishes a connection with the server to commence the scheduled operation,
the communication path is PDM over InfoSpeed.
|
Restrictions:
- The use of InfoSpeed for server-to-server communications is limited to
virtual volume configurations in which TSM for MVS is the target server and
the source servers are non-MVS TSM servers. The source server
definitions must specify the IP address at which the PDM Node Socket Server is
listening as the high level address and the port address from the PDMPORT
server option as the low level address.
InfoSpeed must be working properly before routing TSM traffic over an
InfoSpeed Data Gateway or and ESCON-only InfoSpeed connection. Do the
following to ensure that InfoSpeed is ready to handle TSM session
activity:
- Start the TSM server with the PDMNAME, PDMPORT and PDMCONNECT server
options. Ensure that the PDM DMESAPI load module (the InfoSpeed
callable API) is available in the link list or STEPLIB so that TSM can load
this module.
- If PDM on MVS and PDM on the workstation nodes are operational and the
workstation node is running the DMENSS process, you will see the following
messages when TSM starts:
ANR5981I InfoSpeed/PDM communication enabled on port 1508.
If you do not see the ANR5981I message, either the DMESAPI load module
cannot be loaded by TSM or PDM is not running or is running under a different
subsystem identifier from the one specified in the PDMNAME server
option. If you cannot correct the problem, restart the TSM server with
the following options in the server options files: TRACE ENABLE
PDMand TRACE BEGIN 'file.name'
This will generate trace records to help in determining the cause of the
problem. Remove these trace options from the server option file after
you have determined the problem. From the PDM MVS Job Log:
DME070I SOCKET APPLICATION ON PORT 01508 HAS INITIALIZED
DME069I NODE SOCKET SERVER ON kingpin, IP 9.115.45.21 IS LISTENING ON PORT 1508
- If you verify that TSM is listening on the PDMPORT as reported in the
ANR5981I message, check the PDM MVS Job Log for the DME070I message.
This message appears in the PDM MVS Job Log immediately after TSM reports the
ANR5981I message. This is an indication that TSM and PDM have
established an interface and are ready to field InfoSpeed communication
requests. Look for the DME069I message in the PDM MVS Job log.
There will be one DME069I message for each PDM node that is configured to
proxy TSM traffic. In the preceding example, the Sun Solaris kingpin
node is running the required InfoSpeed software and has an active DMENSS
process running. The IP address for the kingpin PDM node is shown in
the message.
- At this point the communication path from kingpin over the InfoSpeed
Gateway to PDM on MVS is established. For the preceding example, you
could create the following server stanza in the dsm.opt file
on the kingpin node:
TCPSERVERADDRESS 9.115.45.21
TCPSERVERPORT 1508
COMMMETHOD TCPIP
- Start the resident TSM client specifying this new server stanza.
The connection request will be routed to the DMENSS process which is listening
on the specified port. A connection request will be presented to the
TSM server on the PDMPORT 1508 path and the session will be served using PDM
over InfoSpeed.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]