If it's in the doc apologies I couldn't find it.
Below is some test code:
* filename out "C:\Temp"; * change as desired ;
proc cport lib=sashelp file="%sysfunc(pathname(out))/testing.cpt";
select class cars fish shoes stocks;
run;
libname xpt xport "%sysfunc(pathname(out))/testing.xpt";
proc copy in=sashelp out=xpt;
select class cars fish shoes stocks;
run;
/*
Well that rules out using the xport engine.
In fairness, the 9.4 doc does say:
The XPORT engine supports a feature set that is compatible with SAS 6.
The XPORT engine cannot support SAS 9 features, such as long variable names.
Warning or error messages report limitations that are encountered during the transport operation.
For details about typical error messages and recovery actions,
see File library.member.DATA has too long a member name for the XPORT engine.
Curiousity/rhetorical questions:
Are there ANY installations still running SAS V6?
Does SAS even officially support V6?
If the answer is NO, should SAS clean up "bloat" in their software?
For example, isn't the installation of the xport engine just a waste of disk space in SAS 9.x?
*/
proc cimport lib=work file="%sysfunc(pathname(out))/testing.cpt";
* how do i get a listing of the contents without actually importing??? ;
* like i can do with tar, zip, 7-zip, rar, etc. ??? ;
run;
@ScottBass: The macro provided in this paper ( http://www.lexjansen.com/pharmasug/2009/ad/AD08.pdf ) may be what you're looking for.
As for you comments about whether they are still needed, yes, unless the US govt has changed its requirements and, secondly, definitely needed for those of us who have to access archived versions of historical files.
Art, CEO, AnalystFinder.com
p.s. I'm sure a number of mainframe folks are still using SAS6
Thanks @art297. It's good to know there's a hack available for functionality typically provided by similar software archiving/compression packages.
Thanks too for clarifying that V6 is still alive and well, and in production environments.
The link is broken.
I am looking at a Oracle DMW app Auto generated SAS code, it is trying to read contents of CPORT file using proc contents.
libname Source "/u04/dataloader/FILEWATCHER/FileWSASDev/AccentureFixitol";
option nofmterr;
proc contents data=Source.RAVE_ODM_20180727T095357_part1 out=Contents noprint;
run;
/*RAVE_ODM_20180727T095357_part1.CPORT is the cport file in the path passed in libname.*/
How ever this is not working, I did not find any documentation to read the contain of cport file.
I could really use some help here.
Thank you in advance.
There were some stray characters in the link. Reload the post's page and try it again.
Art, CEO, AnalystFinder.com
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!
Learn the difference between classical and Bayesian statistical approaches and see a few PROC examples to perform Bayesian analysis in this video.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.