PH30635: CURRENT_DATE IS RETURNING INCORRECT DATE WHEN RUN AGAINST A DATASET

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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels