Hi,

We got the solution:

ANR5092E is due to the parameter TCPNAME SNSTCP
It should now state TCPNAME *NONE*

Problem was documented in RETAIN.  Also seems to cause S0C4 abends.

I hope scheduling works again now.

Regards,

Marc Van den Wyngaert
Janssen Pharmaceutica

*************************************************************************

Hi,

We run ADSM V1 (level13) with Interlinks TCP/IP.

We recently applied maintenance to TCP/IP and now ADSM can no longer prompt our
clients for scheduled backup.

Message is

ANR5092E Unable to initialize TCP/IP driver - error creating acceptor socket.


Does anyone have the same experience?

Any suggestions to solve/attack this problem?

Thanks,

Marc Van den Wyngaert
Janssen Pharaceutica
Belgium
______________________________ Reply Separator _________________________________