a issue happens when transform sas7bdat into xpt file, how to resolve?

[blueskyxyz]

    libname xptlib xport "&xpt\&_domain_..xpt";

    data &_domain_.(sortedby=_null_ label=&_label_.);
       set adam.&_domain_.;
    run;

    proc copy in=work out=xptlib memtype=data ;
        select &_domain_.;
    run;quit;

Have you met this situation?

there is no warning or error in the log window, I can open the xpt file using sas univeral viewer, but it doesn't work using windows10 sas.

here is the log, when open xpt file using windows10 sas: 

1 proc copy in=TMP1 out=WORK;
NOTE: Writing HTML Body file: sashtml.htm
2 run;

NOTE: Input library TMP1 is sequential.
NOTE: Copying TMP1.ADDV to WORK.ADDV (memtype=DATA).
NOTE: BUFSIZE is not cloned when copying across different engines.
System Option for BUFSIZE was used.
NOTE: There were 664 observations read from the data set TMP1.ADDV.
NOTE: The data set WORK.ADDV has 664 observations and 65 variables.
NOTE: PROCEDURE COPY used (Total process time):
real time 0.26 seconds
cpu time 0.15 seconds

[jimbarbour]

@blueskyxyz,

What are you seeing in your data window ("VIEWTABLE") in SAS?  It looks like (from the log) that everything worked.  Can you post a screen shot of what you are seeing?  Like this:

Jim

[blueskyxyz]

sample code:
libname out xport '....\class.xpt';

proc copy in=sashelp out=out memtype=data;
select class;
run;

[ballardw]

"doesn't work using windows10 sas" is pretty vague.

Are there errors in the log?: Post the code and log in a code box opened with the <> to maintain formatting of error messages.

No output? Post any log in a code box.

Unexpected output? Provide input data in the form of data step code pasted into a code box, the actual results and the expected results. Instructions here: https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-dat... will show how to turn an existing SAS data set into data step code that can be pasted into a forum code box using the <> icon or attached as text to show exactly what you have and that we can test code against.

Your log doesn't show any attempt to actually open or use the set that I can tell from your post.

[Kurt_Bremser]

"doesn't work" on its own without a clear description is totally unhelpful and stupid. Please give a clear description of what happened that did not meet your expectations.

From the log you posted, everything worked fine.

[blueskyxyz]

Could you mind to watch your words? Don't use foolish or stupid on others' post even you are knowledgeable on sas programming.