Date: Thu, 14 Mar 1996 17:52:05 EET
Reply-To: Arjen Raateland <raateland@VYH.FI>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Arjen Raateland <raateland@VYH.FI>
Organization: National Board of Waters and the Environment
Subject: Re: Reading SAS dataset with JMP
In article <19960313.135004.910702.NETNEWS@AUVM.AMERICAN.EDU>, Thomas M Skinner
> Folsom, California
> March 13, 1996
> Sunny, breezy, near 70
> Pieter Knelissen wrote:
>>When we generate a SAS dataset on our VMS-machine, we cannot read it using
>>JMP under Windows. The VMS-machine is also used as a file server accessible
>>PC on which JMP runs. The network is Digital's Pathworks.
>>Can anyone help ?
> You can generate a transport library with either PROC CPORT, or through the
> engine option of the LIBNAME statement (Xport), which some folks find more
> convenient as it works without adding additional steps (this assumes your
> steps are constructed to serve the function of transport only... there is a
> performance hit for reusing these datasets locally.) Note that the file
> structure for the transport file is specific to your OS (see your system
> documentation aka "companion"), but as a binary, should be accessible from
> PC (are you running JMP for Windows?) via your file service facilities.
In order to be able to correctly read a transport file over the
network or, for that matter, copy it across so that it works at the
other side, you will have to make sure the transport file to be read
from the PC has the record attribute carriage_control NONE instead of
the default CARRIAGE_RETURN. You can do this in the LIBNAME statement
with the option CC=NONE, if I'm not mistaken.
My experience with this is from transporting SAS files across a
Pathworks network between VMS and Windows. I heard of the CC-option
only after I had implemented the use of the VMS CONVERT utility
program in my transport application.
When copying a transport file from the PC, I use the NFT utility's
copy command with the MRS:80 switch. After that I still have to
CONVERT to CARRIAGE_CONTROL=CARRIAGE_RETURN on the AXP machine.
Needless to say that this is all much too complicated for the average
user without some sort of program to do all the nitty-gritty stuff.
--... ...-- -.. . --- .... ..--- --.. .- --..
Arjen Raateland, SAS Support
Finnish Environment Agency