Date:         Fri, 15 Mar 1996 16:32:08 -0800
Reply-To:     Paul OldenKamp <oldenkmp@REDWOOD.RT.CS.BOEING.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Paul OldenKamp <oldenkmp@REDWOOD.RT.CS.BOEING.COM>
Organization: BCAG SAS Support
Subject:      Re[2]: VMS to JMP: cport? (NOT!)  NOT! HUH?
Comments: To: Thomas M Skinner <Thomas_M_Skinner@CCM.FM.INTEL.COM>

Thomas M Skinner wrote:
...
> At any rate...this means that JMP, when it refers to a transport library means a
> V5 transport library!  (I guess maybe its documented somewhere, but who reads
> manuals these days.)
> ...
 
I was just about to post a note about what I remembered from my
experience with transport datasets and the first version of JMP on
the Mac 2-3 years ago when Tom's last post arrived.  I recall that
a member of our group got an evaluation copy of JMP and asked me to
transfer some data that we had been working on from UNIX to JMP.
I looked up the formats JMP could import and went off to make the
'transport' dataset.  I did a cport!!  After using ftp to move it to
the Mac I encountered the same errors Tom did.  I tried it all again
on the chance that I had created a corrupted file.  I then looked into
ftp and tried both binary and ASCII modes and some other options.
Then I created a file on the PC and copied it to a floppy so I could
aviod ftp altogether.  Along the way I carefully RTFM'd all the JMP
and relavant SAS documentation I could and I don't think you will find
anything about the distinction between xport and cport transport
datasets in the docs, Tom.  Finally I called SI and got the problem
solved.
 
I believe that the Mac version of SAS does have a JMP engine and I
am surprised that it isn't in at least the 'Orlando' release for
Windows. (Nobody at SUGI was calling 6.12 the 'Chicago' release as
far as I could tell.)
 
Paul OldenKamp, Boeing Company, Seattle, WA, USA