home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
extra
/
promit.bwr
< prev
next >
Wrap
Internet Message Format
|
1988-08-16
|
2KB
Date: Sat 12 Oct 85 18:23:58-EDT
From: D. M. Rosenblum <DR01%CMCCTE@TE.CC.CMU.EDU>
Subject: P/OS Kermit & Print Format Files
P/OS Kermit V1.0 apparently does not know how to send RMS-11 print format
files (i.e. files with VFC record format with two-byte headers, and print
format record attribute, so the fixed control area is a two-byte header
containing print information). I found to my dismay that when I tried to
upload such a file to a TOPS-20 using Kermit it immediately gave me an error
message about an unsupported entry in some field in some RMS control block
(maybe RAT in FAB, but I don't remember) and refused to transmit the file.
It wouldn't even throw away the print format information and just transmit the
variable length part! What I had to do to get around this was use RMSCNV (the
PRO/Tool Kit CONVERT command) with the /FIXED_CONTROL switch to convert the
file to an ordinary variable length record file and then edit it to change all
the formatting information into formfeeds or appropriate numbers of blank
lines and then use Kermit (this time successfully) to upload the file.
I hope that the next release of P/OS Kermit V1.0 will support print format
files by suitably interpreting the print format headers and converting them
into blank lines and formfeeds, as appropriate, when sending such files (just
like it supports Fortran carriage control files by interpreting the Fortran
carriage control characters and sending out files with these replaced by
ordinary ASCII printing characters).
------------------------------
Date: Thu, 22 May 86 09:15:10 EDT
From: rmcqueen (Robert C McQueen) @ sitvxb
Subject: P/OS Kermit does not work with P/OS 3.0
The Pro-3xx version of Kermit from Stevens doesn't work in version 3.0 of P/OS.
It worked in all of the field test versions of P/OS, but doesn't work in the
released version of P/OS 3.0. We are currently working on the problem, but I
can not give you any time frame as to when it will be fixed in that version.
Bob
------------------------------