PM25176: WHEN USING SELECT STARTIME= AND ENDTIME=, THE ZONE= OFFSET PARAMETER IS NOT WORKING AS WOULD BE EXPECTED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A customer is using function BROWSE and SELECT statement with
  starttime and endtime parameters.  They enter their local
  time in the time= parameter and their offset from GMT in the
  zone= parameter and no records are found.  Entering just the
  GMT will result in the records being found. Therefore the z=
  parm is not working as expected.
  Code changes and a manual update will need to be made, in order
  to make this more user-friendly.
  Also, the help statement needs to be adjusted as well.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of QCF3.1. The changes affect      *
  *                 messages selection by start date/time and    *
  *                 end date /time.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using SELECT parameters            *
  *                      SELECT STARTTIME=.., -or-               *
  *                      SELECT ENDTIME=..,  -or-                *
  *                      SELECT STARTTIME=.., ENDTIME=           *
  *                      the zone Z=shh:mm is required, but has  *
  *                      not been used in selection process.     *
  *                      The  GMT and the zone have been         *
  *                      converted to internal timestamp format  *
  *                      and compared to the timestamps of the   *
  *                      messages - all 12 bytes.                *
  *                      The zone is in the last 2 bytes, so it  *
  *                      did not matter - actually the zone      *
  *                      has been disregarded.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The programs have been changes to compare the zone first and
  then the date and time. If the zone in the STARTDATE=..,
  ENDDATE=.. is 0, it is disregarded and messages are selected
  based on the GMT. If the zone Z=shh:mm is not 0, first the zone
  is checked when comparing the timestamps, and the messages are
  rejected if the zones do not match, if the zones match, the
  date/time information is compared.
  

Problem conclusion

• The selection process for SELECT STARTDATE=.. ENDDATE=... is
  changed to compare the zone offset first and then the GMT. The
  field help is changed to better explane the format, required for
  startdate and enddate information for the panels.Also the
  startdate and enddate format for the panels is improved to not
  require the zone information. The zone is set to 0 and
  disregarded in selection process, when not entered in the
  panels.
  

Temporary fix

Comments

APAR Information

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

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

  UK63524

Modules/Macros

•    IQCF13   IQCH93   IQCH930  IQCP0000 IQCP2150
  IQCP2200 IQCQMR2A IQCQMR2B IQCQMR2C IQCQMR2X IQCQMR28 IQCQMR29
  IQCSEL61 IQCXSEL6
  

Fix information

• Fixed component name

  IMS QUEUE CNTL

• Fixed component ID

  5697E9900

Applicable component levels

• R310 PSY UK63524

     UP10/12/29 P F012

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.