SUPPORT / SAMPLES & SAS NOTES
Problem Note 19477: PROC FREQ with WHERE statement causes connection failure using Remote Library Services
 |  |  |  |  |
Using a WHERE statement or clause in the FREQ procedure might cause connection problems when using Remote Library Services (RLS) with SAS/SHARE® or SAS/CONNECT® software.
For example, if you use Transfer Control Protocol (TCP) as the communication access method, you might lose the connection to a SAS/SHARE z/OS server while submitting code similar to the following example:
proc freq data=libref.dset ;
where var < n ;
run;
proc freq data=libref.dset ;
where (var < n) ;
run;
Errors written to the client and server SAS logs might contain the following text:
/* PC client ERROR */
ERROR: Attempt to communicate with server SDCMVS.SHR9 refused by
server. The current request failed.
ERROR: The connection to server SDCMVS.SHR9 has been lost. The
current request failed. This error may reoccur on subsequent
requests.
ERROR: The connection to server SDCMVS.SHR9 has been lost. The
current request failed. This error may reoccur on subsequent
requests.
ERROR: A communication subsystem partner conversation setup request
failure has occurred.
ERROR: Communication Subsystem Request Failure: Supporting
communication link has been severed.
/* z/OS client ERROR */
ERROR: Attempt to communicate with server SDCMVS.SHR9 rejected by
server.
ERROR: The connection to server SDCMVS.SHR9 has been lost. The
current request failed. This error may reoccur on subsequent
requests.
ERROR: A communication subsystem partner conversation setup request
failure has occurred.
ERROR: Communication Subsystem Request Failure: Supporting
communication link has been severed.
/* z/OS SHARE server ERROR */
YHRCREP: Unexpected ERROR C0005B25 from WQRQST in "FREQ"(3) for user
userid(15):
ERROR: A communication subsystem message transmission
request failure has occurred.
ERROR: writev call failed, system error is '66'.
Note: the server does not end abnormally in this example.
You can avoid this problem in the following two ways:
- Use Cross Memory Services (XMS) as your communication access method.
- Use TCP, but disable the overlapping I/O by using the following %LET
statement on the client side:
%LET NOOVLPIO=YES;
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS/SHARE | Microsoft Windows XP Professional | 9.1 TS1M3 | 9.2 TS1M0 |
| Microsoft Windows NT Workstation | 9.1 TS1M3 | |||
| Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Microsoft Windows 2000 Server | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Microsoft Windows 2000 Professional | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Linux | 9.1 TS1M3 | 9.2 TS1M0 | ||
| 64-bit Enabled Solaris | 9.1 TS1M3 | 9.2 TS1M0 | ||
| z/OS | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Linux on Itanium | 9.1 TS1M3 | 9.2 TS1M0 | ||
| HP-UX IPF | 9.1 TS1M3 | 9.2 TS1M0 | ||
| 64-bit Enabled HP-UX | 9.1 TS1M3 | 9.2 TS1M0 | ||
| OpenVMS Alpha | 9.1 TS1M3 | 9.2 TS1M0 | ||
| 64-bit Enabled AIX | 9.1 TS1M3 | 9.2 TS1M0 | ||
| Tru64 UNIX | 9.1 TS1M3 | 9.2 TS1M0 | ||