LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (February 1996, week 4)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Wed, 28 Feb 1996 00:49:21 -0800
Reply-To:     mitchell <SA.MAY@FORSYTHE.STANFORD.EDU>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         mitchell <SA.MAY@FORSYTHE.STANFORD.EDU>
Organization: Stanford University
Subject:      question about XCOPY and CPORT

This question will fall into the "this must have been asked a billion times already..."

I'm going to be porting several SAS data sets from MVS to BOTH a SUN Unix system and an OS/2 system.

Normally, I'd use XCOPY to convert my data sets to transport formats. But, CPORT seems to have replaced XCOPY. But the syntax for CPORT seems too sparse - that is, I can't figure out how to tell CPORT where to stuff the transport data set.

I know a lot about the MVS and OS/2 data formats, but SUN format could be a surprise (althought it shouldn't be). Will it?

The obvious questions seem to be is XCOPY history and should I really be using CPORT. Or it doesn't matter where I'm sending the transport data set - is a transport data set is a transport data set?

What would be really nice is if someone would send me an example of PROC CPORT using a disk SAS data set and making a disk transport data set.

Thanks in advance.

Mitchell Yee sa.may@forsythe.stanford.edu


Back to: Top of message | Previous page | Main SAS-L page