Hello,
Apologies for incorrect usage of terminology and a relatively dumb query.
I had worked with Connect-Direct (CD) as an application programmer 5-6 years back for a client, the task involved writing NDM scripts for transmissions (both GET and PUT, or more aptly Send and Receive) and then using them in batch processes; didn't really wonder how the process was setup. Later as clients changed, moved to good old FTP setup.
Now at my current client, it is back to CD.
We need to setup CD process to be able to GET/PUT datasets to the client's LAN location. My limited networking understanding says, we need to have mainframe and the LAN network acting as a server-client so that a communication hand-shake can happen and the data can flow.
Query: My query is do we need to have a CD client to be installed at the destination node as well, for mainframe CD to send/receive data between the two? From this link, my understanding is, yes, it is required to be installed on the other end as well.
Please correct me if i am totally off-track here.
Thank you.
Setting up Connect-Direct
-
- Global moderator
- Posts: 3720
- Joined: Sat Dec 19, 2009 8:32 pm
- Skillset: Systems programming, SAS, COBOL, CICS, JCL, SMS, VSAM, etc.
- Referer: other forum
- Location: Dubuque, Iowa, USA
Re: Setting up Connect-Direct
My understanding is that yes, CD software has to exist on both ends of the connection for the process to work.
-
- Posts: 381
- Joined: Tue Jan 28, 2014 1:52 pm
- Skillset: COBOL, JCL, DFSORT, VSAM
- Referer: Google
Re: Setting up Connect-Direct
Thank you Mr. Sample; I'll look at the documentation to figure out how same can be setup on both sides - mainframe and front-end interface.