Serious Problems
Always contact your local support representative if you have any of the following problems.
Serial Numbers
On UNIX, if following a system crash or, for some other reason, you need to restore the root file system, you must re-install your machine's serial number after restoring the /etc directory, otherwise Reality will not work.
On Windows, after reformatting, or replacing the C: drive, you must reinstall the system serial number.
Problems with One Terminal
Problems may occur on only one terminal. Examples are:
-
A terminal's process aborts.
-
A terminal's process hangs, that is, gets stuck at some point in its processing.
-
An abnormal display appears on a terminal.
Note
Do not enter any debugger commands on the problem terminal until you have called your local support representative to determine the best method for doing so.
If a terminal appears to have hung, you can use the realprof utility on another terminal to display the DataBasic stack for the problem terminal's reality process. This can tell you what process is running and what it is currently doing.
Reality on Windows Fails to Start
When Reality is installed on a host that is part of a Domain, a user-id Reality User is installed in the Domain User List. If the host is then moved, or made standalone, the Reality services will fail to start because they no longer have a default Reality User id to use. If this problem occurs, you will see the following message when attempting to start Reality from the command prompt:
Cannot attach to central message Q: No such file or directory <49009>: No message queue
Users logging in via Telnet or DDA will be unable to connect.
To solve this problem, run the command ntinstall from
within the Realman folder to create a new Reality User user-id either in
the new domain or locally as appropriate. Then restart the Reality services
with:
realserv -s
Note
If you have both domain
and local Reality User user-ids, the local user-id will be used. This can
prevent the use of networked SYS printers. If necessary, you can remove the local
Reality User
user-id by running ntinstall -r.
Aborts and Core Dumps
On UNIX databases, if a terminal's process aborts, the default behaviour is for a core dump to be generated on the host. On Windows, depending on the problem, a Dr Watson report may be generated or the user may see a message saying that the process has terminated. In both cases, the dump or report can be used by NEC Software Solutions to help diagnose the problem.
This behaviour can be changed by setting the REALDUMP host environment variable to the following values:
0 Abort into the system or DataBasic debugger. Do not generate a core dump or Dr Watson report.
1 Abort into the system or DataBasic debugger and generate a core dump or Dr Watson report.
2 Generate a core dump but do not enter the debugger (default) - this setting is recommended because it generates the most accurate core dump.
You can tell which debugger you have entered by the prompt:
rdb-> The System Debugger prompt.
* The DataBasic Debugger prompt.