ASAP 3.2 Messages Manual

HP NonStop Messages Manual Page 89 of 414
Effect. While attempting to reload domains at startup, ASAPX found an error in the
name of a domain. The domain is not restarted.
Recovery. Manually remove the domain in question. If more than one domain has
been corrupted:
1. Make sure that all of the application processes are running and that all of their
domains are registered, or shut down all application processes using ASAPX. If an
application process is left executing, one must be executing in each processor with
at least one registered domain. To verify this, run a FILEINFO command against
the ASAPX swap subvolume or subvolumes. Verify that all shared memory
segment files are open. These files are named Zasapid Cn where asap id is
the ASAP ID from the ASAPCONF file, and n is the CPU number. If one shared
memory segment file is open, they all must be open.
2. Stop ASAP using the ASAP SHUTDOWN command.
3. Enter the ASAPX CLEANUP DOMAINS command to purge the Domain table.
4. Restart ASAP with the ASAP START command. If the application processes
remained executing, ASAPX completely rebuilds the Domain table from shared
memory. If the applications were shut down, the Domain table is rebuilt over time
as they restart and register with ASAPX.
1808
Objectives load failed, domain: domain, Dmn#: domain number
Cause. ASAPX detected an error trying to load objectives for domain domain. To
determine the cause of this event, see the accompanying file-system error message.
Effect. The correct objectives are not loaded for the domain.
Recovery. Correct the file-system error and retry the operation.
1809
Registered process active: pname, Pin: pin
Cause. The application process pname was restarted before ASAPX after a processor
or system failure. ASAPX detected that it needed to rebuild the shared memory slot for
a domain but found the process that registered the domain was executing at the time.
Effect. ASAPX does not rebuild the shared memory slot for the domain because an
attempt to do so might cause MUTEX problems.
Recovery. First, stop the process in question. Second, restart ASAPX. Finally, restart
the process.