• Subject: Controlling ports used by DDM
  • From: rob@xxxxxxxxx
  • Date: Mon, 22 Jan 2001 16:37:30 -0500


We are using DDM over IP for our internal use.  We have a bunch of internal
companies and have done some tight integration we call internal EDI.  We
are now going to be doing some major work for a customer which has also has
a 400 running BPCS 4.0.5CD.  We want to be doing this internal EDI with
them.  We will be setting up a VPN and continue to use DDM over IP.   IT
has always been considered a strategic advantage here, and one of the 4
pillars of our company.  We will be doing all of the customers connection
to the Internet over their T1.

I've done some testing and which port gets used by the server seems to
jump.  Testing involved:
CRTDDMF FILE(QTEMP/AAAROB) RMTFILE(ROB/AAAROB) RMTLOCNAME(rmtsys *IP)
UPDDTA QTEMP/AAAROB
Then going to rmtsys and doing
WRKOBJLCK OBJ(ROB/AAROB) OBJTYPE(*FILE)
and displaying the joblog.  In message CPI9162 it displays the port used.
But the darn thing will vary!  10516, 10530, etc.  My thought is to only
open up 10500 through 10599.  The Cisco kid can do this but he wondered if
it also uses a different port to initialize the conversation.  I've heard
of this happening for ftp or telnet, like use port xxx to start the comm
then use port yyy for the actual work.  I am not sure that DDM uses any of
these initiator ports.

Opinions please about which ports to open up for DDM.

Rob Berendt

==================
Remember the Cole!

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].