> Timothe Litt wrote:
>> I may have missed it, but you'll get more help if you provide the OS that
>> you're running on, the file attributes (for DCL, dir/full and/or
>> dump/header), and a hex dump of the first block or two of the file.
> I'm running this in ITS, using the DECUUO TOPS-10 emulator.  So maybe
> it's not surprising if it doesn't work exactly right.  There aren't much
> in the way of file attributes.
>
> This is what the file looks like in Unix.  The linefeeds are converted
> to CRLF when transferred to ITS.
>
> 00000000  31 0a 31 09 20 59 4f 55  20 41 52 45 20 53 54 41  |1.1. YOU ARE STA|
> 00000010  4e 44 49 4e 47 20 41 54  20 54 48 45 20 45 4e 44  |NDING AT THE END|
> 00000020  20 4f 46 20 41 20 52 4f  41 44 20 42 45 46 4f 52  | OF A ROAD BEFOR|
> 00000030  45 20 41 20 53 4d 41 4c  4c 20 42 52 49 43 4b 0a  |E A SMALL BRICK.|
> 00000040  31 09 20 42 55 49 4c 44  49 4e 47 20 2e 20 41 52  |1. BUILDING . AR|
OK, so it's stream-crlf.  I was never much of an ITS user, and never
used FORTRAN there.  I don't think ITS had file attributes at the
filesystem level, so we don't have to worry about that level of
complication.

If a leading space (1H )  gets the data read correctly, the RTL thinks a
FORTRAN file is expected by the
user code, and is turning the <data>crlf into <sp>data.  This behavior
is is either explicit (an OPEN argument), or implicit (based on file
name, unit number, or device type).  Is the file extension .DAT?  that
may trigger this.

Is there an OPEN statement for that file?  If so, what does it include? 
If not, how is it connected to which LUN, and what's its full name (as
seen by a UUO)?

What fortran compiler/runtime?  DEC's F40?  FORTRAN-10?  Something else?

Later versions of F40 supported open (some earlier versions had CALL
OPEN(same args)).

You need the reference manual for whichever compiler/RTL you're using.

For FORTRAN-10, look for aa-n383b-tk ("TOPS-10/TOPS-20 FORTRAN Language
Reference Manual")

There is a bitsavers URL for that, but it's broken and seems broken on
the mirrors too:
http://bitsavers.org/pdf/dec/pdp10/TOPS10_softwareNotebooks/vol11/AA-N383B-TK_fortLangMan.pdf


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh

Reply via email to