SAS EG is written in C#/.NET Framework. In general, it should use those mechanisms for anything local to the exe. However, SAS jobs are submitted to a SAS server so that is where SAS, the system, takes over and handles stuff within SAS.     C#/.NET Framework is pretty tied to Windows. Under the covers, I am pretty sure Framework uses O/S calls. It changed under Core, but this is Framework. If you want lower-level details, I would research .NET Framework.  ... View more

Take control of the whole thing with a custom task. If you want power in SAS EG, custom tasks are your best bet. They aren't too hard to do. Focus on a simple Hello World to get started and work up from there.    See these:   https://support.sas.com/documentation/onlinedoc/guide/customtasks/ https://blogs.sas.com/content/sasdummy/2015/06/11/creating-custom-tasks-for-sas-enterprise-guide-expert/   ... View more

Chris is the guy so I would follow his lead on how to break it up a bit.   If you want to understand the structure better, I wrote a utility that will unwind it for you. Free to use, etc.   https://github.com/savian-net/SaviEg     ... View more

As of yet, I have not seen anything that will convert easily between VB* and any of the .NET world (including PowerShell).   Best bet, in my experience, is to ask ChatGPT to do the prelim conversion. I then tweak it from there. It is mostly ok but is never right. YMMV. You have a trivial script so easy to convert.   VBS is dead so best to move away. PowerShell is an excellent choice. ... View more

I doubt it is SAS version; that is probably coincidental. Not necessarily, just a guess.   To track it down, I would suggest looking at the network and the processes to eliminate your end of the puzzle.   Use procmon and filter it down to the EG process. Use one of the network sniffers (I use Fiddler) and see if something is glitching the network. Both tools are free.    A lot of times these things are caused by additional security or other tools deployed onto machines. It could be some of my demons like Ivanti or CrowdStrike or something along those lines. ... View more

For now, use the command line tool that is there:   https://github.com/savian-net/SaviEg     ... View more

You can create a custom task using C#. EG is written in C# and it provides a means of doing this. You have to adhere to an interface and implement the parts.   There are examples on the SAS website and I should have an example or two on my github.   ... View more

Let me try and take a stab and how I would approach if given those circumstances. You can translate to python/your world and see if it makes sense.   I use C#/PowerShell so this is from that perspective.   Create a PS FileSystemWatcher that watches a directory for a File Change. The directory is wherever user saves their projects (see one example: https://devblogs.microsoft.com/powershell-community/a-reusable-file-system-event-watcher-for-powershell/) Make that a Windows service so it monitors all of the time When that change is detected, fire a script to Unwind the EGP Save the code components to a .SAS file Version control that SAS file I am happy to share my C# code that unwinds the EGP and put it on github. Would have to put in a bit of time to get it ready for publication but I have no objections.       ... View more

Let me save you some time (hopefully). The zip file changes each version (or major version). The XSD for the XML in those files is not public (SAS devs don't need it since they can direct map to the nodes). Think of the XML as the serialized version of the object. You have to guess at the deserialization.   The key, for you currently, is that it changes per version. This becomes more dramatic over time. VBS is also a poor language and very much a security risk. That might not matter in your situation.    You can continue to press the VBS script but getting it to work (for more than the specific version it was built for) is probably futile and is a poor platform (vbs) to boot. YMMV but that is my .02 cents.         ... View more

EGP files are merely binary zip files. They can be unzipped and the XML extracted. Playing version control that way, however, would be dangerous. That said, try it and see how it goes. Rename the file from ex. MyFile.egp to MyFile.zip and you can explore the structure.   Using C#, I have unwound the ZIP files as well as the XML so I can extract out the actual SAS code. That app is on github under SaviApp. Note: the EGP XML files and how everything holds together took a lot of work to figure out. Be prepared if you want to figure it out in python..   ... View more

I would echo ChrisNZ's suggestion and use ODBC.  In pretty much every MS/SAS consulting client, I would always encourage ODBC. It just works and is easier to configure.    OleDB is similar but ODBC is more widely used. I don't believe I used the SQLSRVR engine and I did dozens of SAS/SQL Server engagements. IIRC, it was difficult to get setup with modern SQL Server engines due to security.  I am working off of memories so it certainly may have changed. ... View more

Run some of the scripts through CoPilot and ask it to translate them to PowerShell. It should get you over 90% there with little effort. I use it to do VBA to C# and it does a decent job for specific tasks.    The scheduler has nothing to do with VBScript (unless I missed something). You can run any scheduler. For EG work, I use a combination of C# and PowerShell but many people would be comfortable with PS. You then just schedule your PS job.  ... View more

We run regasm, a lot, on thousands of machines. It is part of our normal install script. What it does is create the tlb files which are typelibs for COM/.NET communication. The tlb files allow a .NET program (ex. EG) to communicate with COM interop. Those libs need to be registered in the registry to work. I rely on them for communication between an Office ribbon and the underlying Office components.    Chris is an expert at this and can clarify if I missed something.   VBS is an issue and I would recommend other approaches if you plan on using it in the future:  https://techcommunity.microsoft.com/t5/windows-it-pro-blog/vbscript-deprecation-timelines-and-next-steps/ba-p/4148301     ... View more

There is nothing unusual about this. This is how SAS works in their own products (ex. EG). IntTech has been around, in some form, for decades and it is used to do this integration (code, logs, metadata, etc.). There are plenty of papers on it ranging from VBScript, VBA, C#, etc.   If the concern is that someone will submit malicious code, what I did was just stored the codes files and passed parms in via Swagger or some similar means.   ... View more