Re: problem w/READ INTO in COBOL/VSE?

Alistair,
I *think* that what you are saying isn't quite right. As far as I know all
IBM COBOL's do whatever it takes to get the code to work in a
"standard-conforming" manner which means that the record area SHOULD contain the
same data as the WS area. The only exception to this (that I can think of) is
something like:

FD File1.
01 Alpha1 Pic XXXXX.

..WS

01 AlphaEd-1 Pic XX/XXBX.
...
Read File1 into AlphaEd-1.

In that case, I think the WS version will contain an "edited" version of the FD
data. I don't think this is exactly what Frank was talking about, but if so,
then the two data areas will NOT match.

--
Bill Klein
wmklein <at> ix.netcom.com
"Alistair" <alistair@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1162583712.977012.277610@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Frank Swarbrick wrote:
The following was posted by Michael Rosinger on the vse-l listserv. Any
thoughts?

Michael Rosinger<mrosinger@xxxxxxxxx> 11/03/06 7:27 AM >>>
List,

I am writing a simple COBOL/VSE program where I am reading a SD file and
processing it. I am using the READ INTO option. According to the manual (and

all my years of experience) the BOTH the record area AND the target of the
INTO clause are supposed to be populated with the contents of the record (as

long as the READ was successful).

Well, it's not working that way. I added DISPLAYs of both areas immediately

after the READ and the W-S area (target of INTO) is populated but the file
area for the record is not!


The FD in the Cobol deck will translate to a GET command addressing a
specified record area (the one defined in working storage by the
plaintiff) into which the program places the record (according to the
DCB used). The record area within the datablock will not be available
to the program. Hence, you can view the working storage record but not
the whole of the block of data.



.