topic Re: how to use control M scheduler to schedule enterprise guide projects in SAS Enterprise Guide

how to use control M scheduler to schedule enterprise guide projects

naveenraj — Wed, 25 May 2016 08:56:06 GMT

Hi,

Has anyone used control M scheduler to schedule enterprise guide projects. I have scheduled project with schedule prroject within SAS enterprise guide. If i have multiple projects that are dependent on one another how can i set it up to run one after other using control m. if you have any documents or experiance setting it up, pls share.

Regards,

Naveen

Re: how to use control M scheduler to schedule enterprise guide projects

Kurt_Bremser — Wed, 25 May 2016 10:56:44 GMT

Enterprise Guide exists solely on your Windows desktop. So you would need to start with "How does Control M manage a Windows system?".

EG interfaces with the native Windows Scheduler via VB scripting to run projects.

I would not consider scheduling processes via desktops as sound practice. Instead I'd always try to use more reliable backend servers for scheduling.

In our organization we have:

- Control M on the mainframe

- SAS BI Server on a UNIX server

- Enterprise Guide on desktops

We do not schedule EG projects; instead we save production code 8developed in EG) as .sas files to the UNIX server and have that run in batch mode by Control M. As interface (between Mainframe and UNIX) we use locally built scripting that relies totally on out-of-the-box tools (ksh & openssh).

Re: how to use control M scheduler to schedule enterprise guide projects

LinusH — Thu, 26 May 2016 20:48:54 GMT

I'm with @Kurt_Bremser here, you schedule the generated .sas code.
If wish to have the dependency control in SAS and have the SAS command generated for you, register the .sas files as jobs in SMC. Then build job flows in the schedule manager plugin in SMC. When "scheduled" a vbs or shell script is generated which you can call from control M.

Re: how to use control M scheduler to schedule enterprise guide projects

naveenraj — Mon, 30 May 2016 12:10:13 GMT

thanks @Kurt_Bremser and @LinusH for your insight into this topic.