>We're running OS/390 V2.6, TCP/IP 3.5 and we encountered problems starting
ADSM V3.1 (which is at 2.20).  It seems that >ADSM is looping trying to
complete its connection to TCP/IP.

>Anyone else having this problem?

The cause of the problem was due to not giving ADSM access to OMVS.  Our
ESM is Top Secret and it certainly seemed secretive about displaying any
violations!  Our security person had to browse the Top Secret log to find
the problem.