HP 3000 Manuals HP 3000 Manuals
Appendix C User Logging Error Codes
Table C-1 lists the User Logging error codes and their meanings. These
error codes are returned in the logstatus parameter of each of the User
Logging intrinsics.
Table C-1. User Logging Error Codes
-----------------------------------------------------------------------------------------------
| | | |
| Code | Meaning | Corrective Action |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 0 | No error for this intrinsic call. | None. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 1 | User requested NOWAIT mode and the | Retry the intrinsic call. |
| | logging process is busy. | |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 2 | Parameter out of bounds in logging | Check all parameters to be sure they are |
| | intrinsic. For example, the address | correct and addressed properly. |
| | of data, for WRITELOG, and the length | |
| | given will go beyond the top of the | |
| | stack. | |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 3 | A request to open or write to a | Use the :SHOWLOGSTATUS command to |
| | logging process that is not running. | determine which User Logging processes |
| | | are running. To start or restart a User |
| | | Logging process, the system supervisor |
| | | can use the :LOG command. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 4 | Incorrect index parameter passed to a | The index parameter must be a number |
| | User Logging intrinsic. | that was returned by a successful call |
| | | to the OPENLOG intrinsic. Do not change |
| | | it. It will not be valid after a call |
| | | to CLOSELOG with that index parameter. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 5 | Incorrect mode parameter passed to a | For the WRITELOG intrinsic, valid mode |
| | user logging intrinsic. | parameters are 0, 1, and 2. For all |
| | | other intrinsics, valid mode parameters |
| | | are 0 and 1 only. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 6 | A request to open the logfile was | The :SHOWLOGSTATUS command or the |
| | denied and the User Logging process | LOGINFO intrinsic will give the current |
| | was suspended (the User Logging | state of the User Logging process. If |
| | process is stopping or attempting | the process is stopped, it must be |
| | recovery from an exception condition, | restarted by the system supervisor |
| | for example, a power failure). | before the user can open the file. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 7 | Illegal capability. The user must | See your account or system manager to |
| | have LG or OP capabilities to use the | obtain the proper capabilities. |
| | User Logging intrinsics. | |
| | | |
-----------------------------------------------------------------------------------------------
Table C-1. User Logging Error Codes (Cont.)
-----------------------------------------------------------------------------------------------
| | | |
| Code | Meaning | Corrective Action |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 8 | Incorrect password was passed to a | The creator of the logid can obtain the |
| | User Logging intrinsic. | password by using the ;PASS option of |
| | | the :LISTLOG command. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 9 | An error occurred while writing to | Obtain the File System error from the |
| | the log file. The File System error | $STDLIST and take the appropriate |
| | message will be printed on $STDLIST. | action. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 12 | The system is out of disc space, the | Take the usual action for obtaining disc |
| | logging process cannot proceed. | space, then restart the logging process. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 13 | OPENLOG failed. The maximum number | Temporary solution: Wait for a user, |
| | of users that can access a User | who is accessing the logfile, to finish. |
| | Logging process at one time has been | |
| | reached. This number is configurable | |
| | at system startup only. | Long term solution: At the next system |
| | | startup, have the number of users that |
| | | can access a User Logging process |
| | | increased. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 14 | Invalid access to a log file | Each user wanting to access a User |
| | (security violation). The user, | Logging process, and its associated |
| | group, or account calling the | logfile, must have obtained access to it |
| | intrinsic does not match the user, | through a call to OPENLOG. |
| | group, or account for the log index | |
| | passed. | |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 15 | End-of-file on logfile (the logfile | :RENAME the logfile and :BUILD a new one |
| | is full and AUTO was not on to | with the old name, type :LOG logid,START |
| | automatically switch to a new | to restart the logging process. |
| | logfile). | |
| | | or |
| | | |
| | | :BUILD a new logfile with a new name, |
| | | use the :ALTLOG command to point the |
| | | logid to the new logfile, and use :LOG |
| | | logid, START to restart the logging |
| | | process. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 16 | The logid does not exist. | To see the logids that exist, use the |
| | | :LISTLOG command. To add a logid, use |
| | | the :GETLOG command. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 17 | Parameter (either itemnum or itemval) | Check the LOGINFO parameters, the |
| | missing for the LOGINFO intrinsic. | itemnum and itemval must occur in pairs. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 18 | Invalid item number passed to the | Refer to the MPE XL Intrinsics Reference |
| | LOGINFO itemnum parameter. | Manual (32650-90028) for a complete list |
| | | of valid item numbers that can be |
| | | returned to the itemnum parameter of the |
| | | LOGINFO intrinsic. |
| | | |
-----------------------------------------------------------------------------------------------