topic Re: Switching the Selected Server (SASApp => SASAppVA) via code in EG in SAS Enterprise Guide

Switching the Selected Server (SASApp => SASAppVA) via code in EG

dincoo — Mon, 30 May 2016 10:28:51 GMT

Hi all,

I have a huge code that runs every night in EG.

I want to add another code after the original code but it has to run at SASAppVA server. Actually, I want to update the table which is used by reporting at VA.

Is there a way of doing this like writing a statement like libname?

Many thanks,

Onur

Re: Switching the Selected Server (SASApp => SASAppVA) via code in EG

LinusH — Mon, 30 May 2016 11:02:58 GMT

First, executing jobs in EG in batch for other and personal use cannot be considered as bets practice.

If you wish to update VA/LASR data, I get the impression that isn't only personal...?

Second, developing jobs that are of ETL style, EG, again, is not the preferred tool, DI Studio is.

I would look for a solution where you execute those batch jobs on the SAS server(s). Do you share the metadata server between the two appservers?

Perhaps you need a 3rd party scheduler to manage dependencies between jobs on different serves.

Re: Switching the Selected Server (SASApp => SASAppVA) via code in EG

CaseySmith — Tue, 31 May 2016 02:23:08 GMT

If your SASAppVA workspace server is defined in the same metadata server as your SASApp workspace server (you see both in EG's Servers view), then it would be trivial... add another program node and have the second program run on SASAppVA (select it from the "Selected Server" dropdown on the contextual toolbar of your second program). The first program could run on SASApp and the second on SASAppVA. Draw an explicit link between the two programs to ensure they run in the order you wish. (You can create a link by right-clicking a node and selecting "Link Program to..." or by clicking the right side of a node and dragging to another node.)

If your SASApp and SASAppVA workspace servers are in different metadata contexts, then it requires other approaches (ex. SAS/CONNECT, writing data to permanent location accessible by both environments, etc.).