z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM)
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


EZZ0799I

z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM)
SC27-3657-01

EZZ0799I
VIPADISTRIBUTE WEIGHT IGNORED WHEN DISTMETHOD IS NOT WEIGHTEDACTIVE

Explanation

The VIPADISTRIBUTE statement WEIGHT keyword is valid only when the DISTMETHOD parameter value is WEIGHTEDACTIVE. The WEIGHT keyword is ignored.

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

If this message was displayed as a result of a VARY TCPIP,,SYNTAXCHECK command:

  1. Make one of these changes to correct the statement:
    • Remove the WEIGHT parameter.
    • Change the DISTMETHOD parameter to WEIGHTEDACTIVE.
  2. Issue the VARY TCPIP,,SYNTAXCHECK command again to verify that you have corrected all syntax errors in the profile.
    Otherwise, to use the WEIGHT keyword, do the following steps:
    1. Change the VIPADISTRIBUTE statement to specify a DISTMETHOD parameter value WEIGHTEDACTIVE in the original profile.
    2. 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

Not applicable.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014