Jaap [Dank u well voor uw antwoord] In the sas foundation world Regstry.files are related to sas session and can be repaired or copied : here in our institute, on a linux red hat server people are regularly replacing their sasuser in a x11 connection when they are blocked by a forgotten quote and due to the fact that the "interrupt button" of the session management induces a damaged sas profile mention at restart. Copying a model is a solution but inside the same system and bitness. About the transportation of the sas7bitm template itemstore under 64 bit the warning is saying "is not a template store! It will be ignored" after a ods path(prepend) note.templat(read) statement. BUT we know how to save them even it is a pitty that Sas Institute has not developped a single proc kit to save all the templates of a sasuser or personnal store. about the sas7bitm document itemstore i tried a list/levels=all; and a replay; on a 64bit version of sas of the file with this creation content on the 32 bits version libname note "d:\tabsas"; title ; footnote; ods document name=note.derndoc(write); ods graphics /width=17 cm; proc print data=Sashelp.steel(obs=2); run; title "Exportation de l'acier avec vline"; proc sgplot data=Sashelp.steel; vline date / response=steel markers markerattrs=(symbol=star) ; yaxis label="Fer/Metal" values=(2,3,4,5,6,7,8,9,10) ; xaxis label='Evolution en million de tonnes' values=(1936 to 1980 by 2) ; run; title "Exportation de l'acier avec series"; proc sgplot data=Sashelp.steel; series x=date y=steel /markers markerattrs=(symbol=circle) ; yaxis label="Fer/Metal" values=(2,3,4,5,6,7,8,9,10) grid ; xaxis label='Evolution en million de tonnes' ; run; ods document close; under 64 bits ods rtf file="d:\notes\test\docrtf.rtf" style=ocean; ods graphics/ width=10 cm; proc document name=note.derndoc; list/levels=all; replay ; run;quit; ods rtf close; the results is no error or warning but empty documents! Packages are working upon ods results/outputs and package templates are not templates in a package Conclusion : explore DOCUMENT only if you like it AND after being under 64bits or keep trace of all what you have done carefully under 32bits in code files. Finally but outside the ods scope you are refering in matter of catalog "Using SAS/connect is supporting both directions" My experience with sas connect is from sas windows client session to a linux server with sas. Have you tried or do you know some existing text showing how to establishing a sas connect session between 1) 2 pc with foundation one with sas 64bits and the other with sas 32bits 2) or between two version of sas on a same pc W7 64bits one 9.3.2 32 bits version and a 9.4.1 64bit version. What are the Windows and SAS prerequisites on the like 'server' pc(32 bits) in case 1) I need examples or reports about this manner of doing migration to evaluate the charge in comparison of proc cport or the cntlin= and cntlout= couple. TIA Andre
... View more
