I did not see until today a discuss about this topic
from version 9.2...we are using modified templates in ods
and in ods graphic and gtl
Can anybody clearly announce the rules in matter of change of system platform ?
for example
sas linux 32b to sas linux 64 b 9.4.1
sas windows 9.3.2 32b to sas windows 9.4.0 64b
Is cport working on sas7bitm files? If yes, how?
Are we really obliged to save template by template to a text file
in order to reinject our modified creation in a new version of SAS?
TIA
Andre
You are doing a 32-64 conversion. There is lot being referenced to "proc migrate".
When you are carefully reading that you will find that procedure doing the work will be probably SAS/connect . That is the moment your are needed to setup a SLIBREF definiton.
The other procedure being used is Cport-Cimport. SAS/connect can be used when you need to operate them both (upgrading/downgrading).
CPORT/CIMPORT only when you have a newer version at the destination and not want to use something in an older SAS environment.
You need to change all interfaces SAS is using also in their bitness. This will be more a challenge at Windows (MS-Office ODBC etc) than at Linux.
The sasbitm files are one of a special kind not covered by the copy/convert routines Cport /Connect. They are used for the Template but also as the SAS-registry.
These are release version machine dependent and is not a good idea to have the old versions binary copied. Same reason as you should not do that with Windows-registry.
The Template should be easily being recreated. You can get easily listed all definitions. The original source should be archived somewhere.
SAS-registry should be modified when needed and being documented why you did that.
You are doing a 32-64 conversion. There is lot being referenced to "proc migrate".
When you are carefully reading that you will find that procedure doing the work will be probably SAS/connect . That is the moment your are needed to setup a SLIBREF definiton.
The other procedure being used is Cport-Cimport. SAS/connect can be used when you need to operate them both (upgrading/downgrading).
CPORT/CIMPORT only when you have a newer version at the destination and not want to use something in an older SAS environment.
You need to change all interfaces SAS is using also in their bitness. This will be more a challenge at Windows (MS-Office ODBC etc) than at Linux.
The sasbitm files are one of a special kind not covered by the copy/convert routines Cport /Connect. They are used for the Template but also as the SAS-registry.
These are release version machine dependent and is not a good idea to have the old versions binary copied. Same reason as you should not do that with Windows-registry.
The Template should be easily being recreated. You can get easily listed all definitions. The original source should be archived somewhere.
SAS-registry should be modified when needed and being documented why you did that.
User customization of the SAS Registry can be captured with
PROC REGISTRY EXPORT="myreg&sysdate.-&sysvlong..txt";
RUN;
and appropriate parts recycled on the destination SAS system with
PROC registry IMPORT = 'my chosen registry bits.txt';
RUN;
So there are only individual solutions for templates.
no solution like the kmf file solution for keyboard macros
I will see if i can build a macro to process the text migration of the template.sas7bitm of the sasuser.
Andre
Don't miss out on SAS Innovate - Register now for the FREE Livestream!
Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.