Can you post the log (at least the log snippet for the code shown)? Your program has that DATA step, followed immediately by the two %PUT statements?
I would look for an error in the log prior to this point. When scheduled jobs run, SAS will (by default) enter syntax check mode when an error occurs. If an error occurred earlier in the session, and SAS entered syntax check mode, then the DATA step would not execute, so the macro variables would not be created. But I believe the %PUT statements would still execute.
The code you showed is fine, so the problem must be somewhere else.
... View more
I know this thread only got "reanimated" because of a SPAM message, but this post is a perfect example of why you should (almost) never be using the ancient MISSOVER infile option.
@zekeT_sasaholic wrote:
First.
This process looks strange to me. The reading of input criteria as card statements.
I wont judge as maybe you are using that as a mock up.
but try this...
data layout;
infile cards missover;
input a $1-500 ;
cards;
/** your card stuff **/
;
run;
hth
zeke torres
www.wcsug.com
Using the MISSOVER option will prevent the input statement from moving to the next line when the current line does not have 500 remaining characters.
But it will also discard any line that has less than 500 characters (actually less than 481 since in-line data lines are always padded with spaces to the next multiple of 80 bytes).
Instead use the newer TRUNCOVER option (I think it is only 30 years old).
... View more
If a name is not recognized, it means that your local DNS serving your network segment has no entry for it.
Do you really have the correct name? If yes, your network admjnistrators need to fix this.
... View more
@ballardw
I hadn't thought about what a use could be for code like "N=%left(&sam)", but if you are right, or if you are wrong, I think there is probably a better way to handle it.
It is a constant struggle to get people to explain the big picture of what they are trying to do, they only want to talk about the specific coding problem they have, they don't want to get into the big picture. This particular request seems like it is an instance of the XY Problem.
... View more
If the tables are already sorted by Custid, use @Kurt_Bremsers suggestion. Otherwise SQL FULL JOIN is a simple query.
proc sql; create table want as select coalesce(aa.CustId, bb.Custid) as CustId, coalesce(aa.Y, bb.Y) as Y from aa full join bb on aa.CustId = bb.CustId ; quit;
... View more
Hi All, Sorry if this is out of the norm for a response. Quentin's suggestion in the second link referencing KB0036220 had the answer. By adding "umask 002" to my "workspaceserver_usermods.sh" config file did the trick.
... View more
Always keep in mind that in SAS, time and datetime values are counts of seconds. A fractional difference must therefore come from fractions of seconds, which are not displayed by the formats assigned to your variables.
... View more
You should bring this to the attention of SAS Technical Support.
I moved your post to the Administration community; "All Things Community" is for questions regarding the working of these SAS communities here.
... View more
