CONNECT:Direct provides data transfer capabilities between computing systems in a robust manner and is now available on Titan. Since CONNECT:Direct still exists on the OS/390 North and South systems, a different naming convention is needed to distinguish this facility on Titan. As North users of CONNECT:Direct move their applications to Titan, they will need to make some changes.
The following North system CONNECT:Direct changes will be needed:
• //DMNETMAP DD DISP=SHR,DSN=PCC.NDM32.NETMAP
becomes on Titan
//DMNETMAP DD DISP=SHR,DSN=NIH.NDM.NETMAP
• //DMPUBLIB DD DISP=SHR,DSN=PCCSYS.NDM.PROCESS.LIB
becomes on Titan
//DMPUBLIB DD DISP=SHR,DSN=NIH.NDM.PROCESS
• //DMMSGFIL DD DISP=SHR,DSN=PCC.NDM32.MSG
becomes on Titan
//DMMSGFIL DD DISP=SHR,DSN=NIH.NDM.MSG
There is no need for a STEPLIB statement.
New Node Names and IDs on Titan
Remote users who transmit data to applications via CONNECT:Direct will also be affected when these applications move to Titan. They will need to make changes in their SNODE specification, and have their VTAM administrators make changes to the VTAM definitions and CONNECT:Direct netmap at their site.
The new CONNECT:Direct node name is NIH.STD.NDM. The APPLid is NIH4NDM, and the NETid is NIHNET.
Administrators of remote systems should add the above CONNECT:Direct node definitions to their net map files and also add the VTAM definition to their VTAM tables. While these additions should be made as soon as is convenient, changes to the SNODE specification should not be made until the application actually moves from the North system to Titan. We do suggest, however, that a test transfer be done when all system changes have been made.
This information is also available on the Titan Web page.
Interface Online 218 [ April 20, 2001 ]
