| 0 | No error for this intrinsic call. | None. |
| 1 | User requested NOWAIT mode and the logging process is busy. | Retry the intrinsic call. |
| 2 | Parameter out of bounds in logging intrinsic. For example, the address of data, for WRITELOG, and the length given will go beyond the top of the stack. | Check all parameters to be sure they are correct and addressed properly. |
| 3 | A request to open or write to a logging process that is not running. | Use the :SHOWLOGSTATUS command to 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 User Logging intrinsic. | The index parameter must be a number 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 user logging intrinsic. | For the WRITELOG intrinsic, valid mode 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 denied and the User Logging process was suspended (the User Logging process is stopping or attempting recovery from an exception condition, for example, a power failure). | The :SHOWLOGSTATUS command or the LOGINFO intrinsic will give the current state of the User Logging process. If the process is stopped, it must be restarted by the system supervisor before the user can open the file. |
| 7 | Illegal capability. The user must have LG or OP capabilities to use the User Logging intrinsics. | See your account or system manager to obtain the proper capabilities. |
| 8 | Incorrect password was passed to a User Logging intrinsic. | The creator of the logid can obtain the password by using the ;PASS option of the :LISTLOG command. |
| 9 | An error occurred while writing to the log file. The File System error message will be printed on $STDLIST. | Obtain the File System error from the $STDLIST and take the appropriate action. |
| 12 | The system is out of disc space, the logging process cannot proceed. | Take the usual action for obtaining disc space, then restart the logging process. |
| 13 | OPENLOG failed. The maximum number of users that can access a User Logging process at one time has been reached. This number is configurable at system startup only. | Temporary solution: Wait for a user, who is accessing the logfile, to finish. 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 (security violation). The user, group, or account calling the intrinsic does not match the user, group, or account for the log index passed. | Each user wanting to access a User Logging process, and its associated logfile, must have obtained access to it through a call to OPENLOG. |
| 15 | End-of-file on logfile (the logfile is full and AUTO was not on to automatically switch to a new logfile). | :RENAME the logfile and :BUILD a new one with the old name, type :LOG logid,START to restart the logging process. 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) missing for the LOGINFO intrinsic. | Check the LOGINFO parameters, the itemnum and itemval must occur in pairs. |
| 18 | Invalid item number passed to the LOGINFOitemnum parameter. | Refer to the MPE/iX Intrinsics Reference Manual (32650-90028) for a complete list of valid item numbers that can be returned to the itemnum parameter of the LOGINFO intrinsic. |
