Open System Services NFS Management and Operations Guide

Effect
PCNFSD services cannot be started.
Recovery
Correct the entry in error and restart the PCNFSD process.
*PCNFSD* Cannot launch or access PCAUTHD
Cause
PCNFSD launches PCAUTHD at initialization time and restarts it if it fails. This message indicates
that either PCAUTHD could not be created or it could not communicate with PCNFSD to receive
its startup message.
Effect
PCNFSD services cannot be started.
Recovery
Follow these steps:
1. Verify that the PCAUTHD object is located in the subvolume where PCNFSD resides and
that it is secured for execute access by the user ID that started PCNFSD.
2. Make sure that there are sufficient system resources to create the PCAUTHD process, such
as swap space, low PINs, memory, and so on.
If the problem still occurs, log on as the user that started PCNFSD and, at a TACL prompt, try to
run PCAUTHD to get some additional indication of what might be causing the error.
*PCNFSD* Cannot launch or access PCLPRD
Cause
PCNFSD launches a PCLPRD server each time a job needs to be printed. This error indicates
that PCLPRD either could not be created or could not communicate with PCNFSD to receive its
startup message.
Effect
Spooling services are unavailable.
Recovery
Follow these steps:
1. Verify that the PCLPRD object is located in the subvolume where PCNFSD resides and that
it is secured for execute access by the user ID that started PCNFSD.
2. Make sure that there are sufficient system resources to create the PCLPRD process, such as
swap space, low PINs, memory, and so on.
If the problem still occurs, log on as the user that started PCNFSD and, at a TACL prompt, try to
run PCLPRD to get some additional indication of what might be causing the error.
*PCNFSD* Cannot launch or access SCP: name
name
contains the name of the SCP process in error.
Cause
PCNFSD first attempts to communicate with $ZNET.#ZSPI. If $ZNET does not exist, PCNFSD
attempts to start it. This message indicates that SCP either could not be created or could not
communicate with PCNFSD. Note that there is a 15-second limit for I/O to finish, and therefore
this message might appear on very busy systems.
Effect
PCNFSD services are unavailable.
Recovery
If $ZNET does not exist, start it or verify that the SCP object is located in the $SYSTEM.SYSTEM
or $SYSTEM.SYSnn subvolume and that it is secured for execute access by the user ID that
82 PCNFSD Error Messages