QOSConfig statement

Use the QOSConfig statement to specify the path of a local QoS policy file that contains stack-specific QoS policy statements.

Results: For the associated TCP/IP image on the policy client, if the PolicyServer statement specifies remote QoS policies, then one the following situations occurs:

If no local QoS policies are installed, then the QOSConfig statement is ignored.
If local QoS policies are already installed, the result is the same as if the QoSConfig statement had been deleted.

The refresh interval for the QOSConfig file is inherited from the image configuration file containing the corresponding QOSConfig statement.

The QOSConfig statement can appear only in an image configuration file. If a QOSConfig statement appears multiple times in an image configuration file, the last occurrence of the statement is used. If the QOSConfig statement appears in the main configuration file, it is ignored (unless the main and image configuration files are the same file).

Syntax


>>-QOSConfig--path---------------------------------------------><

Parameters

path

The path of the stack-specific QOS policy file to be installed.

You can specify an MVS™ data set name or a z/OS® UNIX file name. MVS data set names must be enclosed in single quotation marks (' ') and preceded by a double slash (//). Following are examples of both types of names:

QOSConfig  //'USER1.PAGENT.CONF(QOS)'
QOSConfig  /u/user1/pagent.qos

Restriction: Dynamic monitoring for file updates using the -i startup option is supported only for z/OS UNIX files; MVS data sets are not monitored for change.

Results:

If the QOSConfig statement is not specified, then QoS policies are defined in the image configuration file.
If the QOSConfig statement is deleted and FLUSH is configured, then all QoS policies that are defined in this QoS policy file are deleted from the corresponding stack.