BookmarkSubscribeRSS Feed
LynnP_sas
SAS Employee

Submitting a program to run in SAS® should return the same results whether it runs as a background job, runs interactively, or is submitted using SAS® Enterprise Guide® (or SAS® Studio).  You might experience a situation where this does not appear to be the case and wonder what is happening.  Remember that in each scenario, you are running a SAS session that is configured by its option settings.  While the standard configuration options for the SAS session are likely the same, the individual SAS clients might contain specific option settings.

 

These option settings can be affected by pre-code submitted by the SAS client or options settings that are controlled by preferences within the client.  Option settings that can affect results are FMTERR/NOFMTERR and VALIDVARNAME=.  If you are seeing differences in programs that are submitted using different methods, you might want to issue a PROC OPTIONS statement to compare the settings between the two environments.  You can even specify which options you want to see and add the VALUE parameter to display the value as well as how/where the value was set. 

 

For example:

 

 

proc options option=fmterr value;

run;

 

2 REPLIES 2
SASKiwi
PROC Star

This is a good argument for applying global system options at the "SASApp" server context level and not separately on batch and workspace servers.

hackathon24-white-horiz.png

The 2025 SAS Hackathon Kicks Off on June 11!

Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.

YouTube LinkedIn

Creating Custom Steps in SAS Studio

Check out this tutorial series to learn how to build your own steps in SAS Studio.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 2 replies
  • 662 views
  • 4 likes
  • 3 in conversation