Cautions in Setting Environment Variables

Observe these cautions when setting APPX environment variables:

• APPX_PRT_FI_DIR must have a trailing slash.

This variable determines where APPX creates report files. Examples in Unix and Windows:

$ export APPX_PRT_FI_DIR=/tmp/pat/

C:\> set APPX_PRT_FI_DIR=\\server\printfiles\pat\

• Make sure path names are valid.

For any variable requiring a file or directory pathname, make sure that all directories in the path exist. On Unix (or when editing appx_print for UniQue), make sure that the case you use in the variable setting matches the actual case of the filename. A mistake here can cause log files to not appear, or APPX to behave incorrectly.

• Setting a variable in .profile for an APPX/Client user will have no effect.

While a variable set in a Unix .profile will affect a user’s APPX session if they Telnet in to the APPX machine, it will not affect a APPX/Client login. Since we directly start up APPX from APPX/Client, rather than going through a Command Shell as with Telnet, no shell initialization files are processed.

• Clicking "Apply" after a change will not update a running copy of WinAppxD.

WinAppxD runs as a system service. As such, the only way to get WinAppxD (and subsequent APPX/Client sessions started from it) to recognize changes in the system environment is to reboot the server.