Problem Note 41401: A batch report incorrectly shows a status of LATER in the diagnostic client
The current logic for batch-report management incorrectly sets the runcode column in the parmsl.jobcontrol table for a MARTREFRESH report to LATER. However, the value should be FINISHED if the counter column in the userdl.analysis table is set to a value other than the report.autoUpdateCounter value in the app.config file.
The runcode column is shown in the diagnostic client as Run Code in the Job Control Table. To set this value, use the status column of the userdl.analysis table instead of the current logic.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Warranty Analysis | Microsoft Windows 2000 Advanced Server | 4.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 4.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Server | 4.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Enterprise Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Standard Edition | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
64-bit Enabled AIX | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
64-bit Enabled Solaris | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
HP-UX IPF | 4.1 | 4.3 | 9.1 TS1M3 SP4 | 9.2 TS2M3 |
*
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.
A batch report can incorrectly show a status of LATER in the diagnostic client when it should have a status of FINISHED. A code change is required in order to set the status based on the status column of the userdl.analysis table.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2010-12-15 10:59:33 |
Date Created: | 2010-10-26 11:27:01 |