APAR status
-
Closed as fixed if next.
Error description
-
- This only happens when the current_date dataitem is used with the dataset dataitem, for example when together in a List object. - When used by itself it's working correctly, for example when used within a Singleton object - Current_Timestamp is working fine
Local fix
Problem summary
-
**************************************************************** * USERS AFFECTED: * * All Users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to IBM Cognos Analytics 11.2.4 * ****************************************************************
Problem conclusion
Temporary fix
Comments
-
The current_date function is processed by compute service for uploaded files and data sets and returns current date in UTC. A new current_date session parameter has been added to Cognos Analytics 11.2.4 that can be used as a macro (#$current_date#) in data modules and reports to ensure the current data is processed by the query service and returns date of Cognos Analytics server time zone instead of UTC. Documentation: Session parameters
APAR Information
-
APAR number
PH30635
-
Reported component name
COG REPORT STUD
-
Reported component ID
5724W12RS
-
Reported release
B09
-
Status
CLOSED FIN
-
PE
NoPE
-
HIPER
NoHIPER
-
Special Attention
NoSpecatt / Xsystem
-
Submitted date
2020-10-16
-
Closed date
2022-12-16
-
Last modified date
2022-12-16
-
APAR is sysrouted FROM one or more of the following:
-
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTSF6","label":"Cognos Analytics"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B09","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
06 September 2024