Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!NTA-VAX.ARPA!steinar
From: steinar@NTA-VAX.ARPA (Steinar Haug RUNIT)
Newsgroups: mod.computers.vax
Subject: PSIPAD logging
Message-ID: <8701191245.AA00520@nta-vax.arpa>
Date: Mon, 19-Jan-87 12:41:54 EST
Article-I.D.: nta-vax.8701191245.AA00520
Posted: Mon Jan 19 12:41:54 1987
Date-Received: Tue, 20-Jan-87 04:17:46 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23
Approved: info-vax@sri-kl.arpa

>>When capturing data from the public data network, the LOG file
>>picks up characters that appear as "R>" when the file is typed
>>out afterwards. In a dump, these correspond to hex "00523E".
>>
>>Does anyone know what causes them, and how to get rid of them?
>>(Short of writing a filter program to remove them afterwards.)
>
>You can't get rid of them.  The T> and R> are inserted when you
>do a $ SET HOST/X29/LOG to indicate transmitted and received
>packets by the PSI software.  PSIPAD has no concept of CRLFs
>like RTPAD does, so it inserts the T> and R> sequences.  (Look
>for the T> at the top of your example).
>
>Thus, each packet you send is preceded in the log file by a T>
>and each packet received is indicated by R>.

You *can* get rid of them! On my system, $ SET HOST/X29/LOG does
not give T> and R>. The PAD command SET LOG_FILE <file> *does*,
unless told otherwise with the /NOSTAMP qualifier, ie. use
SET LOG_FILE /NOSTAMP <file> instead.

                                  Steinar Haug
                                  haug@nta-vax.arpa