Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!hplabs!ucbvax!YALE.ARPA!LEICHTER-JERRY From: LEICHTER-JERRY@YALE.ARPA Newsgroups: mod.computers.vax Subject: Re: DUMPER32 utility Message-ID: <8606131137.AA29514@ucbvax.Berkeley.EDU> Date: Fri, 13-Jun-86 07:38:22 EDT Article-I.D.: ucbvax.8606131137.AA29514 Posted: Fri Jun 13 07:38:22 1986 Date-Received: Sat, 14-Jun-86 15:54:53 EDT Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Organization: The ARPA Internet Lines: 23 Approved: info-vax@sri-kl.arpa [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 -------