About LinusH

LinusH

My experience of sending this type of errors to SAS support isn't great, they can rarely point out what causes the error. So I have usually solved it by restructuring the query. How large are the tables? (in saswork by looking into you program)

LinusH

Agree with @PaigeMiller sequences are easier to maintain/use. If you need the group_id within the new variable you can try this: data have; length group_id indicator 8; input group_id indicator; datalines; 1 1 1 0 1 0 1 1 1 0 1 0 1 0 2 1 2 0 ; run; data want; set have; by group_id; if first.group_id then index = 0; if indicator = 1 then index+1; new_id = cats(put(group_id,best.),'-',put(index,best.)); run; But to get the result you need, try this: data want; set have; by group_id; if first.group_id then index = 0; if indicator = 1 then index+1; new_id = cats(put(group_id,best.),substr('abcdefghijklmnopqrstuvwxyz',index,1)); run; It was not clear from your example how many times the indicator can change, but I guess the maximum with this technique would be 26.

LinusH

If this is collected by one person, maybe it's easier to direct her to store the data in a more readable format. If this data is entered manually it's error prone.

LinusH

I would start with storing the output in data sets, which can be obtained by using ODS: https://documentation.sas.com/doc/en/statug/15.2/statug_ttest_details38.htm Then exactly how to get them into Word is a different issue, and again ODS can be of help. Are you in a single user environment, otr do you by chance have Add-in for MSOffice and/or access to a SAS Stored Process server?

LinusH

In SAS no, in TD, probably not either. The connection time is probably the least of your concerns. Data processing and movement are. The only difference between the two is the DISTINCT. If your TD setup is good this operation will go faster there compared to SAS (don't know your SAS setup either...). If you don't want the trouble of writing explicit pass through code, you could use SAS SQL, your query will be passed down automatically to TD. The most optimal (from performance perspective) is to store the result in TD and continue working there, but then it depends on your use case, what you intend to do with the data next. If you wish to optimize the query further, speak with your TD DBA to see if anything can be done in TD.

LinusH

LinusH

"I am building a flow that contains multiple jobs.". If you run the job flow in SAS Job Scheduler (or any other scheduler that you decide to integrate), I'm pretty sure the logs are saved, even if the job fails. Have you verified this?

LinusH

Sounds like standard behviour for scheduling software, so it does not make sense to build it yourself. Logs are usually stored after running flows, and the log tells you where and why the job failed. Not sure why you want to store this in a database.

LinusH

The requirement is a bit vague. Do you want this for all users/applications in your environment? What is the use case to capture syntax errors? Usually if a SAS job/session ends in error, your environment keeps track on that (e.g. SAS Job scheduling). There are probably several ways of doing it, but a basic one would be to make sure the environment saves all the logs, and then have a (SAS? ) scripts that parses it.

LinusH

"It's a FEDSQL" No it's not, you have "proc sql;" in your program. If you wish to use FedSQL syntax you actually need to use the FedSQL procedure.

LinusH

You must not have a space between <DATE> and your constant.

LinusH

I would say the most common ist hat you would have separate depots for different computing environments. The SW order for your depot will tell you the content of the order.

LinusH

It is hard to trouble shoot DI jobs without access to the DI job itself. But it seems you haven't gone through the whole log yourself? If a job work sometimes, consider it not to function. You might have a libnme assignment too late in the code, and the second time it works, but not the first. But, check all the errors in the log and try to fix them one by one. ERROR: Libref RPTKDC19 is not assigned. ERROR: SQL View WORK.W1MN90FN could not be processed because at least one of the data sets, or views, referenced directly (or indirectly) by it could not be located, or opened successfully. How is this libname (not) assigned, perhaps it's defined as pre-assigned by external configuration, and now this is not done? LIBNAME report ORACLE PATH=REPOR SCHEMA=tbaadm AUTHDOMAIN="tes" ; %rcSet(&syslibrc); proc _____ 1 61 The SAS System 13:09 Friday, July 18, 2025 3278 ! sql NOPRINT; select count(1) ods_land.ERROR_TEST; %rcSet(&sqlrc); run; ERROR: Specified AuthenticationDomain not found in foundation repository. Misspelling? Or are you running the job in another environment where "tes" authdomain doesn't exist?

LinusH

It would be helpful to see the code and the error.

LinusH

As others pointed out, EG is "just" an interface to SAS. Other interfaces are SAS Studio (web based) and VScode. But I assume you primarily want to learn SAS coding. Buying your own SAS license (if possible) - I wouldn't consider that affordable for personal use. If you are an active student, you could get access to SAS Viya for Learners, but you need a University email account (e.g. .edu).