EZZ0784I

Explanation
 The specified parameter cannot be used on a VIPADISTRIBUTE
DEFINE statement that specifies the ENCAP parameter. The parameter
is ignored.
 In the message text: 
parm
The parameter on the VIPADISTRIBUTE DEFINE statement
linenum
The line number in the configuration file on which the parameter
is specified

System action
 TCP/IP continues. The statement is processed,
but the specified configuration  parameter 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 statement: Remove the specified parameter from the VIPADISTRIBUTE DEFINE
statement. 
Remove both the TIER1 and ENCAP parameters.See VIPADYNAMIC statement in z/OS Communications Server: IP Configuration
Reference for more information about valid VIPADYNAMIC
statement parameters.

If this message was displayed as a result of a VARY
TCPIP,,SYNTAXCHECK command, issue the command again to verify that
you have corrected all syntax errors in the profile.Otherwise:
If you removed the TIER1 and ENCAP parameters from the statement
do the following:Issue VIPADISTRIBUTE DELETE statements for all previous VIPADISTRIBUTE
DEFINE statements for this DVIPA.
Issue a VIPADELETE statement for the DVIPA.

Issue the VARY TCPIP,,OBEYFILE command with the changed VIPADYNAMIC
block. 

See the information about the VIPADYNAMIC
statement in z/OS Communications Server: IP Configuration
Reference.

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 appear 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
  EZZ0784I VIPADISTRIBUTE OPTLOCAL ON LINE 11 IS IGNORED WHEN ENCAP IS SPECIFIED