sys$startup:clue$startup.com cannot find DOSD

Post Reply

Topic author
vaxman65
Member
Posts: 7
Joined: Wed Apr 28, 2021 9:07 pm
Reputation: 0
Status: Offline

sys$startup:clue$startup.com cannot find DOSD

Post by vaxman65 » Thu May 11, 2023 1:43 pm

I set my dumpfile off the system disk with $ SET DUMP_OPTIONS/DEVICE=DKA100: and created it there. However, when sys$startup:clue$startup.com runs, it reports it cannot find it.

I turned on verification and it looks like it bails on the code to find the DOSD before it realizes it is on x86 and does not need the bit set in DUMPSTYLE.

Here is a log of the run with VERIFY turned on:

Code: Select all

$!      DOSD: check if bit 2 is set in DUMPSTYLE, and if true verify there
$!      is indeed a dumpfile on the device pointed to by the logical
$!      CLUE$DOSD_DEVICE. On x86 the info is in a data file in sys$manager:
$!
$ dump_file = ""
$ if ( f$int(f$getsyi("dumpstyle")) .and. 4 ) .eq. 0 then goto 500$
$500$:
$ if dump_file .eqs. ""
$ then
$   dump_file = f$search("sys$specific:[sysexe]sysdump.dmp")
$   if dump_file .eqs. ""
$   then
$     if f$getsyi("savedump") then dump_file = f$search("sys$specific:[sysexe]pagefile.sys")
$   endif
$ endif
$!
$ if dump_file .nes. ""
$ else
$   write sys$output "%CLUE-I-NODMP, unable to locate dumpfile or primary pagefile."
%CLUE-I-NODMP, unable to locate dumpfile or primary pagefile.
$ endif
As a test, I changed DUMPSTYLE in the active params from 128 to 132, set my process name to STARTUP and reran. The detached process then opened sys$manager:sys$dump_config.dat, found the DEVICE= line and ran properly.

User avatar

m_detommaso
Valued Contributor
Posts: 67
Joined: Thu Jun 06, 2019 6:57 am
Reputation: 0
Location: Brindisi (Italy)
Status: Offline
Contact:

Re: sys$startup:clue$startup.com cannot find DOSD

Post by m_detommaso » Thu May 11, 2023 2:01 pm


VSI OpenVMS x86-64 V9.2 Release Notes
Document Number: DO-RLNV92-01A
Publication Date: July 2022
Operating System and Version: VSI OpenVMS x86-64 V9.2



"2.1.22. System Crash Dumps

VSI OpenVMS x86-64 supports a single system crash dump of the compressed selective format. Bits 0 and 3 in the system parameter DUMPSTYLE must both be set. The value 9 is the default setting. VSI OpenVMS x86-64 system crash dumps are written using a minimal VMS environment called the dump kernel. All the files used by the dump kernel are included in the MemoryDisk, described in Section 2.1.14 of this document.

Dump Off System Disk

Crash dumps can be written to the system disk or to an alternate disk designated for the purpose. Dumps to the system disk are written to SYS$SYSDEVICE:[SYSn.SYSEXE]SYSDUMP.DMP, which can be created or extended using the SYSGEN utility.
Dumps to an alternate device can be set up as described in the following example that specifies DKA100: as the desired dump device.

Note : On VSI OpenVMS x86-64, the Dump off System Disk bit of the DUMPSTYLE system parameter is no longer required.

1. Create a dump file on DKA100: using the SYSGEN utility.

$ RUN SYS$SYSTEM:SYSGEN
SYSGEN> CREATE DKA100:[SYS0.SYSEXE]SYSDUMP.DMP /SIZE=200000
SYSGEN> EXIT
$

3. Enter the command:

$ SET DUMP_OPTIONS/DEVICE=DKA100:

You can confirm the setting using the SHOW DUMP_OPTIONS command.
The change is effective immediately, without requiring a reboot."



------

VSI OpenVMS x86-64 E9.2-1 Release Notes
Document Number: DO-RNE921-01A
Publication Date: March 2023
Operating System and Version: VSI OpenVMS x86-64 E9.2-1



"2.1.24. System Crash Dumps

VSI OpenVMS x86-64 system crash dumps are written using a minimal VMS environment called the Dump Kernel. All files used by the Dump Kernel are included in the MemoryDisk described in Section 2.1.15

New System Crash Dump – Interleaved Dumps

Starting in version E9.2-1, VSI OpenVMS x86-64 supports two system crash dump types: Compressed Selective Dump and Interleaved Dump.

A Compressed Selective Dump is written using only the primary CPU running in the Dump Kernel, while an Interleaved Dump makes use of the available secondary CPUs. If the dump device is a Solid State Disk, the dump can be written much faster, thus allowing the system to be rebooted sooner.

The DUMPSTYLE parameter specifies which dump type is being used. The default value for the parameter is 9 (Compressed Selective Dump). However, if the system has more than one CPU and the SYS$SYSTEM:MODPARAMS.DAT file does not include a value for the DUMPSTYLE parameter, then, when AUTOGEN runs, it will set the value of DUMPSTYLE to 128 (Interleaved Dump).

In OpenVMS x86-64, the only other pertinent bits in the DUMPSTYLE parameter are bit 1 (full console output: registers, stack, and system image layout) and bit 5 (only dump system memory, key processes, and key global pages). Either or both of these bits can be set in addition to the two base values (9 and 128). Bit 2 (dump off system disk) is no longer required."




/Maurizio
Last edited by m_detommaso on Thu May 11, 2023 2:13 pm, edited 1 time in total.


dgordon
VSI Expert
Active Contributor
Posts: 32
Joined: Tue May 09, 2023 7:57 am
Reputation: 1
Status: Offline

Re: sys$startup:clue$startup.com cannot find DOSD

Post by dgordon » Thu May 11, 2023 2:41 pm

Thanks for noticing and reporting this issue. Fortunately, this problem has already been reported to VSI. It turns out that there were multiple bugs hiding in that simple bug report. The two most important ones have been fixed for V9.2-1.

The first problem is the one you describe. If you have bit 2 disabled for x86 (a bit the x86 dump kernel ignores), then CLUE$STARTUP.COM will not find the DOSD device. You could probably figure out how to make a couple of small edits to CLUE$STARTUP to fix the oversight.

The second problem is that once the first problem is fixed, CLUE HISTORY does not work for interleaved dumps. The only workaround at this point is to not use interleaved dumps. Set DUMPSTYLE to 13 and ignore the message from the dump kernel complaining that deprecated bits are set. CLUE HISTORY will then work correctly. Once V9.2-1 is available, you can set DUMPSTYLE back to 128 for interleaved dumps.

If you are using interleaved dumps and still want a CLUE HISTORY report, log in and create one interactively by executing the following commands:
$ ANALYZE/CRASH dumpfile
$ READ/EXEC/NOLOG
$ CLUE/HISTORY/OVERRIDE
$ EXIT
You must do this interactively. The bug in SDA for interleaved dumps purges SDA commands pending in the command procedure, so writing a custom command procedure won't work.
Executive Vice President of InfoServer Engineering at VSI.

Post Reply