HPlogo MPE/iX Error Messages Manual Volume I: HP 3000 MPE/iX Computer Systems > Chapter 7 Directory Traversal Subsystem

(Subsystem 519)

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

This section presents the error messages for the Directory Traversal Subsystem (519).

1

MESSAGE

Undefined error.

CAUSE

An error occurred that is not translated by the DIRT subsystem.

ACTION

Set break point at DIRT.HANDLE_ERROR and look at the stack trace to see which subsystem is generating the error in the first place.

31

MESSAGE

DIRT cannot go beyond PX_MAX_LEVEL (PX_PATH_MAX div 2) levels. The levels are counted from / and CWD depending on whether the path_ptr^ is absolute of relative path name.

CAUSE

DIRT's internal limitation due to using arrays of fixed size.

ACTION

Either you can continue traversing at least other directories that are not that deep (error function returns TRUE) or you can change the CWD to a lower level directory and continue search from there.

32

MESSAGE

DIRT cannot return a filename longer than PX_PATH_MAX bytes.

CAUSE

During the traversal of the directory, DIRT encountered a file whose pathname would exceed PX_PATH_MAX bytes.

ACTION

Either you can skip this name (error function returns TRUE) or you can change the CWD to a lower level directory and continue search from there.

33

MESSAGE

Path_ptr^ contains a name in MPE structure but name length exceeds 16 characters.

CAUSE

Names directly under /, MPE account, MPE group cannot exceed 16 characters.

ACTION

Pass a correct path_ptr^.

61

MESSAGE

Error during HPDIRREAD.

CAUSE

DIRT called HPDIRREAD and encountered unexpected error.

ACTION

Set a break point at DIRT.HANDLE_ERROR and look at the stack trace to see what error is being generated by HPDIRREAD.

91

MESSAGE

Undefined error while using directory services.

CAUSE

DIRT called some directory services and encountered unexpected error.

ACTION

Set a break point at DIRT.HANDLE_ERROR and look at the stack trace to see what error is being generated by directory services.

92

MESSAGE

A component of the path does not exist.

CAUSE

A component of the path_ptr^ does not exist.

ACTION

Check the path_ptr^ and try again.

93

MESSAGE

A component of the path is not a directory.

CAUSE

A component of the path_ptr^ exists but is not a directory.

ACTION

Check the path_ptr^ and try again.

94

MESSAGE

User lacks TD access.

CAUSE

User lacks TD access on a directory in the path.

ACTION

Either give user the TD access or tell user about the security violation.

95

MESSAGE

The last component of the path does not exist.

CAUSE

The last component of the path_ptr^ does not exist.

ACTION

Check the path_ptr^ and try again.

96

MESSAGE

Internal security error.

CAUSE

Unknown. DIRT was using some security service while the error occurred.

ACTION

Set a break point at DIRT.HANDLE_ERROR and look at the stack trace to see what error is being generated by security.

121

MESSAGE

Error while calling HPFOPEN.

CAUSE

Unknown. DIRT was calling HPFOPEN when the error occurred.

ACTION

Set a break point at DIRT.HANDLE_ERROR and look at the stack trace to see what error is being generated by HPFOPEN.

122

MESSAGE

Security violation during HPFOPEN, failed to open a directory.

CAUSE

User lacks appropriate access to HPFOPEN the directory.

ACTION

Check if the user has RD access on the directory.

123

MESSAGE

Too many file already open, failed to open a directory.

CAUSE

The user has too many files already open.

ACTION

Close the files/directories opened prior to calling DIRT. It is also possible that there are too many directories being opened by DIRT itself. In such a case change CWD to a lower level and try again.

124

MESSAGE

The directory has been opened exclusively by someone else.

CAUSE

DIRT is trying to HPFOPEN a directory that is opened exclusively by someone else.

ACTION

Wait for the other process to close the directory or skip this directory by error function returning TRUE.

125

MESSAGE

The UFID of the directory is a bad one.

CAUSE

It is possible that there is directory corruption. Also, it is possible that the directory has been purged by someone else in a small time window (not a bug - just that state of the dir has changed).

ACTION

If it is the first reason, run FSCHECK to see if everything is ok. If it is the second reason, don't worry and just skip this directory.

156

MESSAGE

The filter supplied to DIRT is not correct.

CAUSE

The filter_ptr^ is not correct syntactically.

ACTION

Check the filter_ptr^ and try again.

157

MESSAGE

The path supplied to DIRT is not correct.

CAUSE

The path_ptr^ is not correct syntactically.

ACTION

Check the path_ptr^ and try again.

161

MESSAGE

Error occurred while calling Genfxlate.

CAUSE

Error occurred while calling Genfxlate.

ACTION

Check the MPE syntax path_ptr^ and try again.

162

MESSAGE

Genfxlate found group component of name doesn't exist or is a dir.

CAUSE

MPE syntax path_ptr^ has a non-existent group or is a directory.

ACTION

Check the MPE syntax path_ptr^ and try again.

163

MESSAGE

Genfxlate found account component of name doesn't exist or is a dir.

CAUSE

MPE syntax path_ptr^ has a non-existent account or is a directory.

ACTION

Check the MPE syntax path_ptr^ and try again.

Feedback to webmaster