About CaseySmith

CaseySmith · ‎08-28-2019

EG 8.1 Update 1 was recently released (last week... 8/20). I have not seen or heard any reports of the issue you describe. If you had EG logging turned on when the problem occurred, please send me the EG log and we'll investigate (it should have additional details about the unexpected error). If others encounter, please let us know asap (post back here and/or contact SAS Tech Support), so we can get more info, debug, and resolve. Thanks, Casey

CaseySmith · ‎08-27-2019

To see an example of VBScript that can be used to execute an EG project (rather than SAS code directly as in your example), schedule a project in the EG interface, which will create an EGScript.vbs file you can inspect. Casey

CaseySmith · ‎08-21-2019

@AlexL, I recommend trying the "Unlock all open data before running code" option (in EG's Tools->Options->Data->Performance). By default, EG 8.1 only unlocks data that it knows was created by the program you are about to run. Checking that option will result in EG unlocking *all* the data open in data views in that EG session, which reduces the possibility of resource contention. If that option does not accomplish your goal, I second contacting Tech Support, so we can get more details on the problem you are encountering. EG has always used member-level locking (even prior to 8.1), unless using SAS/SHARE, but that should not impede you. In fact, improvements have been made in 8.1 related to data locking... we now only hold the lock for 3 minutes of inactivity by default and then release it under the covers without closing the data grid. Prior to 8.1, the lock was held as long as the data was open in the grid. The grid would be closed after 30 mins of inactivity, thus releasing the lock. Casey

CaseySmith · ‎08-15-2019

This is a known issue that was fixed in EG 7.12 HF2 and 7.13, so I'm assume you are using an earlier version? If you are using EG 7.12, installing the latest 7.12 HF should resolve the problem. If you are using a version prior to 7.12, upgrading to 7.13 or later (I recommend the latest... 8.1) should resolve the problem. Casey

CaseySmith · ‎08-15-2019

What version of SAS are you running? 9.4M5 or 9.4M6? Are you saying the same ssh keys work with GITFN_CLONE? Or do you mean with "git clone" from command-line? @dazimm, any ideas why this wouldn't work with ssh keys? Perhaps related to the ssh keys needing to be generated a special way? Casey

CaseySmith · ‎08-15-2019

I'm glad switching the results format (ex. to SAS Report) is a reasonable workaround for now. Note: The HTML results format in EG 7.15 used the ODS HTML/HTML4 destination. EG 8.1 uses ODS HTML5 by default. I suspect the issue is specific to ODS HTML5. So, another workaround (if you prefer to stick with html) may be to use HTML4 instead of HTML5 in EG 8.1 (select "Use HTML" radio button, instead of "Use HTML5", in EG's Tools->Options->Results->HTML). In other words, I have a feeling using any results format other than HTML5 would avoid the issue. Casey

CaseySmith · ‎08-13-2019

Hi @TimCampbell, I agree with @SASKiwi that this would be a good one to report to SAS Tech Support. I wonder though if this is related to the new default results format in EG 8.1. EG 8.1 uses the ODS HTML5 destination as the default results format (consistent with SAS Studio) while previous versions of EG used SAS Report by default. You could test this theory by unchecking HTML and checking SAS Report in EG's Tools->Options->Results->General->Results Formats, and then re-run your code and see if you can still reproduce. Casey

CaseySmith · ‎08-08-2019

Yes, please open a track with SAS Tech Support. We'd like to get more details about the problem you are seeing, in hopes that we can reproduce, diagnose, and fix. Casey

CaseySmith · ‎08-08-2019

The reason you are getting the transcoding error is because you are trying to read a character that is not recognized in your current SAS session encoding. I would normally recommend changing your SAS session encoding to UTF-8, but if that is not an option, the only other thing I can think to try is to ignore the transcoding error via the NORSASIOTRANSERROR system option... https://go.documentation.sas.com/?docsetId=nlsref&docsetTarget=p09yh96xgvdzhjn1gimcw1d7vy1c.htm&docsetVersion=9.4&locale=en ... or try the outencoding option (on a libname statement) to copy the data to a library with an encoding that your current session encoding supports (ex. LATIN9 in your case): https://go.documentation.sas.com/?docsetId=nlsref&docsetTarget=n02q3gv9mfdwnmn1ca9kqa3gbayl.htm&docsetVersion=9.4&locale=en (ex. https://communities.sas.com/t5/General-SAS-Programming/Transcoding-problem/td-p/390028) Casey

