----- Original Message -----
From: "Bill Long" <[log in to unmask]>
Sent: Sunday, April 29, 2018 7:59 AM
>> On Apr 28, 2018, at 11:26 AM, Robin Vowels <[log in to unmask]> wrote:
>>
>> From: "Bill Long" <[log in to unmask]>
>> Sent: Friday, April 27, 2018 5:54 AM
>>
>>>> On Apr 26, 2018, at 7:57 AM, Jaromir Jakacki <[log in to unmask]> wrote:
>>>>
>>>> Thank you for replay,
>>>>
>>>> the main point is that my colleague made mistake and have calculated wrong record length
>>>> (calculated record length correctly, but did not use '-assume byterecl' flag). Then wrote data
>>>> without the flag. I would like to fix it using record length based on bytes. For example for
>>>> real*8 array with 10 elements:
>>>>
>>>> 1) his record length (SRL) is 10*8*4 = 320
>>>
>>> This just seems wrong. The I/O data are 80 bytes long.
>>
>> That's what he said.
>>
>> I’ve not heard of an implementation that uses a length unit of just 2 bits.
>>
>> 2 bits? Where does that come from?
>
>
> If the record length unit size is 2 bits, then an 80-byte record would be 320 “units” long.
Your conclusion is nonsensical. 10 × 8 × 4 = 320.
>>>> 2) based on bytes record length (DRL) should be 10*8=80
>>>>
>>>> How can i read data based on SRL and write is based on DRL.
>>>>
>>>> I tried to read it using recl=320 but it does not work (it saves data, but i am not able to
>>>> read it using different sofware).
>>>
>>> You can open the file for STEAM access and manually position the file at the right locations
>>> that have the data you are trying to read.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
|