Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!AI.AI.MIT.EDU!KFL
From: KFL@AI.AI.MIT.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: VAX C Printf problem.
Message-ID: <179126.870404.KFL@AI.AI.MIT.EDU>
Date: Sat, 4-Apr-87 15:14:10 EST
Article-I.D.: AI.179126.870404.KFL
Posted: Sat Apr  4 15:14:10 1987
Date-Received: Sun, 5-Apr-87 13:12:37 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 19
Approved: info-vax@sri-kl.arpa

This is because VMS is record oriented rather than character oriented.
There is frequent confusion between a newline appearing because of the
end of a record, and a newline appearing because the is a <CR><LF> in
the file at that point.  Different software deals with this differently.

A file can have NONE for CARRIAGECONTROL.  This means that only <CR><LF>
will cause a newline on a terminal or a printer.  You can covert your
logfile to that form, but that wouldn't fix the problem, because there
are no <CR><LF>s in the logfile.  LIST for CARRIAGECONTROL is the
default.  That means a newline is sent to the terminal or the printer
whenever there is a new record in the file.  This is probably the form
of your logfile.  Do DIRECTORY/FULL to check.

There are also STREAM files, which are character oriented like all text
files in Unix and MS/DOS.  This is how all text files should have been
on VMS, had the developers thought about it a little.  Unfortunately,
most software on VMS does not generate or accept STREAM files.

								...Keith