OSF DCE Problem Determination Guide

Error Messages and Status Codes
Text: The program could not delete an entry from an error logfile.\n
Explanation: The program gdsdaemon could not delete an entry from it’s internal error
logfile SHDERR.
Action: Report the problem to the responsible software engineer.
0x1260a972 GDS_S_SUP_DNLIST_REMDSA_ERR
Severity: Fatal Component: gds / GDS_S_GENERAL
Text: The program could not retrieve the DSA name for the index %d from the
database.\n
Explanation: The program gdsdaemon could not find the name of a Directory Service
Agent (DSA) for the specified index in an internal name list of the DSA.
Action: Report the problem to the responsible software engineer.
0x1260a969 GDS_S_SUP_FOPEN_ERR
Severity: Fatal Component: gds / GDS_S_GENERAL
Text: File %s could not be opened, errno = %d.\n
Explanation: The program gdsdaemon could not open the specified file.
Action: Evaluate errno for the reason. Depending on the reason, possible actions are:
Change the access mode of the file.
Create the file.
Activate the Directory System.
Report the problem to the responsible software engineer.
0x1260a96d GDS_S_SUP_HEADER_ERR
Severity: Fatal Component: gds / GDS_S_GENERAL
Text: The program could not read the header information of the file %s.\n
Explanation: The program gdsdaemon could not read the header information of the file
where the shadowing jobs are stored.
Action: Try to create the shadowing job again via the tool gdsditadm or report the
problem to the responsible software engineer.
0x1260a964 GDS_S_SUP_ILL_DIRID
Severity: Fatal Component: gds / GDS_S_GENERAL
Text: The gdsdaemon program was started with an illegal directory identifier %d.\n
Explanation: The program gdsdaemon was started with an illegal directory identifier.
Action: Start the program again with a valid directory identifier.
124330 Tandem Computers Incorporated 2−333