BookmarkSubscribeRSS Feed
deleted_user
Not applicable
Anyone using EG for production reporting systems? I'm very interested in any experiences and tips.

Specifically, we're seeking to schedule daily, weekly, and hourly jobs on Windows XP server using EG as the primary development and data reviewing process. We'll have about 1,000 different jobs to run over various schedules.

Our data size is relatively small most of the time, 30 seconds and under to run. Some are larger and take up to 10 minutes.

We are most interested in audits, conditional starts (i.e. data occured in a certain range, run job A, otherwise run job B).

Suggestions? Comments?
3 REPLIES 3
Andrew_F
Calcite | Level 5
You cannot directly replace the functionality of regular SAS using EG. For instance, using EG, try this common control technique:

data _null_ ;
if &sqlobs = '0' then abort abend 9 ;
run ;

There are other gotchas as well.
deleted_user
Not applicable
I have spoken with customers about how they typically maintain such an environment. It is different than straight batch SAS submission, but nearly as flexible but with some integration that EG offers that isn't in batch SAS.

1) They put a central PC/high-end desktop in the data center that the main admins for SAS can remote desktop into. This machine is always on and on a high speed network.

2) They use the project scheduling capability in EG. This is VB script based and leverages Windows AT (scheduler.) Note- EG can also act as an OLE Automation client to be called from other apps if desired.

3) People can customize the VB scripts for a variety of purposes. For example, here is an example VB script to allow passing custom parameters into the project at run time (by Chris Hemedinger on our Dev Team):

Option Explicit
Dim app
Dim prjName
Dim prjObject
Dim parmList
Dim parm

prjName = "C:\temp\autowithparams.egp" 'Project Name

' start the app and open the project
Set app = CreateObject("SASEGObjectModel.Application.4")
Set prjObject = app.Open(prjName,"")

' discover the parameters
Set parmList = prjObject.Parameters
Wscript.Echo "Project has " & parmList.Count & " parameters."

' work with the first parameter
Set parm = parmList.Item(0)
WScript.Echo parm.Name & " parameter has default value of " & parm.DefaultValue
parm.Value = "M"

WScript.Echo parm.Name & " parameter has been set to value of " & parm.Value

' run the project
prjObject.Run

WScript.Echo parm.Name & " parameter has been set after Run to value of " & parm.Value

prjObject.Close
app.Quit


Also refer to http://support.sas.com/techsup/unotes/SN/002/002696.html and http://support.sas.com/faq/045/FAQ04515.html for more details.

Best regards,
Stephen
deleted_user
Not applicable
Thansk Stephen! Any other pointers?

sas-innovate-2024.png

Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.

Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.

 

Register now!

SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 3 replies
  • 706 views
  • 0 likes
  • 2 in conversation