Table of Contents
Advertisement
Error Messages
Cannot start. Ending previous session, try again
Cause: The host system could not start a new emulation session, and is
ending the previous session.
Action: After the previous session has ended, try starting a new emulation
session. If that fails, try "emul700 -u <logical name>" to unlock the emulator
and cycle power, if needed.
Cannot start. Pod initialization failed
Cause: The host system could not start a new emulation session because it
could not initialize the emulator.
Action: Cycle power on the emulator; verify that there are no red lights on
the front of the emulator. You may need to run the Terminal Interface "pv"
command to verify that the emulator is functioning properly before starting a
new session.
Cannot unlock emulator; emulator in use by user: <USER NAME>
(10328)
Cause: The emulator is already in use by the named user.
Action: Current user must release the emulator.
Cannot unlock emulator; emulator not locked (10328)
Cause: You have issued a command to unlock an emulator that is not locked.
Action: The emulator is available now. You can start the interface.
Cannot unlock emulator; lock file missing
Cannot unlock emulator; semaphore missing (10328)
Cause: Lock semaphore missing.
Action: Verify existence and permissions of /usr/hp64000 directory. Cycle
emulator power and use emul700 -u <logical name>.
CMB execute; emulation trace started (1305)
Cause: This status message informs you that an emulation trace
measurement has started as a result of a CMB execute signal (as specified by
the specify trace command).
451
Advertisement
Table of Contents
