Checking system generation errors, Checking workstation error log files, Checking pathway errors – HP Integrity NonStop H-Series User Manual
Page 182: Volume management troubleshooting, Alternate system volume troubleshooting
For a spooler location, use the format:
\system.$collector.#location
For a description of EMS messages related to DSM/SCM, see the DSM/SCM Messages Manual.
Checking System Generation Errors
If a problem occurs during system generation, the errors are written to the system generation output
file. The location of this file for each target is designated in the system generation defaults (see
).
Checking Workstation Error Log Files
You can check the error log files that reside in the same directory as ZDSM.EXE (or ZDSMSCM.EXE),
such as the CIERROR.LOG, which is the error log file for CONFGINFO
NOTE:
For NonStop Software Essentials client troubleshooting, HP SIM debugging with trace
can be used (see
“Running Traces on the NonStop Software Essentials Client Component”
).
Checking Pathway Errors
Check for PATHWAY errors that are logged but not displayed to the screen. The $YPHI process
logs Pathway messages to $vol.PATHSCM.PATHLOG, on the volume where ZDSMSCM resides.
To examine the log, use the FUP COPY command to copy the file to another file or spooler location
with the SHARE option if $YPHI is still running. For more information on the FUP COPY command,
see the File Utility Program (FUP) Reference Manual.
Volume Management Troubleshooting
Alternate System Volume Troubleshooting
When you create multiple logical targets, or when you are running out of space on the current
$SYSTEM, you can create an alternate system volume for new SYSnn subvolumes. When you
create an alternate system volume:
•
$SYSTEM must be the permanent name, not the alternate name, for the alternate volume to
be loadable.
•
If you load the system that is currently running on a disk whose primary and alternate volume
names are the same (that is, $SYSTEM) on a disk having different primary and alternate
volume names (that is, $SYSTEM and $ALTNAME respectively), you cannot see the $SYSTEM
($SYSTEM) disk. Instead, change the alternate name of the $SYSTEM disk from $SYSTEM to
something else. and load the system on $SYSTEM ($ALTNAME). Then the disk comes up as
its alternate name.
•
To perform a system load from alternate system volumes (that is, use multiple logical targets),
the ZDSMSCM subvolume must be located on a volume other than $SYSTEM or any alternate
system volume.
•
After you rename a primary or alternate volume:
1.
Verify the database.
2.
Receive the snapshot before carrying out any other DSM/SCM activity.
•
After you rename an archive volume or a scratch volume:
182
Troubleshooting