Hi,
I created a secure macro catalog on a 64 bit Windows OS. When the same catalog is used on a 32 bit Windows OS, it gives
ERROR: File xxxxxx was created on a different operating system.
How do we create a catalog that works across all operating systems. Or otherwise is it possible to create a 32bit version of the catalog on a 64 bit OS?
Thanks in advance.
Vineet
No, and no. Catalogs are OS- and bitness-specific. Recreate from code in each environment.
Then you need to set up a 32 bit environment for migrating the catalogs, or have the client migrate to 64 bit.
Or you have to re-examine the reasons for keeping your code secret.
It is very important for us not to share the proprietary code with the client.
Whereas, CPORT doesn't work, it gives following message:
11 proc cport library=tmp1 file=trans;
12 run;
NOTE: PROC CPORT begins to transport catalog TMP1.SASMACR
NOTE: The catalog has 17 entries and its maximum logical record length is 3604.
WARNING: Entry type MACRO not supported by CPORT.
WARNING: Entry type MACRO not supported by CPORT.
I'm sorry I miss understood you question. CPORT is for FORMAT catalogs migration. You may need to save the original source code and later compile it.
@vineet7878_gmail_com wrote:
It is very important for us not to share the proprietary code with the client.
Why don't trust your client?
@data_null__ wrote:
@vineet7878_gmail_com wrote:
It is very important for us not to share the proprietary code with the client.
Why don't trust your client?
and therefor why should the client trust you?
@vineet7878_gmail_com wrote:
It is very important for us not to share the proprietary code with the client.
Whereas, CPORT doesn't work, it gives following message:
11 proc cport library=tmp1 file=trans;
12 run;
NOTE: PROC CPORT begins to transport catalog TMP1.SASMACR
NOTE: The catalog has 17 entries and its maximum logical record length is 3604.
WARNING: Entry type MACRO not supported by CPORT.
WARNING: Entry type MACRO not supported by CPORT.
If this issue is so important to your company then the proper approach would be to get a 32 bit system with their OS and run the code your new system and send that catalog.
However you might want to very carefully check that you have not used any features in your code that are not available in the other OS or version.
Thanks for all your help. I see there is no simple solution to this problem. Without the portability of macro catalogs across platforms, functionality of secured catalogs in SAS is pretty much useless.
As an interpreting environment, the SAS world is basically open-source.
As a consultant's customer, handover of ALL code (at least after a project is finished) would be a strict requirement for me.
hi Kurt,
I strongly disagree. Do we have the code for Microsoft windows, microsoft excel or hundreds of other software tools that we use on daily basis in computer, phones etc, although a lot of code is open source.
Code custom built for a client is client's property, whereas propriety code used to execute specific tasks is usually not client's property.
Vineet
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
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.