Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
EZZ0829I z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM) SC27-3657-01 |
|
EZZ0829I MORE THAN 31 BACKUPS WERE SPECIFIED ON THE VIPADISTRIBUTE
STATEMENT WHEN DISTMETHOD IS HOTSTANDBY ExplanationWhile processing a profile data set, TCP/IP found a VIPADISTRIBUTE statement that specified more than thirty one addresses as BACKUP addresses. Because the distribution method is HOTSTANDBY, there must be exactly one DESTIP address that is PREFERRED and at least one DESTIP address that is coded as BACKUP. Thirty-one is the maximum number of DESTIP addresses that may be specified as BACKUP addresses. System actionIf processing an initial profile or a VARY TCPIP,,OBEYFILE command, TCP/IP continues, but 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 responseContact the system programmer. System programmer responseIf this message was displayed as a result of a VARY TCPIP,,SYNTAXCHECK command, correct the error before using the profile data set as an initial profile or as a VARY TCPIP,,OBEYFILE profile. Otherwise, do the following steps to correct the problem:
See the information about the VIPADYNAMIC statement in z/OS Communications Server: IP Configuration Reference. User responseNot applicable. Problem determinationNot applicable. Sourcez/OS® Communications Server TCP/IP: Configuration & Initialization ModuleEZACFPVA Routing code10 Descriptor code12 AutomationThis 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
|
Copyright IBM Corporation 1990, 2014
|