EZZ0749I

Explanation
 The specified parameter cannot be used on a VIPADISTRIBUTE
DEFINE statement if the statement specifies an IPv4 address. 
 In
the message text:parm
A parameter on the VIPADISTRIBUTE DEFINE statement
linenum
The line number in the configuration file on which the parameter
is specified

System action
If processing an initial profile or
a VARY TCPIP,,OBEYFILE command, TCP/IP continues. The VIPADISTRIBUTE
DEFINE statement is ignored.
This message is also
displayed as part of VARY TCPIP,,SYNTAXCHECK processing when the VARY
TCPIP,,SYNTAXCHECK command detects this error in a profile data set.
No changes are applied to the active configuration by VARY TCPIP,,SYNTAXCHECK
processing.

Operator response
 Contact the system programmer.

System programmer response
 Make one of these changes to correct the problem:  Remove the specified parameter from the VIPADISTRIBUTE DEFINE
statement.
Change the IPv4 address to an IPv6  interface.See the information
about VIPADYNAMIC statement in z/OS Communications Server: IP Configuration
Reference.

If this message was displayed as a result of a VARY TCPIP,,SYNTAXCHECK
command, issue the command again to verify that you have removed all
syntax errors from the profile.  Otherwise, issue the VARY TCPIP,,OBEYFILE
command with the changed VIPADYNAMIC block.

User response
 Not applicable.

Problem determination
 Not applicable.

Source
 z/OS® Communications
Server TCP/IP: Configuration & Initialization

Module
 EZACFPVA

Routing code
 8

Descriptor code
 12

Automation
 This message is directed to the console.
 You can use automation to detect and respond to TCP/IP profile errors
reported during initial profile and VARY TCPIP,,OBEYFILE processing.
This message can also be displayed during VARY TCPIP,,SYNTAXCHECK
processing.  Because the VARY TCPIP,,SYNTAXCHECK command does not
affect the active configuration, you might want to adjust your automation
to ignore the configuration messages that are displayed after EZZ0061I
and before EZZ0065I.

Example
  EZZ0749I VIPADISTRIBUTE ENCAP ON LINE 35 CANNOT BE SPECIFIED WITH AN IPV4  ADDRESS 