This is a list of the software directly used by the file collections component of PSSP. Problems within the requisite software may manifest themselves as error symptoms in file collections software. If you perform all the diagnostic routines and error responses listed in this chapter, and still have problems with the file collections component of PSSP, you should consider these components as possible sources of the error. They are listed with the most likely candidate first, least likely candidate last.
During configuration of File Collections, installed files are copied from /usr/lpp/ssp/filec to their proper location in directories /var/sysman and /usr/lpp/ssp/bin. If these files are updated during the application of a PTF, the install script ensures that the files in /var/sysman and /usr/lpp/ssp/bin are updated. However, if an error occurs during this processing, the files may not be updated properly.
IBM ships and installs the following files:
Other files are created during configuration. If SP system configuration errors occur, these files may not be created.
This list is for the current level of PSSP. Some files may not exist for older levels of PSSP.
On a node, File Collections relies on the /etc/mastername command to supply the boot/install server hostname. The boot/install server could be the control workstation or a node which has been configured as a boot/install server. The /etc/mastername command, in turn, relies on the existence of the /etc/ssp/server_name file. This file is updated when necessary by the SP Installation and Configuration code. This is the method used by File Collections to obtain the File Collections server name when running on a node.
Normally, configuration errors can be corrected by running /usr/lpp/ssp/bin/services_config. The services_config script calls filec_config with the input parameters necessary to configure File Collections.