Usage Note 30863: An "ERROR: No logical assign for filename _WEBOUT" message might occur when running a SAS® program that uses the %STPBEGIN and %STPEND autocall macros
The following messages might occur when running a SAS program that uses the %STPBEGIN and %STPEND autocall macros:
ERROR: No logical assign for filename _WEBOUT.
WARNING: No body file. HTML output will not be created.
These messages can occur if the SAS program is not being executed as a stored process.
Using the %STPBEGIN and %STPEND macros is only valid when you are executing code through a SAS® Stored Process Server or SAS® Workspace Server, so these macros will not work from a regular SAS session in batch mode or through the Display Manager. You must first register the stored process from the SAS® Management Console or from SAS®Enterprise Guide®. Then you can execute the stored process from any of the BI clients such as SAS Enterprise Guide, the SAS® Add-In for Microsoft Office, the SAS® Information Delivery Portal, SAS® Web Report Studio, and so on.
To test the code in a regular SAS session before you start using it as a stored process (which is always a good practice), you can comment out the %STPBEGIN and %STPEND statements and temporarily substitute ODS HTML statements. For example:
*ProcessBody;
/* %stpbegin; */
ods html file="<path>\myfile.html";
proc print data=sashelp.class;
run;
ods html close;
/* %stpend; */
For more information on using the %STPBEGIN and %STPEND macros, see the SAS 9.1.3 Integration Technologies, Developer's Guide.
See SAS Note 34120, " 'ERROR: No logical assign for filename _WEBOUT' occurs," for another scenario that results in this ERROR message.
See SAS Note 33585, " 'WARNING: No logical assign for filename _WEBOUT' occurs," for a scenario that results in a WARNING message about the _WEBOUT filename rather than an ERROR.
Operating System and Release Information
SAS System | SAS Integration Technologies | z/OS | 9.1 TS1M3 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 | |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 | |
Microsoft® Windows® for x64 | 9.1 TS1M3 | |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 | |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 | |
Microsoft Windows 2000 Server | 9.1 TS1M3 | |
Microsoft Windows 2000 Professional | 9.1 TS1M3 | |
Microsoft Windows NT Workstation | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | |
Microsoft Windows XP Professional | 9.1 TS1M3 | |
Windows Vista | 9.1 TS1M3 | |
64-bit Enabled AIX | 9.1 TS1M3 | |
64-bit Enabled HP-UX | 9.1 TS1M3 | |
64-bit Enabled Solaris | 9.1 TS1M3 | |
HP-UX IPF | 9.1 TS1M3 | |
Linux | 9.1 TS1M3 | |
OpenVMS Alpha | 9.1 TS1M3 | |
Solaris for x64 | 9.1 TS1M3 | |
Tru64 UNIX | 9.1 TS1M3 | |
*
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.
Date Modified: | 2021-04-27 09:55:16 |
Date Created: | 2008-01-04 10:40:36 |