# if less than requested bytes, we're at EOF # read bytes from source file, 1K at a time

# assign a Fileref so we can use FileService from IOM (The complete example is available on GitHub.) Here's a PowerShell program snippet that implements these steps.

When completed, close the local and remote file handles, and unassign the SAS file reference ( Close method and DeassignFileref method).

Write the contents into a local file (PowerShell objects).

Read the contents of the file into a local array of bytes ( Read method, repeating in 1K increments).

Tell SAS to open the remote file for reading ( OpenBinaryStream method).

Obtain a SAS reference to the file (FileService AssignFileref method.

For a file download operation, these are the basic steps: As with most file-based operations in SAS, the FileService relies on the use of a SAS fileref, or the name that SAS uses to reference your file within a program. The SAS Workspace provides the FileService API, which allows you to transfer file-based content between your local application and the SAS session. When the program runs, it creates a file named hist.png in the /projects/results folder within the SAS session. Ods listing gpath='$destPath' style=plateau # change these to your own SAS-session-based Consider this program, implemented in a PowerShell script, which creates an image with PROC SGPLOT:

What if your program creates Output Delivery System (ODS) files such as HTML or graphics? To retrieve those results, you need to download the files from the SAS session to your local machine, where your application can access them. When you run a SAS program on a remote session, sometimes the expected result is more substantial than just a text-based listing. In that example, the only results I retrieved were the SAS log and SAS listing (text) output, if any. In a previous article, I described how to use Windows PowerShell to connect to a remote SAS Workspace, run a SAS program, and retrieve the results.

How to download sas disc