Re: Accessing .sas7bcat with Enterprise guide

MarkusWeick · Posted 07-12-2023 02:56 PM

Hi all,

I would be grateful for some help on how to access the content of a .sas7bcat file in enterprise guide.

Cheers, Markus

Please help to keep the community friendly.
Like posts you agree with or like. Mark helpful answers as “accepted solutions”. Generally have a look at https://communities.sas.com/t5/Getting-Started/tkb-p/community_articles

Solamente · Posted 07-12-2023 03:11 PM

Check out this SAS Note. https://support.sas.com/kb/24/575.html

ballardw · Posted 07-12-2023 03:20 PM

Do you know which version of SAS made the file?

The extension SAS7BCAT means that the file is a catalog. You may not be able to access a catalog created on a different operating system.

What is supposed to be in the catalog that you want to access?

The general approach is to have the file in a LIBRARY that your session has access to prior to use. How to use the contents depends on what is in it.

MarkusWeick · Posted 07-12-2023 03:30 PM

I assume it was made with the same 9.4 I am using now. It should contain a collection of macros.

Please help to keep the community friendly.
Like posts you agree with or like. Mark helpful answers as “accepted solutions”. Generally have a look at https://communities.sas.com/t5/Getting-Started/tkb-p/community_articles

ChrisHemedinger · Posted 07-12-2023 03:35 PM

This is a catalog file from SAS. If you assign a library to the folder that contains the file, you can then use the Catalog and Formats Explorer tool in SAS Enterprise Guide (under the Tools menu) to see the entries, such as compiled macros and formats.

SAS For Dummies 3rd Edition! Check out the new edition, covering SAS 9.4, SAS Viya, and all of the modern ways to use SAS!

MarkusWeick · Posted 07-12-2023 03:47 PM

Yes @ChrisHemedinger , I now can see the macro I am looking for. How can I open it?

Please help to keep the community friendly.
Like posts you agree with or like. Mark helpful answers as “accepted solutions”. Generally have a look at https://communities.sas.com/t5/Getting-Started/tkb-p/community_articles

SASKiwi · Posted 07-12-2023 04:06 PM

@MarkusWeick - While you can report on the contents of SAS catalogs with PROC CATALOG. macro entries can't be "opened", only executed and the source code of the macro cannot be extracted. You need to refer to the SAS code that created the macro originally.

MarkusWeick · Posted 07-12-2023 04:17 PM

I just tried the tip in Extracting a macro code from Catalog File - SAS Support Communities.

But got the the error message "The /SOURCE option was not specified when the macro M_UC was compiled. So I give up for the moment and search for the source code tomorrow.

Thanks to @Solamente, @ballardw, @ChrisHemedinger, @SASKiwi. You all brought me some steps further even if I haven't reached my goal yet.

Please help to keep the community friendly.
Like posts you agree with or like. Mark helpful answers as “accepted solutions”. Generally have a look at https://communities.sas.com/t5/Getting-Started/tkb-p/community_articles

AlanC · Posted 07-12-2023 05:13 PM

Another tip: do not store code/macros in catalogs. If you can't find the source, you are hosed. I have seen that happen as well.

IMO, catalogs are an archaic format and should be avoided at all costs.

https://github.com/savian-net

MarkusWeick · Posted 07-13-2023 01:22 AM

Hi @AlanC , thanks for the advice. After my experience so far I definitely won't store code/macros in catalogues.

Cheers, Markus

Please help to keep the community friendly.
Like posts you agree with or like. Mark helpful answers as “accepted solutions”. Generally have a look at https://communities.sas.com/t5/Getting-Started/tkb-p/community_articles

AlanC · Posted 07-13-2023 01:37 AM

I dont even store formats there. It is easier to %include everything.

Computers are just way more powerful than they were back in the day.

https://github.com/savian-net

Patrick · Posted 07-13-2023 03:41 AM

@AlanC wrote:
I dont even store formats there. It is easier to %include everything.

Computers are just way more powerful than they were back in the day.

Which of course then stores the macros and formats in this archaic format in WORK 😄

But agree with what you say except for the rare exception where one needs secure compiled macros.

ballardw · Posted 07-17-2023 04:34 AM

@Patrick wrote:

@AlanC wrote:
I dont even store formats there. It is easier to %include everything.

Computers are just way more powerful than they were back in the day.

Which of course then stores the macros and formats in this archaic format in WORK 😄

But agree with what you say except for the rare exception where one needs secure compiled macros.

Which is why I keep project specific formats in a permanent library and add the library to the FMTSEARCH path.

That way, as needed, I can override the same named format by making a version in WORK that appears first in the search path and still have both available as needed...

Macro's not so much.

yabwon · Posted 07-17-2023 06:09 AM

Continuing @AlanC suggestion. Maybe you consider using SAS Packages and SAS Packages Framework.

It allows you to easily share complex codes (a lot of macros, formats, functions, etc.) with others in easy way and at the same time it keeps source code (which is also easily accessible to user [not only developer]).

The latest YouTube video describing SPF is here: https://www.youtube.com/watch?v=T52Omisi0dk

Video about how to build your firs package is here: https://www.youtube.com/watch?v=hqexaQtGw88

Bart

_______________
Polish SAS Users Group: www.polsug.com and communities.sas.com/polsug

"SAS Packages: the way to share" at SGF2020 Proceedings (the latest version), GitHub Repository, and YouTube Video.
Hands-on-Workshop: "Share your code with SAS Packages"
"My First SAS Package: A How-To" at SGF2021 Proceedings

SAS Ballot Ideas: one: SPF in SAS, two, and three
SAS Documentation

SASKiwi · Posted 07-17-2023 01:01 AM

@MarkusWeick - If you switch to using AUTOCALL macro libraries, then by definition you are working off macro source code files stored in a defined AUTOCALL folder. In my experience this is the best way to manage macros and you are a lot less likely to lose them. If you do they stop working...🙂

2025 SAS Hackathon: There is still time!

SAS Training: Just a Click Away