Update cycle 9202 brought with it a renamed node, NIHLIST, which also hosts a Listserv peer. This dual change (node & Listserv) has the unfortunate side effect that your Listserv may have trouble communicating with NIHLIST, if an intermediate node has failed to update the RSCS (or JNET, for that matter) routing tables. Check your console logs for the fatidical DMTCMQ310E Location NIHLIST is not defined RSCS error message, so you can pester the appropiate slow updater into action. Cheers, Juan P.S. 1: NIHLIST was formerly known as NIHCUSV1. P.S. 2: Fortunately, NIHLIST has not defined any lists yet.