>ANS1017E (RC-50)  Session rejected: TCP/IP connection failure

Seth - Perhaps some of the following may help, from my notes...

ANS4017E Session rejected: TCP/IP connection failure [Same as ANS1017E]
        This is what the client sees and reports, but has no idea why.
        The cause is best sought in the ADSM server Activity Log for that
time.
        Could be a real datacomm problem; or...
        If during a Backup, likely the server cancelling it due to higher
        priority task like DB Backup starting and needing a tape
        drive...particularly when there is a drive shortage.  Look in the
        server Activity Log around that time and you will likely see
        "ANR0492I All drives in use. Session 22668 for node ________ (AIX)
        being preempted by higher priority operation.".
        Or look in the Activity Log for a "ANR0481W Session NNN for node
        <NodeName> (<NodeType>) terminated - client did not respond within
NN
        seconds." message, which reflects a server COMMTimeout value that is
        too low.  (The AIX server default is a puny 60 seconds.)  Boost it -
and
        don't be afraid to make it half an hour or more, which is how long
it
        will take clients to plow through massive file systems during a
backup.
        If server system is MVS (OS/390), it could mean that the ADSM Server
        was not up on that system.