SPDSFSAV Macro Variable

Specifies whether you want to retain table data if the SPD Server table creation process terminates abnormally.

Valid in:	SPD Server
Default:	NO. Normally, SAS closes and deletes tables that are not properly created.
Restriction:	Assignments for macro variables with character input (for example, YES \| NO \| BINARY arguments) must be entered in uppercase (capitalized).

Syntax

Required Arguments

Details

Example

Syntax

SPDSFSAV=YES | NO

Required Arguments

YES

enables FORCESAVE mode and saves the table.

NO

Default server actions delete partially completed tables.

Details

Large tables can require a long time to create. If problems such as network interruptions or disk space shortages occur during this time period, the table might not be properly created and an error condition might be signaled. If SAS encounters such an error condition, it deletes the partially completed table.

In the server, you can set SPDSFSAV=YES. Saving the partially created table can protect the time and resources invested in a long-running job. When the SPDSFSAV macro variable is set to YES, the SPD Server LIBNAME proxy saves partially completed tables in their last state and identifies them as damaged tables.

Marking the table damaged prohibits other SAS DATA or PROC steps from accessing the table until its state of completion can be verified. After you verify or repair a table, you can clear the “damaged” status and enable further read/update/append operations on the table. Use the PROC DATASETS REPAIR operation to remove the damaged file indicator.

Example

Configure the server before you run the table creation job for a large table called ANNUAL. If some error prevents the successful completion of the table ANNUAL, the partially completed table will be saved.

%let SPDSFSAV=YES;
DATA SPDSLIB.ANNUAL;
...
RUN;

Last updated: February 8, 2017