Another automation question - the VB.net side isn't able to read job conditions in an egp file....

saslover15 — Tue, 11 Aug 2020 20:21:42 GMT

The automation we are building is failing on job conditions. At line 5, below, notice there is nothing in between the quotes of the "if" condition. It is null. So the VB.net side that drives the run can't yet see what the condition is. In the job condition in the SAS EG project, it says "If this condition is true: "Include or Exclude Vendor equal to 'EXCLUDE'" So we want the piece of hand-coding to run if the user chooses EXCLUDE. Our automation can read the user picking EXCLUDE just fine. But when it gets to the job condition, it can't read the SAS EG interface's job condition.

How do we fix this so our automation can see this "if" condition??? Here is the log snippet with the missing if condition:

Log for "Condition Evaluation for Piece_of_Handcoding1." run at 8/11/2020 3:34:20 PM on MyServer
1          ;*';*";*/;quit;run;
2          OPTIONS PAGENO=MIN;
3          %LET INCL_EXCL = EXCLUDE;
4          data _NULL_; rc = 0;
5          if '' = 'EXCLUDE' then
6             rc = 1;
7          CALL SYMPUT('_egrc', PUT(rc,1.));
8          stop;
9          run;

Re: Another automation question - the VB.net side isn't able to read job conditions in an egp file..

saslover15 — Wed, 26 Aug 2020 19:42:31 GMT

We solved this, in case anyone ever stumbles across this post. The solution is to put on the VB.NET side, 'INCLUDE' = 'INCLUDE' (or 'EXCLUDE = 'EXCLUDE' if it is the exclude scenario).

topic Another automation question - the VB.net side isn't able to read job conditions in an egp file.... in SAS Enterprise Guide

Another automation question - the VB.net side isn't able to read job conditions in an egp file....

Re: Another automation question - the VB.net side isn't able to read job conditions in an egp file..