Problem Note 63389: Code that sets consecutive SYSTASK commands stops executing after about 6,481 consecutive attempts
 |  |  |  |  |
A set of SYSTASK commands that is meant to run in a loop might stop working when it reaches approximately 6,481 consecutive times.
Here is an example of code that should generate 10,000 consecutive SYSTASK commands. However, the commands stop executing after the 6,481st time.
%macro a;
%do i=1 %to 10000;
systask command 'echo >NUL' taskname=t&i status=s&i;
waitfor _all_ t&i;
%end;
%mend a;
%a
%do i=1 %to 10000;
systask command 'echo >NUL' taskname=t&i status=s&i;
waitfor _all_ t&i;
%end;
%mend a;
%a
The workaround is to break up the consecutive SYSTASK commands. You can divide the set of SYSTASK commands across unconnected SAS jobs and then run the jobs separately.
A fix for this issue is planned for a future software release.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | Base SAS | z/OS | 9.4 TS1M5 | |
| z/OS 64-bit | 9.4 TS1M5 | |||
| Microsoft® Windows® for x64 | 9.4 TS1M5 | |||
| Microsoft Windows 8 Enterprise 32-bit | 9.4 TS1M5 | |||
| Microsoft Windows 8 Enterprise x64 | 9.4 TS1M5 | |||
| Microsoft Windows 8 Pro 32-bit | 9.4 TS1M5 | |||
| Microsoft Windows 8 Pro x64 | 9.4 TS1M5 | |||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4 TS1M5 | |||
| Microsoft Windows 8.1 Enterprise x64 | 9.4 TS1M5 | |||
| Microsoft Windows 8.1 Pro 32-bit | 9.4 TS1M5 | |||
| Microsoft Windows 8.1 Pro x64 | 9.4 TS1M5 | |||
| Microsoft Windows 10 | 9.4 TS1M5 | |||
| Microsoft Windows Server 2008 | 9.4 TS1M5 | |||
| Microsoft Windows Server 2008 R2 | 9.4 TS1M5 | |||
| Microsoft Windows Server 2008 for x64 | 9.4 TS1M5 | |||
| Microsoft Windows Server 2012 Datacenter | 9.4 TS1M5 | |||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4 TS1M5 | |||
| Microsoft Windows Server 2012 R2 Std | 9.4 TS1M5 | |||
| Microsoft Windows Server 2012 Std | 9.4 TS1M5 | |||
| Microsoft Windows Server 2016 | 9.4 TS1M5 | |||
| Windows 7 Enterprise 32 bit | 9.4 TS1M5 | |||
| Windows 7 Enterprise x64 | 9.4 TS1M5 | |||
| Windows 7 Home Premium 32 bit | 9.4 TS1M5 | |||
| Windows 7 Home Premium x64 | 9.4 TS1M5 | |||
| Windows 7 Professional 32 bit | 9.4 TS1M5 | |||
| Windows 7 Professional x64 | 9.4 TS1M5 | |||
| Windows 7 Ultimate 32 bit | 9.4 TS1M5 | |||
| Windows 7 Ultimate x64 | 9.4 TS1M5 | |||
| 64-bit Enabled AIX | 9.4 TS1M5 | |||
| 64-bit Enabled Solaris | 9.4 TS1M5 | |||
| HP-UX IPF | 9.4 TS1M5 | |||
| Linux for x64 | 9.4 TS1M5 | |||
| Solaris for x64 | 9.4 TS1M5 | |||
A fix for this issue for Base SAS 9.4_M6 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/D9T.html#63389A fix for this issue for Base SAS 9.4_M5 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/B6Q.html#63389
Consecutive SYSTASK commands in a loop that runs about 6,481 times can stop executing.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2018-12-17 12:54:34 |
| Date Created: | 2018-12-14 13:34:55 |