EZZ0730I

Explanation
 A NETACCESS statement was defined without a DEFAULT
entry.  All IP addresses  should be defined in a security zone, but
in an MLACTIVE environment, all IP  addresses must be defined in a
security zone.  Any request to receive or send  to an IP address that
is not defined in a security zone fails in an  MLACTIVE environment.
 You should always configure DEFAULT to ensure that a  zone is found
for all IP addresses. 

System action
 If processing an initial profile or
a VARY TCPIP,,OBEYFILE command, TCP/IP continues. 
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
Add a DEFAULT entry to the NETACCESS statement. See NETACCESS statement in z/OS Communications Server: IP Configuration
Reference for more information.
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 a VARY TCPIP,,OBEYFILE
command using this profile.

Module
 EZACFPAR

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.

Procedure name
  rdparser