Please post the whole log of the proc report into a window opened with the {i} button.
BTW, I recommend to get rid of these stupid variable names three years before yesterday. Such fancy strings belong in labels, that's why labels exist.
@anirudhs wrote:
Team following code is not giving any output on sas viya but the code is working is working in sas 9.4 but when executed on viya its showing only note as you may have missed a quoted string or its 256 char long no error :
PROC REPORT DATA=demo.Rural_Sales_MASTER_CORE_ZONE MISSING
style(report) = {just=center borderwidth=0.5 font = ('zurich BT',12PT) bordercolor = black}
style(header) = {foreground = WHITE background =maroon font = ('zurich BT',12PT) fontweight = bold bordercolor =black}
style(column) = {just=left foreground = black borderwidth = 0.5 borderstyle=solid bordercolor = black};
/*WHERE ZONE IN ('Zone SW','Zone NE');*/
COLUMN ZONE 'FTD(#)'n 'MTD(#)'n 'Target Accounts'n 'SDLM(#)'n 'FTD(Cr.)'n 'MTD(Cr.)'n 'Target Amount'n 'SDLM(Cr.)'n ;
DEFINE ZONE/GROUP;
define 'Target Accounts'n/"Plan(#)";
define 'Target Amount'n/"Plan (Cr.)";
RBREAK AFTER / SUMMARIZE ;
COMPUTE ZONE;
IF _BREAK_ ="_RBREAK_" THEN DO ZONE ='Total' ;
CALL DEFINE(_ROW_,"STYLE","STYLE={FOREGROUND = WHITE BACKGROUND = MAROON FONT = ('ZURICH BT',12PT) FONTWEIGHT = BOLD}");
END;
ENDCOMP;
RUN;
Doesn't work is awful vague.
Are there errors in the log?: Post the code and log in a code box opened with the {i} to maintain formatting of error messages.
No output? Post any log in a code box.
Unexpected output? Provide input data in the form of data step code pasted into a code box, the actual results and the expected results. Instructions here: https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-dat... will show how to turn an existing SAS data set into data step code that can be pasted into a forum code box using the {i} icon or attached as text to show exactly what you have and that we can test code against.
Your batch job is running with SAS system option validvarname=v7 (which makes a lot of sense IMO).
As I already said, get rid of those stupid variable names three years before yesterday.
@anirudhs wrote:
Hi Kurt actually we cannot get rid of the variable names as its the requirement of the client as they are in habbitual of these names as per the indian banking names.
Any other way out
IMO that's a non-argument. Fancy names can be stored in labels and retrieved from there when you export to other formats (csv, Excel).
They are not needed within SAS and only cause trouble.
As a consultant, it is also your job to show your client where they do not work efficiently.
But if you still want to keep hurting yourself, use
options validvarname=any;
before running this code.
Please post the log you get from the scheduled run, from the options validvarname to the proc report.
@anirudhs wrote:
Hi Kurt , the issue is that when submitting the code manually its working perfectly but tis not resolving when in scheduler and the options command is also not working in scheduler
That doesn't make sense. Code issued manually and via batch might get a different environment (different config and autoexec files) which could explain what you observe. But any option set directly in your program code will overwrite what's set in the environment config as default.
If this is about variable names then add options VALIDVARNAME=ANY; at the beginning of your code.
Registration is now open for SAS Innovate 2025 , our biggest and most exciting global event of the year! Join us in Orlando, FL, May 6-9.
Sign up by Dec. 31 to get the 2024 rate of just $495.
Register now!
Learn the difference between classical and Bayesian statistical approaches and see a few PROC examples to perform Bayesian analysis in this video.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.