My environment is MVS server ADSM v2.1.3  backing up OS/2 Warp servers,
some of which are approx. 1 hour drive from ADSM server. We typically
use SNALU6.2 communication protocol. Every once in a while I will get
the following message:

  CpicOpen: Error unable to allocate conversation, rc:
CM_PRODUCT_SPECIFIC_ERROR (20) from CPIC call cmallc.
sessOpen: Failure in communications open call. rc: -209
ANS4950S Session rejected: SNALU6.2 connection failure.
CPIC product-specific error.

To correct this, is all I have to do is stop and restart scheduler and the next
night the backup runs fine. I'm thinking this is a network problem, am I
correct?
Before I go to the network guru's I'd just like to know if I need to do
something different in ADSM.

Thanks,

Kelly Root