SUPPORT / SAMPLES & SAS NOTES
Problem Note 38637: The swaactivatebatchjobs program that starts Emerging Issues child processes continues despite successful completion of the Emerging Issues processing
 |  |  |  |  |
Emerging Issues processing completes successfully, but the swaactivatebatchjobs program that starts the Emerging Issues child processes continues running. This problem occurs because the Job Control Table (JCT) is interrupted. As a result, the JCT record is not updated to RunCode=FINISHED.
As a workaround, use your operating system to terminate the swaactivatebatchjobs process manually.
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 Warranty Analysis | Microsoft Windows Server 2003 Datacenter Edition | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 |
| Microsoft Windows Server 2003 Enterprise Edition | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||
| Microsoft Windows Server 2003 Standard Edition | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||
| 64-bit Enabled AIX | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||
| 64-bit Enabled Solaris | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||
| HP-UX IPF | 4.1 | 4.2 | 9.1 TS1M3 SP4 | 9.2 TS2M2 | ||