determines an optimal access path to store or retrieve the data

1) Class of service. Indication of how an upper-layer protoco requires that a lower-layer protocol treat its messages. In SNA subarea routing, COS definitions are used by subarea nodes to determine the optimal route to establish a given session. A COS definition comprises a virtual route number and a transmission priority field. Also called TOS (type of service).
2) Corporation for Open Systems. Organization that promulgates the use of OSI protocols through conformance testing, certification, and related activities.

The ndd Command
Several of the network settings discussed in this article are configured using the ndd command. It is used to examine and set kernel module parameters, namely the Transmission Control Protocol/Internet Protocol (TCP/IP) drivers. Most kernel parameters accessible through ndd can be modified without rebooting the system.
To see which parameters are available, use the following ndd commands:
# ndd /dev/arp \?
# ndd /dev/icmp \?
# ndd /dev/ip \?
# ndd /dev/tcp \?
# ndd /dev/udp \?These commands list the parameters for the
Address Resolution Protocol (ARP), Internet Control Message Protocol (ICMP), IP, TCP, and User Datagram Protocol (UDP) drivers. In this updated BluePrint OnLine article, the various drivers are listed in alphabetic order.
The Solaris 8 and 9 OE releases include support for the next version of the Internet Protocol suite (IPv6) and the Internet Protocol Security architecture (IPsec). These have additional drivers. A list of parameters for these drivers can be found with the following commands:
# ndd /dev/ip6 \?
# ndd /dev/icmp6 \?
# ndd /dev/tcp6 \?
# ndd /dev/udp6 \?
# ndd /dev/ipsecesp \?
# ndd /dev/ipsecah \?The IPv6 parameters for the ICMP, IP, TCP, and UDP drivers are also listed in the standard (IPv4) parameter lists. This article does not discuss IPsec, but the parameters are listed here for completeness. Neither IPv6 nor IPsec support will be supported in any Solaris OE release earlier than Solaris 8 OE.
There are also network interface device drivers with parameters that can be adjusted using the ndd command. The following command will list the parameters for the hme (FastEthernet) device driver:
# ndd /dev/hme \?The "\?" string is required to prevent the shell from interpreting the "?" as a special character. Using "\?" will list all parameters for the driver and indicate whether the parameter is read only, write only, or
read and write. The current parameter value or status information can be read by specifying the driver and
parameter names.
This example shows the output of a ndd command examining the debugging status of the ARP driver. (The output "0" indicates that the option is disabled.)
# ndd /dev/arp arp_debug
0ndd-specified parameter values are integers with "0" meaning disable, "1" meaning enable, or a large integer to set a time or size value. Setting parameters requires the "-set" option, the driver name, the parameter name, and the new value.
For example, to enable debugging mode in the ARP driver use this ndd command:
# ndd -set /dev/arp arp_debug 1Notes on Parameter Changes Previously, only some ndd parameter documentation was available from Sun. This has been a known problem. Since the release of the Solaris 8 OE, there is now documentation of selected tunable TCP/IP parameters. The book is the Solaris Tunable Parameters Reference Manual and is available on the docs.sun.comSM web site. Most of the parameter information for the Solaris 9 OE is also applicable to previous releases.
Network parameters set with the ndd command apply to the currently running Solaris instance; parameter changes do not last past system reboots. Once a system is booted, the default parameters will be used. To provide a simple method of setting the ndd network parameters mentioned in this article at Solaris boot time, a system init script has been created and is described in "Sample System nddconfig init Script."
Setting driver parameters involves making trade-offs. Most parameters involve changing the default Solaris OE configuration. The default settings are optimal for most situations. Adjusting parameters might affect normal system operation, so Sun does not encourage parameter changes.
All ndd parameter changes suggested in this article include a discussion of trade-offs, where appropriate. Some settings change the expected operation of systems; these are noted. Most of these recommended parameter changes are being actively used on production systems at customer sites.
Sun sometimes alters parameter names or adds additional parameters between releases of the Solaris OE. Most of the IPv4 parameters described in this article are used consistently across Solaris OE releases. When there are exceptions, the text for the parameter specifically mentions the OE differences.

Managerial grid model
The Managerial Grid Model (1964) is a behavioral leadership model developed by Robert Blake and Jane Mouton. This model identifies five different leadership styles based on the concern for people and the concern for production. The optimal leadership style in this model is based on Theory Y.
 
A graphical representation of the Managerial GridAs shown
in the figure, the model is represented as a grid with concern for production as the X-axis and concern for people as the Y-axis; each axis ranges from 1 (Low) to 9 (High).

The five resulting leadership styles are as follows:

The impoverished style (1,1)
In this style, managers have low concern for both people and production. Managers use this style to avoid getting into trouble. The main concern for the manager is not to be held responsible for any mistakes, which results in less innovative decisions.

The country club style (1,9)
This style has a high concern for people and a low concern for production. Managers using this style pay much attention to the security and comfort of the employees, in hopes that this would increase performance. The resulting atmosphere is usually friendly, but not necessarily productive.

The produce or perish style (9,1)
With a high concern for production, and a low concern for people, managers using this style find employee needs unimportant; they provide their employees with money and expect performance back. Managers using this style also pressure their employees through rules and punishments to achieve the company goals. This style is based on Theory X, and is commonly applied by companies on the edge of failure.

The middle-of-the-road style (5,5)
Managers using this style try to balance between company goals and workers' needs. By giving some concern to both people and production, managers who use this style hope to achieve acceptable peformance.

The team style (9,9)
In this style, high concern is paid both to people and production. As suggested by the propositions of Theory Y, managers choosing to use this style encourage teamwork and commitment among employees. This method relies heavly on making employees feel as a constructive part of the company.

In computing, load balancing is a technique to spread work between many computers, processes, disks or other resources in order to get optimal resource utilization and decrease computing time.

If you ask three warehousing professionals, you may get four different answers! However, it gets too full somewhere below 100 percent. About 85 percent is optimal. Beyond that point, you start moving stock to make room for inbound materials. Therefore, being theoretically full is always different from being practically full.