Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!ames!ucbcad!ucbvax!YMIR.BITNET!NED
From: NED@YMIR.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: Re: VAX C Printf problem.
Message-ID: <8704040956.AA13051@ucbvax.Berkeley.EDU>
Date: Fri, 3-Apr-87 12:14:00 EST
Article-I.D.: ucbvax.8704040956.AA13051
Posted: Fri Apr  3 12:14:00 1987
Date-Received: Sun, 5-Apr-87 10:18:14 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 17
Approved: info-vax@sri-kl.arpa

The "problem" is that SET HOST/LOG captures text essentially on a per-QIO
basis. Each of the printf calls you did seems to have resulted in a separate
QIO and hence a separate record in the log file. Note that log files are
written with no carriage control attributes and with explicit carriage
returns, line feeds and so forth in the records themselves, so the appearance
of the text is correct when you TYPE it out. This type of file (explicit
imbedded carriage control) is produced by several notorious VMS utilities,
notable RUNOFF.

I have used SET HOST/LOG to record sessions with DIALOG and other dialup
database services, and it can be a pain to munge the files produced into
something reasonable. The conversion program I use most of the time is TECO,
which for the most part does the right thing, reading a file with imbedded
carriage control and writing a "regular" file with carriage return carriage
control records. Long live TECO!

                                Ned Freed (ned@ymir.bitnet)