APAR status
Closed as program error.
Error description
ENVIRONMENT: ITM 6.2.1 fp1(Issue was run into on) RELATED FILES/OUTPUT: See Below REPRODUCTION STEPS: 1. Setup Linux or any other OS agent. 2. Setup data collection on the attributes you are going to run a Custom SQL against 3. Create the a query like below or similar to your test agent: ( The query in this screen shot is: SELECT "WRITETIME", "System_Name", "CPU_ID", "User_CPU", "User_Nice_CPU", "System_CPU", "Busy_CPU", "Idle_CPU", "Wait_IO_CPU", "User_Sys_Pct", "Timestamp" FROM "KLZ_CPU" WHERE $TIMESPAN$ "System_Name" = $NODE$ ORDER BY "WRITETIME" DESC ) 4. Assign this query to the workspace: For this query, the customer entered the following value for $TIMESPAN$ : 1 = 1 AND 5. The Table will show the sample with data. 6. Click "OK", if you have data, you should see the table displaying the query. Note that the Time Span Query is displayed This will successfully pass a time into the $TIMESPAN$ variable specified in the Custom SQL. Here is the TEP ctsql trace. (Trace removed due to APAR space constraints) However, if you select the Time Span Navigator (top right of the picture directly above) and select anything: This is the result: (Trace removed due to APAR space contraints) L2 ANALYSIS: Based off the documentation, it states: Not all workspace views are able to display a time span or the range that you have specified. In this case, no values are displayed and a message in the view's status bar says that the query assigned to the view does not support a historical time range. It is likely that historical data collection has not been configured for the attribute group shown in the view or there is no historical data to report. Exit historical navigation mode to remove this message. To see historical data in this view, you must first configure historical data collection for the attribute group referenced by the query, then start collection and wait a sufficient period of time for historical data to be gathered before displaying the view again. Based off the statement above, ITM "captures the table (which can be mapped to attribute group) in the query definition in the TEPS database". This was reproduced on an NT and LZ agent. Traces are above. A current possible code fix exists for this issue, however, I will not place it in this doc to keep code internal.
Local fix
Problem summary
History navigation mode fails with custom SQL. Custom SQL created in a workspace with a substitutable $InputDate$ variable will have parm substituted initially. Custom SQL for Historical collection worked fine initially but changing time span didn't work and showed the following errors. KFWITM491W Historical data not available for this view. KFWITM492W Query is unable to utilize time span filter
Problem conclusion
The code is changed to check if it's a custom query for historical time span changes. The fix for this APAR is included in the following maintenance vehicle: | fix pack | 6.2.1-TIV-ITM-FP0004
Temporary fix
Comments
APAR Information
APAR number
IZ77704
Reported component name
TEPS
Reported component ID
5724C04PS
Reported release
621
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-18
Closed date
2010-08-09
Last modified date
2010-12-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TEPS
Fixed component ID
5724C04PS
Applicable component levels
R621 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCTLMQ","label":"ITM Tivoli Enterprise Portal Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
15 December 2010