|
CSS is capable of providing
several independent print server environments on one system. To operate in
such an environment, the CSS_ENV variable must point to the home
directory of the Virtual CSS Server. Setting CSS_ENV to the
value "/" will cause the CSS programs to run in
the standard (main) environment.
Setting CSS_ENV
• Bourne Shell sh(1), Bourne Again
Shell bash(1)
.profile (sh)
.bashrc (bash) |
CSS_ENV=/usr/css1
export CSS_ENV |
| shell prompt |
CSS_ENV=/usr/css1
export CSS_ENV |
| temporarily |
CSS_ENV=/usr/css1 command
[option...] |
• C-Shell csh(1)
| .login |
setenv CSS_ENV /usr/css1 |
| shell prompt |
setenv CSS_ENV /usr/css1 |
| temporarily |
NA |
Virtual CSS Server Directory Stucture
The home directory for each virtual
server must contain the following sub-directories:
| Directory |
Contents |
| etc |
| File |
Contents |
Optional |
| css.default |
configuration parameters |
|
| css.devices |
device definitions |
|
| css.forms |
form definitions |
|
| css.banner |
banner message of the day |
yes |
|
| lib |
Internal CSS control files such as compiled
device and form definitions, the report queue and others. |
| spool |
Optional directory for intermediate spool files. May
be overwritten by setting the CSS_SPOOL_DIR parameter in $CSS_ENV/etc/css.default. |
A typical setup session:
# if not registered yet, enter virtual server license (type CVS)
CSS_ENV=/ /etc/ulm
# setup
directory structure:
umask 0
mkdir /usr/css2
cd /usr/css2
mkdir etc lib
# register user activation keys
(type CSS and WinCss)
CSS_ENV=/usr/css2 /etc/ulm
# copy and modify CSS configuration files
cp /etc/css.* ./etc
vi ./etc/css.*
# compile device and form definitions, initialize report queue
CSS_ENV=/usr/css2 /etc/csa -d -f -R |
Device Sharing
To share devices among several virtual CSS
environments, the external lock feature of css.devices
(el capability) must be used. It is mandatory that each logical
device using a particular physical device has the identical el
capability value defined. Devices in use by another virtual server or
software package will show the busy status in the css(U)
interface program.
Configuration Parameters Needing
Special Attention
Setting the CSS_SPOOL_DIR
configuration variable of distinct CSS environments to the same
directory will result in data loss.
The WINCSS_PORT configuration
variable should be set to a distinct port number for each virtual CSS
environment. As an alternative, you can use the cssws(U)
p-option to set individual port numbers. One cssws(U)
windows server must be started for each virtual environment at boot time.
Sample /etc/rc setting:
• WINCSS_PORT set in each css.default
file
...
CSS_ENV=/ /usr/lib/css/cssws
CSS_ENV=/usr/css2 /usr/lib/css/cssws
... |
• WINCSS_PORT not set
...
CSS_ENV=/ /usr/lib/css/cssws -p 6851
CSS_ENV=/usr/css2 /usr/lib/css/cssws -p 6852
... |
|
