10-11-2016 04:18 PM
Our requirement is the schedule the SAS EG program/jobs/projects which are located on network drive. And theschedling should be done from SAS server. Network drive is accessable from SAS server.
We tried to access the SAs EG projects by logging on SAS server and accessing network drive. We got error message pop up (Cannot find the file "Z:\XXXXXX.egp" on "My Computers". Also attaching the same in the post.
Please suggest how the scheduling of the SAS EG jobs can be done from SAS server which are placed in network drive.
10-11-2016 05:16 PM
EG projects can only be scheduled on a PC. If you want to schedule on your SAS server you need to export the EG project to SAS program(s) using the EG File Export options then schedule the programs. What scheduler are you intending to use? Some are available via SAS Management Console. Check with your SAS administrator if you are not sure what's available.
10-11-2016 11:55 PM
10-12-2016 02:35 AM
Scheduling on your SAS server is a very good choice, for the reasons you have explained. As I already said EG projects can only be scheduled on a PC where EG is installed.
So you need to export your EG project to SAS programs (in EG - File Export) and then schedule those. You can still put these SAS programs on the same network drive if you wish but your SAS server must be able to reference that drive. There is probably no Z drive mapped on your server. If my explanation is not clear please let me know.
10-12-2016 04:20 AM
I also STRONGLY suggest to schedule only SAS code, and never EG projects in a production environment
- projects require the presence of a working SAS EG on the host executing the scheduled objects. This means additional maintenance, and, more importantly, only works on Windows "servers", as EG is totally dependent on Windows because of (argh) .NET. You also need to make sure that the metadata configuration of the server-side EG matches that of the clients.
- Base SAS codes are text files that can be viewed/edited with a simple text editor on ANY operating system. To execute them, you only need a working SASFoundation (not even a metadata connection for most of the jobs), and a proper autoexec.sas that contains the library definitions needed for your scheduled codes. Totally platform-independent, and any scheduling software can be made to execute the necessary batch or shell-script files.