Re: sequential file formats

Can you tell us WHY you want this information? Almost (possibly all) vendors
provide documentation on their OWN 'file structures" (and often they also
include OPTIONS for file types). As others have pointed out on (IBM - not all -
mainframes) the "RDW" (record descriptor word) ONLY appears for variable length
(RECFM=V) (or possibly spanned?) records. For fixed length files this doesn't
exist. For BLOCKED files (again IBM mainframe) there is also a 4-byte "block
descriptor word" before each block of records. As far as "print" output goes,
on IBM mainframes, you also need to check out the ADV compiler option and there
are different syntax options that produce RECFM=FA vs RECFM=FM (ASA characters
vs Machine characters)

On all (most?) environments where Micro Focus provides a compiler, there are
bunches and BUNCHES of things that can impact this, for example
- the RDW compiler directive "emulates" IBM mainframe RDW support
- RECORD SEQUENTIAL files are stored very differently from LINE SEQUENTIAL
files (either source code or directives can impact this) - and fixed vs variable
impacts this as well.

"traditionally" most Windows (and DOS? and OS/2?) compilers use "CR/LF" to
terminate "line sequential" files - while they ONLY use "LF" (as I recall) for
Unix and Linux systems. How they handle "AFTER/BEFORE ADVANCING" (and the
older POSITIONING) and Report-Writer type files may also vary.

Again, tell us what you REALLY want to know and we may be able to give you
better information. If this is just a case of "I'm curious" then about your
SPECIFIC code example, then some people may be able to run it - but I don't
know.

P.S. You may want to compile your program with a compiler that has ANSI or FIPS
"flagging" available (which I don't think Open-COBOL does) to at least get a
"Standard conforming" source code. Without checking in detail, I think your
example (in another post) ignores:
A-/B-margin
Assign to shouldn't be a literal
no paragraph names
etc

You have
organization is relative sequential
record key is big-record.

which means that this is a RELATIVE file with access sequential - which is NOT
what is "usually" meant be "sequential file" - but instead what is meant by a
"relative file". (On an IBM mainframe, this would need to be pointing to a RRDS
VSAM file and NOT to a QSAM file). SEQUENTIAL files do not have "keys".
"Keyed" files have (usually VERY different structures. See for example the
Micro Focus INDXFORMAT - or something like that - I didn't check) directive)

--
Bill Klein
wmklein <at> ix.netcom.com
"theador" <Theador@xxxxxxxxx> wrote in message
news:1122264295.228797.240710@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I have noticed that every compiler/op sys seems to create a different
> format for sequential files. for instance, a COBOL program on the
> mainframe will create a sequential file with a four byte header that
> indicates length. On microfocus on AIX, a COBOL program will create a
> similar file but the with a special record as the first record that has
> some additional information.
>
> Does anyone know of a comprehensive list of all the different formats
> that may be out there?
>
> I will post small sample program that will create a two record
> sequential file in hopes that some of you will run the program and
> report back the format of the file that is produced. A hex dump as a
> post would be great. if you can not hex dump on your selected
> operating system, then email the output to theador@@@@gmail and I will
> hex dump the file and post it.
>
> Hopefully we can cover these combinations:
> Fujitsu on UNIX
> Fujitsu on WIndows
> IBM on AIX
> IBM on z/OS
> MicroFocus on UNIX
> MicroFocus on WIndows
> AccuCOBOL
> OpenCOBOL
>
> Thanks to those who can help in this experiment,
> Theador.
>


.

Relevant Pages

  • Re: Micro Focus and "dialects"
    ... This following is my response speaking primarily from an IBM mainframe ... COBOL dialects and standards through a number of compiler options and ... Within each choice (eg. Enterprise COBOL ... > directives do impact a FEW syntax/semantic issues. ...
    (comp.lang.cobol)
  • Re: COBOL Compiler for Windows
    ... rebadged Micro Focus compiler. ... to run TSO/SPF on your mainframe. ... Or maybe he wants a mainframe emulation environment, ... Why would a small developer pay several thousand for a .NET COBOL ...
    (comp.lang.cobol)
  • Re: Non-Standard Mainframe Language?
    ... the mainframe. ... Dave Pitts had a port of GCC available for USS ... make a later version of MVS available on a "Personal use basis" then folks ... For most people, there is a free compiler called "gcc" available, ...
    (bit.listserv.ibm-main)
  • Re: OO in Batch (Was: Program ID)
    ... compiler, but the free version was pretty well limited to the Windows ... COBOL uder Linux on the Mainframe to any signfigant extent, and, from ... reason mainframes are viewed with suspicion and irritation these days. ...
    (comp.lang.cobol)
  • Re: sequential file formats
    ... not a COBOL expert and I was compiling on a substandard compiler ... a commercial COBOL compiler. ... data to test routines that convert sequential files between the various ...
    (comp.lang.cobol)