Problem Note 41468: Multi-processing CONNECT programs might become unresponsive when data is piped using the SASESOCK engine
 |  |  |  |  |  |
MP CONNECT programs might become unresponsive when data is piped between tasks using the SASESOCK engine and when explicit ports are used. The program can behave differently on different machines, with different versions of SAS® software, and with different time-out values. An example of the code that causes the problem is included on the Full Code tab.
To work around this problem, use service names for open ports instead of direct port numbers.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS/CONNECT | Microsoft Windows XP Professional | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2008 for x64 | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 for x64 | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Standard Edition | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft Windows XP 64-bit Edition | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft® Windows® for x64 | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| z/OS | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Windows Vista | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Windows Vista for x64 | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| 64-bit Enabled AIX | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| 64-bit Enabled HP-UX | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| 64-bit Enabled Solaris | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| HP-UX IPF | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Linux | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Linux for x64 | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| OpenVMS on HP Integrity | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
| Solaris for x64 | 9.21 | 9.3 | 9.2 TS2M0 | 9.3 TS1M0 | ||
This is and example of code that could cause the program to become unresponsive when it is submitted.
options sascmd="!sascmd";
signon task1;
signon task2;
rsubmit task1 cwait=no;
libname pipe1 sasesock ":8001" timeout=500;
data pipe1.test;
do i=1 to 10000000;
x1=ranuni(2992029);
x2=ranuni(2994029);
output;
end;
run;
endrsubmit;
rsubmit task2 cwait=no;
libname pipe1 sasesock ":8001" timeout=500;
proc means data=pipe1.test;
var x1 x2;
run;
endrsubmit;
listtask _all_;
waitfor _all_ task1 task2;
rget task1;
rget task2;
signoff task1;
signoff task2;
A fix for this issue for SAS/CONNECT 9.21_M2 is available at:
http://ftp.sas.com/techsup/download/hotfix/HF2/B99.html#41468
Multi-processing CONNECT programs might become unresponsive when data is piped using the SASESOCK engine.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2010-11-10 11:36:40 |
| Date Created: | 2010-11-01 13:28:23 |