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 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.
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. |
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:
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:
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 PDM 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.
DME070I SOCKET APPLICATION ON PORT 01508 HAS INITIALIZED DME069I NODE SOCKET SERVER ON kingpin, IP 9.115.45.21 IS LISTENING ON PORT 1508
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.
TCPSERVERADDRESS 9.115.45.21 TCPSERVERPORT 1508 COMMMETHOD TCPIP