BookmarkSubscribeRSS Feed
vineet7878_gmail_com
Obsidian | Level 7

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

13 REPLIES 13
vineet7878_gmail_com
Obsidian | Level 7
I don't have access to 32 bit OS and my client only has 32 bit OS.
data_null__
Jade | Level 19
Are you sure hiding your code is a good idea. If you are willing to let others see your work then you can use good old auto-call and not have to worry about bitness.
vineet7878_gmail_com
Obsidian | Level 7

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.

SuryaKiran
Meteorite | Level 14

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. 

Thanks,
Suryakiran
vineet7878_gmail_com
Obsidian | Level 7
I don't have access to 32 bit OS, my code is sitting in 64 bit OS. Whereas my client is using 32 bit OS.
data_null__
Jade | Level 19

@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?

Tom
Super User Tom
Super User

@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?

ballardw
Super User

@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.

vineet7878
Fluorite | Level 6

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.

 

Kurt_Bremser
Super User

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.

vineet7878
Fluorite | Level 6

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

sas-innovate-2024.png

Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.

Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.

 

Register now!

How to Concatenate Values

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.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 13 replies
  • 1581 views
  • 3 likes
  • 7 in conversation