RE: EE connections including STRPASTHR, SNADS, SAVRSTLIB and DDM will hang for 20 seconds to 4 minutes

STRPASTHR, TELNET do not use DDM files. So changing that will have no
effect.

If you can ping it (and at least get back the right IP address even if
they block pings) then you can use that name in CRTDDMF.

There is a tiny risk that SNA DDM will use a different port than TCP DDM
and that may take some firewall work but, hey, you can always create a new
ddm file and test that first, eh?

SNDNETSPLF and SNDNETF don't give a RA about DDM. That's all tied up in
that CFGDSTSRV, and ADDDIRE, kind of stuff. Same as STRPASTHR, (only
STRPASTHR doesn't need ADDDIRE).

There are only two risks that I can think of:
1 - Getting the right location name. If you can telnet to it, or ping it,
then you've got the right location name.
2 - Port blocking. That's a really simple test by creating a DDM file
named differently yet pointing to the same location.
CRTDDMF FILE(TESTLIB/OTHERSITE) RMTFILE(SYSIBM/SYSDUMMY1)
RMTLOCNAME(OTHERSITE *IP)
DSPPFM FILE(TESTLIB/OTHERSITE)
If you can see the contents of the remote SYSIBM/SYSDUMMY1 then the port
is not blocked.

And if the CRTDDMF is not buried in code anywhere you do not have to
change ONE line of code to convert SBMRMTCMD.

Rob Berendt