Why is the VIPA not being used as a source after z/OS upgrade?

Question & Answer

Question

After an upgrade to z/OS 2.2 (or above), the preferred address (VIPA) is not being used for outbound connections. The SOURCEVIPA keyword is on the IPCONFIG statement, SOURCEVIPAINTERFACE is specified on all of the INTERFACE statements, the HOME address list has the VIPA before the real devices, and there are no applicable SRCIP statements. But the OSA's home address is still being used.

Answer

In z/OS 2.2, the CLAWUSEDOUBLENOP and STOPONCLAWERROR keywords were removed from the IPCONFIG statement. If either of these is still coded, then the entire IPCONFIG statement (including the SOURCEVIPA keyword) is ignored and the following message produced:

 EZZ0318I CLAWUSEDOUBLENOP WAS FOUND ON LINE xxx AND VALID IPCONFIG PARAMETER WAS EXPECTED

Remove the obsolete keywords either and restart TCPIP or do an OBEYFILE command specifying a data set with just the complete IPCONFIG statement.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

ZOSCS COMMSERVER

Was this topic helpful?

Document Information

Modified date:
30 July 2018

UID

dwa1461565

Tips