DATA Step, Macro, Functions and more

Translating a Process Flow to a nohup script

Reply
New Contributor
Posts: 3

Translating a Process Flow to a nohup script

Hey!

 

I have EG 4.2 projects that have some not so complex process flow. It is mostly to sync programs from different SAS servers we have in the company. I've been trying to automate those programs without the scheduler, since our computers disconnect from the servers after some time. I've been using the nohup to fix this. In order to sync the sas programs, I have them send an "ok" table via FTP so that the other program can start, but this seems rather sloppy.

 

I assume that the EG acts like an IDE would and send commands to the SAS server like the IDE sends to the compiler and creates all the links and compiles all the other codes and execute the main file. How does the EG translates a process flow to base sas? What would be the best way to do something like this?

 

Thanks for the help! 

PROC Star
Posts: 1,561

Re: Translating a Process Flow to a nohup script

EG only sends SAS code to the SAS server.

 

All the programs and the links between them are in the EG project, which is read on your PC by your EG session. The server knows nothing about them until EG sends code to run on the server.

 

Does this make sense?

New Contributor
Posts: 3

Re: Translating a Process Flow to a nohup script

Yes, it does

 

I get that, the problem is that the connection to the SAS server can be lost. The EG has some logic to make the sync and order of the process flow to work. I'd like to emulate that without the EG, I'd like to send a nohup command directly to the SAS server to avoid losing that connection

PROC Star
Posts: 1,561

Re: Translating a Process Flow to a nohup script

> the problem is that the connection to the SAS server can be lost.

 

It shouldn't. Solve the underlying network issue.

 

> EG has some logic to make the sync and order of the process flow to work. I'd like to emulate that without the EG, I'd like to send a nohup command directly to the SAS server to avoid losing that connection

 

EG interacts with SAS servers via the SAS Integrated Object Model (IOM), a proprietary SAS communication protocol. You'll need a way to make the server (and EG) think that the line is up when it isn't. Not really an option imho.

 

Respected Advisor
Posts: 3,887

Re: Translating a Process Flow to a nohup script

SAS is a scripting language and there is no compile/link. EG just sends SAS code to the server for execution. The SAS server then compiles the script at run time (so it's "interpreted").

 

With EG under File/Export you can export all the code to a .sas file (a file containing SAS script). Move this generated code to the server and then schedule it server side like you would do with any other script. 

 

 

New Contributor
Posts: 3

Re: Translating a Process Flow to a nohup script

I've just tried the export code solution, but it does not change servers, it runs all the codes on a single server (the one from the first code).

Ask a Question
Discussion stats
  • 5 replies
  • 101 views
  • 0 likes
  • 3 in conversation