CaseySmith · ‎08-06-2019

Yes, this has been improved in EG 8.1. When the Show full details when viewing SAS Libraries in File Dialog details view option (in EG's Tools->Options->General) is checked (off by default), if you right-click a table in the Servers pane and select Properties you will see the row count, along with other detailed info. For example: Additionally, when that option is on, EG's file open dialog will show the row counts along with other info in the Details view. For example: (This feature (the extra details in the FOD) has existed for many EG releases, but the extra details in the data set properties dialog from the Servers pane is new to EG 8.1.) Note: The option is off by default only because it can take slightly longer to query for the additional detailed info. Of course, alternatively, you can always submit SAS code to retrieve the record count (query the sashelp.vtable dictionary table as @Technolero showed or run proc contents on the desired data). Casey

CaseySmith · ‎08-06-2019

I was curious, so gave it a shot, but as you'll see from this log snippet, it only returns the filename: 76 filename myfile FILESRVC folderpath="/Users/cassmi" filename="yo.txt"; 77 %put %sysfunc(pathname(myfile)); yo.txt Also, there isn't really a way this (getting a path that references a file from SAS Content, but can be used in a server file system context) could work, since there is no full path to this file (in server file system context). The file doesn't exist on the server file system. It only exists in the SAS Content location. Casey

CaseySmith · ‎08-06-2019

Hi Isek, Yes, execution (via scripting) is by process flow, project, or individual items. There isn't an easy way to run just a single branch in a process flow via the scripting interface. I'm glad organizing by process flow allows you to accomplish your goal. Casey

CaseySmith · ‎08-06-2019

Short answer... no, there is not. That said, EG project (.egp) files are zipped archives, which contain project.xml files that define the items in the EG project and their relationships. Not a recommended, supported, nor easy approach as you would be getting into the "guts" (implementation details), but technically possible to identify the tables used in each flow in a project from the .egp file. Casey

CaseySmith · ‎08-06-2019

It's a little confusing, but the SAS Content tree and the server file system are two separate file stores (logical and physical, respectively). You uploaded the .shp file to the SAS Content location, but the code is referencing (looking for, but can't find) a file path on the server file system. So, you have two options... 1) You can access a file from a SAS Content folder directly by using a FILESRVC fileref. For example: filename myfile FILESRVC folderpath="/Users/sasdemo" filename="tl_2018_04_sldu.shp"; %shpimprt(shapefilepath=myfile Note: This requires that your SAS code is capable of accepting a fileref rather than only a file path string. Since macro parameters are just strings, I doubt the shpimprt macro will accept a fileref for the sharefilepath parameter, so probably not an option for you in this example. 2) You can FTP the file to your server file system (or a location it can access) and then reference that file in your SAS code. Note: In SAS Studio 5.1, only the SAS Content tree is surfaced in the UI. The server file system is not accessible from the SAS Studio 5.1 UI. In SAS Studio 5.2, the SAS Content tree and the server file system will be accessible. Thus, you'll be able to upload directly to either. Casey

CaseySmith · ‎08-06-2019

Hi @isek, Your PowerShell script works fine for me -- it runs the two desired process flows. (I used EG 7.15 HF8.) Note: The script as written runs the two flows, but does not save the project, so you won't see any difference in your project. If you want the results of the running of the process flows to be stored in the project, make sure to save the project in your script (ex. $project.Save()) before closing it. Note 2: If you have 32-bit EG installed, make sure you are running the PowerShell script with the x86 version of PowerShell. Similarly, if you have 64-bit EG installed, use the x64 version of PowerShell to run the script. Casey

Online Status	Offline
Date Last Visited	Friday