Date:         Thu, 1 Feb 1996 20:25:00 -0700
Reply-To:     John O'Callaghan <jocallag@NYX.CS.DU.EDU>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         John O'Callaghan <jocallag@NYX.CS.DU.EDU>
Organization: Nyx.net, free public access to the Internet
Subject:      Re: KERMIT xport OS/2 to VMS

This *could* be an OS/2 problem. Check the date of the COM.SYS file in
your \OS2\BOOT directory. It should be 2/9/95 or 5/30/95 , preferably the
latter. If its dated in 1994 (probably 10/3/94) then it may not be
working correctly. There was a problem with this version of COM.SYS. For
example, I transfer alot of data between my OS/2 machine and a remote VMS
machine via serial link and Kermit for OS/2. This *never* worked for me
until I found out about the broken COM.SYS file. Check around on various
ftp archives for the fix. Its available either via the fixpacks, or I
think there was a specific fix just for this. If you just can't find it,
email me and I'll send it to you (if indeed you think it could be the
problem).
 
Good luck,
John
 
 
USA::JHK27056 (JHK27056%USA.decnet@USAV01.GLAXO.COM) wrote:
: All,
 
: I need advice on a problem I am having with a transport library
: created with PROC DATASETS.  I am creating the transport file
: using OS/2 SAS and then sending it to a VAX using KERMIT.
 
: I used a binary transfer with kermit.  I CAN use the file if I don't
: send it to the VAX.  So I know that my transfer is breaking it.
 
: Does anyone know of any SUGI papers about this topic.  I have the
: tech report about transporting files, but remember a SUGI paper
: from a few years ago that was helpful, but I don't remember where.
 
: Thanks in advance,
 
: John King