Table of Contents
Advertisement
START ERROR 300 : PCS SESSION ID not defined.
Possible Cause
When you are using with B or K shell,
customization of /etc/pro le is incorrect.
When you are using a C shell,
customization of /etc/csh.login is incorrect.
When you are using with HP VUE,
customization of
/usr/lib/X11/vue/Vuelogin/Xsession is
incorrect.
START ERROR 310 : Group 'pcs' not registered.
Possible Cause
The customization of /etc/group le is
incorrect.
START ERROR 330 : Device file /dev/pcs/hpib
Possible Cause
The select code of HP-IB interface card is
incorrect.
When you are using a diskless cluster
system and the computer for a diskless
cnode has no additional HP-IB interface
card, SYSCONFIG.7 must be used as the
template for SYSCONFIG le, not
SYSCONFIG.27.
C-2 Installation Problems You May Encounter
Solution
Check the contents of /etc/pro le. The
/etc/pro le must have following lines:
PCS_SESSION_ID=pcs_$$
export PCS_SESSION_ID
Check the contents of /etc/csh.login. The
/etc/csh.login le must have following line:
setenv PCS_SESSION_ID pcs_$$
Check the contents of Xsession le. The Xsession
le must have following lines:
PCS_SESSION_ID=pcs_$$
export PCS_SESSION_ID
Solution
Check the contents of /etc/group le. The le
must include the following line:
pcs::13:
xx
not found.
Solution
Check the select code setting of additional HP-IB
interface card.
Check the contents of /usr/pcs/etc/SYSCONFIG
le. Note that the SYSCONFIG le is CDF.
Advertisement
Table of Contents
