IBM Support

PK67172: REPROCESS TO BE STARTED FROM ANY TIME POINT (NOT CHECKPOINT TIME)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • REPROCESS to be started from ANY time (not CHECKPOINT time).
    
    This is a forward fit of QCF V210 APAR PK51187.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of QCF3.1 which use REPROCESS and      *
    *                 want to reprocess messages based on          *
    *                 time the messages have been created.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: REPROCESS selects messages using        *
    *                      time set in CHKPT statement.            *
    *                      It firsts selects the check point,      *
    *                      then all messages that are in queue     *
    *                      checkpoint and all messages after.      *
    *                      This APAR is a solution for customer    *
    *                      requirement to select messages for      *
    *                      reprocessing, based on the time the     *
    *                      messages have been created.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

  • New option has been added to support REPROCESS
    function with automatic checkpoint selection:
    Parameter DT (Date Type) sets the date/time
    D=..,T=.. parameters type. This is either the
    checkpoint date/time, or the starting value for
    messages creation time.
    1. With IQCSELCT use new function in checkpoint
    statement with LAST:
    
    CHKPT    LAST,SYS3,RE,D=2007.290,T=13:38:11,DT=CP
    FUNCTION REPROCESS
    Or
    
    CHKPT    LAST,SYS3,RE,D=2007.290,T=13:38:11,DT=MSG
    FUNCTION REPROCESS
    
    - Parameter DT = CP will start with  the checkpoint
    with timestamp equal to  D=...T=.... Local time.
     All messages that have been on the queue (and not
    processed ) at the time of the checkpoint and all
    messages that have been inserted after the
    checkpoint will be selected.
    ( message selection can be restricted with
    SELECT statement - SELECT STARTTIME=D..,T=..)
     -Parameter DT = MSG will select all messages that
    have been inserted at and  after D=...T=... local time.
    With this parameter an earlier checkpoint will be
    used as starting point and all messages that have
    been inserted after the specified date/time  will be selected.
    
    There can be a significant difference when using
    both parameters- DT=CP usually selects more messages -
    it selects messages that have been created at earlier
    point and not been processed till the checkpoint
    ( these messages will be in the checkpoint records).
    DT=MSG will select only messages that have been
    created at and after the selected D=..T=..
    
    However, next 2 sets of statements will create the same
    output:
    CHKPT    LAST,SYS3,RE,D=2007.290,T=13:38:11,DT=CP
    FUNCTION REPROCESS
    SELECT  STARTTIME=D=2007.290,T=11:38:12.000000
    and
    CHKPT    LAST,SYS3,RE,D=2007.290,T=13:38:12,DT=MSG
    
    FUNCTION REPROCESS
    
    2. With IQCABAT0 use new function in checkpoint
    statement with new parameter @prm4:
    Sample and comments for the new parameter are in the updated
    sample
    
    With DT=CP- the exact checkpoint is used and all messages
    that have been on the queue and all messages that arrived
    on the queue after  will be selected
    With DT=MSG - an earlier checkpoint will be selected
    to be the start checkpoint - and only messages that have
     been inserted after the date/time will be selected.
    Messages that are inserted earlier and stay on the queue will
    be ignored.
    

APAR Information

  • APAR number

    PK67172

  • Reported component name

    IMS QUEUE CNTL

  • Reported component ID

    5697E9900

  • Reported release

    310

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2008-06-04

  • Closed date

    2008-06-23

  • Last modified date

    2008-07-01

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

    PK51187

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

    UK37603

Modules/Macros

  • IQCABAT0 IQCACKPT IQCAEG01 IQCALST0 IQCAMSG0
    IQCAQRY0 IQCARCAB IQCARCDM IQCARPRS IQCARUN  IQCASEGE IQCASELO
    IQCMDATA IQCMLSTR IQCSELCT IQCSELDC IQCUNLOD IQCXWRUL
    

Fix information

  • Fixed component name

    IMS QUEUE CNTL

  • Fixed component ID

    5697E9900

Applicable component levels

  • R310 PSY UK37603

       UP08/06/25 P F806

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A6","label":"IMS Queue Control Facility"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2008