1

I would like to use Enterprise Guide as a development environment for creating a SAS job (Base SAS code only), but I then need to use DI Studio to schedule that job to run at a particular time.

I want to use EG for developing the job because I believe it is a better development environment (program editor etc.) than DI.

I also want the job to exist as a stored process so that users can run it outside the schedule if necessary.

Can I create a simple DI Studio job that merely calls an existing stored process?

jl6
  • 6,110
  • 7
  • 35
  • 65

1 Answers1

1

Of course - there are many ways to achieve this. One is to create a separate job (with 'user written code' component) and Stored Process, both of which simply %include your Enterprise Guide program.

Another is to create your stored process using Enterprise Guide, and then in DI Studio (user written code) call the stored process directly using proc stp (see documentation)

Yet another is to paste your EG code into DI Studio and 'deploy job as stored process' - documentation for that is here.

Oh, and to answer your 'headline' question - you don't schedule jobs in DI! The deployed .sas code can be scheduled via Schedule Manager (SMC), the OS itself, or other third party tools (eg LSF).

Allan Bowe
  • 12,306
  • 19
  • 75
  • 124
  • 1
    +1 on using `%include` for both DI jobs and stored processes. Keeps the .sas code out of metadata, and easily maintainable using any editor / IDE. – Quentin Mar 03 '17 at 13:07