SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 61386: A stored process fails and errors are generated when the STP procedure is executed remotely

DetailsHotfixAboutRate It

Errors similar to the following might be generated when PROC STP executes remotely:

FILENAME _WEBOUT TEMP RECFM=V LRECL=32767 ENCODING=utf-8;
                                                   ---                                                   24                                               
ERROR: Error in the FILENAME statement.
ERROR 24-2: Invalid value for the ENCODING option.
ERROR: Failure in statements submitted to remote Connect server session: ERROR:
Error in the FILENAME statement.

When PROC STP submits a stored process and it executes remotely, the following FILENAME statement, which points to the _WEBOUT file, is added automatically: 

filename _webout temp recfm=V lrecl=32767;

The _WEBOUT file is a temporary file allocation that is used to hold _WEBOUT data on the remote machine until it can be copied back to the local host.

When the local SAS® session on which PROC STP is executing has the ENCODING system option set, PROC STP then adds an ENCODING= option to the FILENAME statement. The problem occurs when the ENCODING= value contains a non-alphanumeric character (for example, the dash character [-] in the value UTF-8). Values for the ENCODING= option must be surrounded by quotation marks if they contain non-alphanumeric characters. 

To work around this problem, you need to force PROC STP to run locally instead of remotely by adding the SERVER=LOCAL option to the PROC STP statement. The FILENAME statement for _WEBOUT is not generated when the stored process executes locally. 

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS Integration TechnologiesWindows 7 Enterprise 32 bit9.4 TS1M49.4 TS1M5
Microsoft Windows Server 2012 Std9.4 TS1M49.4 TS1M5
Microsoft Windows Server 2012 R2 Std9.4 TS1M49.4 TS1M5
Microsoft Windows Server 2012 R2 Datacenter9.4 TS1M49.4 TS1M5
Microsoft Windows Server 2012 Datacenter9.4 TS1M49.4 TS1M5
Microsoft Windows Server 2008 for x649.4 TS1M49.4 TS1M5
Microsoft Windows Server 2008 R29.4 TS1M49.4 TS1M5
Microsoft Windows Server 20089.4 TS1M49.4 TS1M5
Microsoft Windows 109.4 TS1M49.4 TS1M5
Microsoft Windows 8.1 Pro x649.4 TS1M49.4 TS1M5
Microsoft Windows 8.1 Pro 32-bit9.4 TS1M49.4 TS1M5
Microsoft Windows 8.1 Enterprise x649.4 TS1M49.4 TS1M5
Microsoft Windows 8.1 Enterprise 32-bit9.4 TS1M49.4 TS1M5
Microsoft Windows 8 Pro x649.4 TS1M49.4 TS1M5
Microsoft Windows 8 Pro 32-bit9.4 TS1M49.4 TS1M5
Microsoft Windows 8 Enterprise x649.4 TS1M49.4 TS1M5
Microsoft Windows 8 Enterprise 32-bit9.4 TS1M49.4 TS1M5
Microsoft® Windows® for x649.4 TS1M49.4 TS1M5
z/OS9.4 TS1M49.4 TS1M5
Windows 7 Enterprise x649.4 TS1M49.4 TS1M5
Windows 7 Home Premium 32 bit9.4 TS1M49.4 TS1M5
Windows 7 Home Premium x649.4 TS1M49.4 TS1M5
Windows 7 Professional 32 bit9.4 TS1M49.4 TS1M5
Windows 7 Professional x649.4 TS1M49.4 TS1M5
Windows 7 Ultimate 32 bit9.4 TS1M49.4 TS1M5
Windows 7 Ultimate x649.4 TS1M49.4 TS1M5
64-bit Enabled AIX9.4 TS1M49.4 TS1M5
64-bit Enabled Solaris9.4 TS1M49.4 TS1M5
HP-UX IPF9.4 TS1M49.4 TS1M5
Linux for x649.4 TS1M49.4 TS1M5
Solaris for x649.4 TS1M49.4 TS1M5
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.