[Info-vax] wrong file format

[Jan-Erik Söderholm]

Den 2020-12-23 kl. 13:01, skrev Henry Crun:
> On 23/12/2020 11:44, Phillip Helbig (undress to reply) wrote:
>> In article <rru1jb$gnq$2 at dont-email.me>,
>> =?UTF-8?Q?Jan-Erik_S=c3=b6derholm?= <jan-erik.soderholm at telia.com>
>> writes:
>>
>>> Trying to SET FILE/ATTR to anything that does not match the
>>> actual file content will usually give weird results.
>>
>> Right.
>>
>>> EDT tries to read the file according to the file attribs, not
>>> according to what the file actually contains.
>>
>> Right.
>>
>>> What are the "standard SET FILE/ATTR incarnations"? A secret?
>>
>> Almost always, SET FILE/ATTR=RFM:<whatever> does the trick.
>>
>>> You might try a DUMP and see how the records/lines actually are
>>> terminated and set the file attribs accordingly.
>>
>> Yes, if a simple fix doesn't work, I'll have to dig deeper.
>>
>>> I'm sure that you are aware that SET FILE/ATTR of course does not
>>> change any of the content of the file, right?
>>
>> Right.
>>
>>> B.t.w., what does a "damaged" file mean here? Dropped on the floor?
>>> Is it an original file foreign to VMS?
>>
>>  From VMS to VMS via the internet, but not a standard problem one
>> encounters in such situations.  :-
>
> I have solved similar problems using the TPU LEARN and REPEAT commands
> (om files of several hundred thousand lines...)
> 

Well, *IF* it is the actuall *content* that is "wrong". If not, that
is not the right solution. Why mess with the content if it is OK?

But if there is an issue with the content, that can probably be fixed
with a short DCL or Python script also.