About ly2024

ly2024 · ‎06-24-2025

This is what I found out: The old job actually ran the old program, instead of the new program with the update (same name, same saved folder), but the permanent dataset already contains the new columns because of my manual run. So they don't match. Whenever the program in SAS Studio is modified, the old scheduled job should be deleted, although the program still uses the same name and is saved in the same folder; and a new job for the updated program should be scheduled. It seems that the scheduled job will grab the Studio program and keep it with itself instead of just pointing to the program in Studio.

ly2024 · ‎06-21-2025

Hi Ballardw, Thank you for your thoughtful suggestions. Yes, I saved the LOG. This morning, the job ran successfully. The permanent appends the dataset, and the dashboard shows the update. So when the Studio program has some modification or update, the job scheduled to run it needs to be deleted, and a new job needs to be scheduled. This is what I learned. As you said, this may be related to the system options set up. If I find out why later, I will update this post. Thank you.

ly2024 · ‎06-20-2025

I deleted the original scheduled job to run the Studio program. Then I scheduled a new job to run it. The job will run daily in the morning. Will check on it tomorrow morning. Hopefully this will resovle the issue.

ly2024 · ‎06-20-2025

Ballardw, Thank you. Daily and permanent are using the same source. The program codes to prepare them are also the same, except the one running in SAS Studio to prepare daily has one more step to append the daily to the permanent. I don't understand why it would run successfully when I executed it step by step in Studio, but the automated job will fail. I am thinking of copying the code into a new program and scheduling a job on that new one to see. Best, Lin

ly2024 · ‎06-20-2025

XXX_Daily is a SAS dataset created by the code in the same program. The program will first do some manipulations and after the dataset is done, then append to the CAS table.

ly2024 · ‎06-20-2025

Let me try PROC APPEND! 😊

ly2024 · ‎06-20-2025

Hi Tom, Thank you for your feedback. I first ran the code in SAS Base and got the permanent one refreshed with data until Tuesday. Then went to the SAS Studio, updated the code, loaded the permanent one, ran the code, and appended Wednesday's dataset. Maybe there is something different between BASE and Studio. Let me check my BASE program. If its structure was different from the permanent one's structure, why would the manual run be done successfully? CASLIBNAME is the name of the CAS folder. But good catch on that length requirement. Thank you!

ly2024 · ‎06-20-2025

Hello community, I encountered an issue and needed the help of experts to see what happened. I have a SAS Studio program scheduled to run a job daily. It worked well. On Wednesday, I updated the program a little bit and tested it by running it manually. It worked at that time. Then I rescheduled a job for it. The job failed. The error message is "ERROR: The provided list of column names did not match names in table XXX" while it is to append a dataset to CAS table. SAS code is as below: DATA CASLIBNAME.XXX (APPEND=YES); SET XXX_DAILY; RUN; I just debugged and ran it manually, and it works. May I know how to resolve it and avoid this kind of thing when trying to append in the future? Thank you so much! Lin

ly2024 · ‎03-14-2024

Tom, You right. I checked "Select server", and changed it to "0 Local", now it works fine. I am a beginner of SAS EG. So, selecting a running server is a must-do setup for a project? Thank you! Lin

ly2024 · ‎03-14-2024

Today I run a project that has %include statement and libname statement, it works fine. Then I created a new project with those two statements, but both of them didn't work. The error message for statement "%include "C:\user\xxx\abc.sas"; " is WARNING: Physical file does not exist, /opt/sas/config/Lev1/SASApp/C:\Users\xxx\abc.sas. ERROR: Cannot open %INCLUDE file C:\Users\xxx\abc.sas. The error message for statement "libname test "C:\user\xxx";" is NOTE: LIbrary TEST does not exist. Both the exactly same statements work fine in the other project. Does anyone have some clue about it? Thank you!

Online Status	Offline
Date Last Visited	‎06-24-2025 12:10 PM

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

SAS Studio Program: append dataset data step works manually, but not w...

Re: %include statement works in one project, but not another one

%include statement works in one project, but not another one

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

Re: SAS Studio Program: append dataset data step works manually, but n...

SAS Studio Program: append dataset data step works manually, but not w...

Re: %include statement works in one project, but not another one

%include statement works in one project, but not another one