What is printing SYSDUMP.LIS to SYS$PRINT?

[Art Wiens]

I'm looking into the above minor "issue". Something is printing this file at system startup time. It has done this "forever" and the customer can vaguely remember that there was a problem a long time ago and possibly a SYSGEN parameter was changed to make this happen?

Searching around I found the DCL snippet that "everyone should have" in their SYSTARTUP_VMS.COM file which analyses the crash dump at startup time (and does just such a print), but this code is not present on this system.

Some params:

BUGCHECKFATAL 0
BUGREBOOT 1
DUMPBUG 1
DUMPSTYLE 2
SAVEDUMP 0

VAX/VMS v6.2, CHARON-VAX 4000-106, but it did this long before it was a CHARON-VAX - used to be a VAX 4000-105.

Any clues?

Thanks in advance,
Art

[Wim Van den Wyngaert]

The default for "set output" in ana/sys is sysdump.lis. May be search for that ? May be wildcards were used when printing ?

Fwiw

Wim

[Art Wiens]

I should rephrase one thing, the code IS present in the middle of a secondary startup procedure, but there is a clear:

$ GOTO SKIP_DUMP
...
$ SKIP_DUMP:

around it. I can't see how it would accidentaly fall inside the skipped code.

Art

[Hein van den Heuvel]

So there's not labels beyond the '$ GOTO SKIP_DUMP' and before the ANALYZE command?

(And there is no 'cute' redefintion of goto, or a 'backspaced' comment sign not visible with type or search? ! :-)

Most importantly... are you 100% sure that is the very SYSTARTUP_VMS.COM which is running? No confusion with SYS$COMMON vs SYS$SPECIFIC?

Cheers,
Hein.

[Dean McGorrill]

I suppose you could turn on verbose boot and
see if you can catch it

[John Gillings]

Art,

You could put an alarm ACE on the print queue to nail down the time and process that queues the job.

If it's from the STARTUP process, there's a simple way to stop the file from actually printing, and possibly help isolate the location - in SYLOGICALS.COM (or one of the other very early customisable procedures) add:

$ DEFINE SYS$PRINT NOQUEUE

(note this is a PROCESS logical name, so it will only affect PRINT commands within the startup process itself). Any print commands to SYS$PRINT will fail with:

%PRINT-F-CREJOB, error creating job
-JBC-E-NOSUCHQUE, no such queue