HP3000-L Archives

March 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Leonard S. Berkowitz" <[log in to unmask]>
Reply To:
[log in to unmask][log in to unmask], 10 Mar 2000 12:10:44 -0800258_us-ascii John,

At the colon prompt type:

:help file filecode

Regards
Paul Christidis

Comrades:

Is there a command or utility that will give me definitions of every (or most)
file codes?

thanks,
John Stephens58_10Mar200012:10:[log in to unmask]
Date:
Thu, 9 Mar 2000 12:26:52 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
One of our jobs, on a test system, blew up with a COBOL file status 39 when
dealing with a CM KSAM file

File's fixed attributes diffeer from program (39) record size (COBERR 648)

And then in the tombstone did indeed report a RECORD SIZE different from the
FD/01 in the COBOL program. The tombstone reported the RECORD SIZE incorrectly,
however (70 bytes when the file is actually 74 bytes, matching the FD/01). We
recompiled the program with $CONTROL MAP to validate the FD/01. We checked the
file equations, the access date and we were pointing to the correct file.

One suggestion was that the issue was the large quantity of deleted records in
the data file. A copy of this KSAM duo was copied from another machine, and the
job is now OK.

Can someone explain what happened here?

Thanks.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737 (eff. 2/15/2000)

ATOM RSS1 RSS2