Question & Answer
Question
A distributed VIPA has a VIPADEFINE on one system with VIPABACKUPs on some others in the sysplex. After a sysplex wide shutdown, one of the backup systems was the first to come up. But the VIPA was not created, and applications attempting to bind their listener using that address failed with errno EADDRNOTAVAIL (EDC8116I message) and reason code 744C7230 (JRBINDADDRNACTIVE - Local address was not active when processing the bind request).
Answer
The backup definition was coded as follows:
VIPABACKUP 15 10.9.8.7
This form of specification will only take over an existing DVIPA when the system with VIPADEFINE goes down. In order to have the backup system create the DVIPA when IPLed first, the following form needs to be used:
VIPABACKUP 15 MOVEABLE IMMED 255.255.255.255 10.9.8.7
Product Synonym
ZOSCS COMMSERVER
Was this topic helpful?
Document Information
Modified date:
27 February 2018
UID
dwa1433874