https://communities.sas.com/t5/SAS-Procedures/The-code-and-error-message-regarding-to-import-transport-file/m-p/26359#M6014 For the future, this type of post is more suitable for the forum named "SAS Macro Facility, Data Step and SAS Language Elements", rather than posting in the very first forum in the list.<BR /> <BR /> Though you have not shared info at all about what you are attempting to accomplish (from-environment, to-environment, SAS version, to start), it's somewat clear that you are attempting to copy an XPORT format SAS dataset.<BR /> <BR /> So, from the diagnostic and knowing SAS naming restrictions, I would say that your problem source is that a SAS data library member cannot have an imbedded blank character.<BR /> <BR /> Suggest you renaming the XPORT format file and at least replace the "blank" with an underscore. You will also want to ensure that the file has been transfered in binary-format, as well.<BR /> <BR /> Scott Barry<BR /> SBBWorks, Inc.<BR /> <BR /> <BR /> Moving and Accessing SAS Files between Operating Environments<BR /> <A href="http://support.sas.com/documentation/cdl/en/movefile/59598/HTML/default/moveacc.htm" target="_blank">http://support.sas.com/documentation/cdl/en/movefile/59598/HTML/default/moveacc.htm</A> Sun, 06 Dec 2009 16:26:21 GMT sbb 2009-12-06T16:26:21Z https://communities.sas.com/t5/SAS-Procedures/The-code-and-error-message-regarding-to-import-transport-file/m-p/26358#M6013 The import code:<BR /> <BR /> libname myin xport "C:\project\temp\peter\edc\ODI 1_0.xpt";<BR /> libname xptout 'C:\project\temp\peter\edc\';<BR /> <BR /> proc copy in=myin out=xptout MEMTYPE=DATA;<BR /> run;<BR /> <BR /> The log file with error:<BR /> NOTE: Input library MYIN is sequential.<BR /> NOTE: Copying MYIN.ODI 1_0 to XPTOUT.ODI 1_0 (memtype=DATA).<BR /> ERROR: The value ODI 1_0 is not a valid SAS name.<BR /> ERROR: File XPTOUT.'ODI 1_0'n.DATA has not been saved because copy could not be completed.<BR /> NOTE: Statements not processed because of errors noted above.<BR /> NOTE: PROCEDURE COPY used (Total process time):<BR /> real time 0.00 seconds<BR /> cpu time 0.00 seconds<BR /> <BR /> NOTE: The SAS System stopped processing this step because of errors. Sun, 06 Dec 2009 01:44:46 GMT https://communities.sas.com/t5/SAS-Procedures/The-code-and-error-message-regarding-to-import-transport-file/m-p/26358#M6013 deleted_user 2009-12-06T01:44:46Z https://communities.sas.com/t5/SAS-Procedures/The-code-and-error-message-regarding-to-import-transport-file/m-p/26359#M6014 For the future, this type of post is more suitable for the forum named "SAS Macro Facility, Data Step and SAS Language Elements", rather than posting in the very first forum in the list.<BR /> <BR /> Though you have not shared info at all about what you are attempting to accomplish (from-environment, to-environment, SAS version, to start), it's somewat clear that you are attempting to copy an XPORT format SAS dataset.<BR /> <BR /> So, from the diagnostic and knowing SAS naming restrictions, I would say that your problem source is that a SAS data library member cannot have an imbedded blank character.<BR /> <BR /> Suggest you renaming the XPORT format file and at least replace the "blank" with an underscore. You will also want to ensure that the file has been transfered in binary-format, as well.<BR /> <BR /> Scott Barry<BR /> SBBWorks, Inc.<BR /> <BR /> <BR /> Moving and Accessing SAS Files between Operating Environments<BR /> <A href="http://support.sas.com/documentation/cdl/en/movefile/59598/HTML/default/moveacc.htm" target="_blank">http://support.sas.com/documentation/cdl/en/movefile/59598/HTML/default/moveacc.htm</A> Sun, 06 Dec 2009 16:26:21 GMT https://communities.sas.com/t5/SAS-Procedures/The-code-and-error-message-regarding-to-import-transport-file/m-p/26359#M6014 sbb 2009-12-06T16:26:21Z