DATA Step, Macro, Functions and more

How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Reply
Contributor
Posts: 27

How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

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

Super User
Posts: 10,280

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878_gmail_com

No, and no. Catalogs are OS- and bitness-specific. Recreate from code in each environment.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
How to convert datasets to data steps
How to post code
Contributor
Posts: 27

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to KurtBremser
I don't have access to 32 bit OS and my client only has 32 bit OS.
Super User
Posts: 10,280

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878_gmail_com

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.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
How to convert datasets to data steps
How to post code
Respected Advisor
Posts: 3,852

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878_gmail_com
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.
Contributor
Posts: 27

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878_gmail_com

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.

Valued Guide
Posts: 597

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878_gmail_com

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
Contributor
Posts: 27

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to SuryaKiran
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.
Respected Advisor
Posts: 3,852

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878_gmail_com

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

Super User
Super User
Posts: 8,125

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to data_null__

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

Super User
Posts: 13,583

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878_gmail_com

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

New Contributor
Posts: 2

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878_gmail_com

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.

 

Super User
Posts: 10,280

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to vineet7878

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.

---------------------------------------------------------------------------------------------
Maxims of Maximally Efficient SAS Programmers
How to convert datasets to data steps
How to post code
New Contributor
Posts: 2

Re: How do I create a secure macro catalog that works across 32bit and 64 bit operating systems

Posted in reply to KurtBremser

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

Ask a Question
Discussion stats
  • 13 replies
  • 151 views
  • 3 likes
  • 7 in conversation