HP3000-L Archives

January 2010, 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:
Reply To:
Date:
Sat, 9 Jan 2010 21:53:22 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (45 lines)
What does LISTF say?
I know with message files, and when you call to FCONTROL with 
controlcode=46, FFLEINFO returns the size of the data records, including 
the 4 byte header.

Maybe be something similar for CIR files as well?

Michael Anderson,
J3k Solutions




Brian Donaldson wrote:
> I have an interesting little situation going on that I hope someone out there
> in Lister Land will be able to shed some light upon.
>
> I have a Cobol program (PM program) that FOPEN's a circular file with the
> correct rec size (320 bytes).
>
> Further down in the logic prior to the FWRITE it calls FFILEINFO to get the 
> rec size prior to the FWRITE. FFILEINFO is giving me a rec size = 324 bytes.
>
> And so, the FWRITE fails with a 43 error code (boundary violation) which
> would be correct based upon the 324 bytes rec size.
>
> I am puzzled as to why FFILEINFO is returning 324 bytes as the rec size instead 
> of 320 bytes which was the rec size used in the FOPEN.
>
> Is the file system adding on another 4 bytes because this file is a 
> circular file and if so, why?
>
> Comments, suggestions appreciated as always.
>
> TIA,
> Brian Donaldson.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>   

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2