Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: error messages get

Original Message
Name: leng
Date: November 18, 2007 at 21:54:45 Pacific
Subject: error messages get
OS: alpha vms
CPU/Ram: 1gb
Model/Manufacturer: hp
Comment:
Hi guys, i am having problem with getting the error messages, may i know what is the problem here?

DCL-I-SUPERSEDE, previous value of CAL002-DEBUGGING-ON has been superseded
%DIRECT-W-NOFILES, no files found
%DCL-W-INSFPRM, missing command parameters - supply all required parameters
$STATUS == "%X00038048"
19-NOV-2007 11:31:59
%DCL-I-SUPERSEDE, previous value of INPUT_FILE has been superseded
OPENING FILE TO GET DATA................
%COB-F-RECORD_LONG, record too long to match attributes of FILE.DAT;129
-RMS-W-RTB, 170 byte record too large for user's buffer
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
DEC$COBRTL


Report Offensive Message For Removal

Response Number 1
Name: SKStewart
Date: November 19, 2007 at 09:11:10 Pacific
Subject: error messages get
Reply: (edit)
leng,

Probably, these messages are being generated from inside a command file, or script. It is difficult to determine the true problem without knowing the commands in the command file. Try entering the OpenVMS command "SET VERIFY" before executing this command file again. That should list the commands in the file as they are executed, and you can then see the exact command that generated each error message. When that is done, enter "SET NOVERIFY" to return to normal.

You can also enter the command "HELP/MESSAGE" to see documentation on error messages.

As for what the individual messages mean:

"DCL-I-SUPERSEDE" means that a logical name was redefined. This is only an informational message ("-I-") and is not an error.

"DIRECT-W-NOFILES" means a DIRECTORY command did not find any files that matched the name entered.

"DCL-W-INSFPRM" means an OpenVMS command was entered that could not be executed because it did not have all the required parameters. (Perhaps one should have been a file name found by the previous DIRECTORY command? Or perhaps you are supposed to enter a parameter when you execute the command file?)

"COB-F-RECORD_LONG" I'm not familiar with, but it looks like a COBOL run-time library message that the program is writing to a file that is defined to have a maximum record length that is too short for the write.

"RMS-W-RTB" means "Record Too Big"; the file system (RMS) is apparently repeating the COBOL error message.

"TRACE-F-TRACEBACK" means that in response to a fatal error, the system is printing some debugging information.

So, as a tentative guess, the command file first attempted to find a file that matched some general name and failed. The command file did not abort (as it should have); instead it kept running and ran some command with a blank file name. That command started a COBOL program that is supposed to write information to the file. Since the file name was not entered, the program (or the command file) created a default file ("FILE.DAT"), but this file was created with the wrong record length, so the program could not write to it. By the way the ";129" means this is the 129th copy of FILE.DAT, so perhaps this problem has happened 129 times.

As I said, that was speculation, but perhaps it will give you an idea of what to look for.

Good luck


Report Offensive Follow Up For Removal

Response Number 2
Name: Bob Gezelter
Date: November 19, 2007 at 19:05:21 Pacific
Subject: error messages get
Reply: (edit)
leng,

I would more or less concur with SKStewart. Without the context (and the most likely locally written command files), it is difficult, if not impossible to be more specific about the detailed problem and how to correct it.

- Bob Gezelter, http://www.rlgsc.com


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: error messages get

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC