macmillan%wnre.aecl.cdn%ubc.CSNET@CSNET-RELAY.ARPA.UUCP (06/10/86)
Does anyone have a working copy of the DUMPER32 utility to read TOPS-10
backup tapes on a VMS system? An EXE file would be appreciated. The
version received from the DEC integration tools clearinghouse produces
this message:
$ RUN DUMPER32
%CLI-F-SYNTAX, error parsing 'BLOCKING_FACTOR'
-CLI-E-ENTNF, specified entity not found in command tables
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
7FFA936A 7FFA936A
7FFA9170 7FFA9170
7FFA8C9D 7FFA8C9D
00007FAA 00007FAA
PARSER ELEMENT_IS_PRESENT 1536 00000013 00007E95
PARSER PAR$PARSE_QUALIFIERS 907 00000014 00007B46
DUMPER DUMPER_MAIN 1182 00000040 00004640
$
John MacMillan
Atomic Energy of Canada
Whiteshell Nuclear research establishment
Pinawa, Manitoba, Canada
R0E 1L0
(204) 753-2311 ext. 2539rmcqueen@sitvxb.BITNET (Robert C McQueen) (06/11/86)
The DUMPER32 utility on the DEC integration tools clearinghouse produces the error because you have to define the command for the utility first. You can define the command via the DCL command SET COMMAND. The .CLD file for DUMPER32 should be included on the tape. Robert McQueen Stevens Institute of Technology BITNET: RMCQUEEN@SITVXA ARPA: RMCQUEEN%SITVXA.BITNET@WISCVM.WISC.EDU
LEICHTER-JERRY@YALE.ARPA (06/13/86)
[The author of the original message reported the following error while
trying to run DUMPER32 from the DEC Integration Tools Clearinghouse.]
$ RUN DUMPER32
%CLI-F-SYNTAX, error parsing 'BLOCKING_FACTOR'
-CLI-E-ENTNF, specified entity not found in command tables
%TRACE-F-TRACEBACK, symbolic stack dump follows
....
This error message most likely means that DUMPER32 expects to be started up
via a DCL command line, and get its parameters from that line. If you simply
RUN the program, the DCL command line buffer contains nothing meaningful, and
the program gets back garbage.
Somewhere in your distribution, there should be a file called something like
DUMPER32.CLD. This is the command language definition for DUMPER32; you
should do a SET COMMAND DUMPER32 (or whatever the name is). Then use the
DCL command so defined to start up DUMPER32. There should be documentation
somewhere on the kit to tell you what the command line should look like -
perhaps a help file is included. Failing that, stare at the .CLD a bit; they
are usually pretty easy to read.
-- Jerry
-------