IBM Support

PM26713: DFHMAINS DEFINES TRANSACTION DEFINITIONS WITH DATALOC(BELOW) INSTEAD OF DATALOCATION(ANY).

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • We have CICS TS 4.1 running Service Flow Runtime 3.2 (SFR).
    
    SFR is building & installing definitions in CICS for the
    application transaction used by the flows
    THe issue is that we are seeing the transactions being
    defined
    with :
    TASKDATALOC(BELOW)
    
    whereas the DFHMAXRT template on the workstation has :
    TASKDATALOC(ANY)
    .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS SFR transactions defined as        *
    *                      TASKDATALOC(BELOW).                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There is an inconsistency with the 2 methods that may be used
    to define an SFR Transaction resource to a CICS system.
                                                                   .
    Method 1 is selected on the SFM modeller ( a check box ) and
    when selected, a 'resource template' ( DFHMAXRT ) is used.  This
    template has TASKDATALOC(ANY) specified.
                                                                   .
    Method 2 uses SFR transaction CMIT which will drive DFHMAINS.
    A CREATE TRANSACTION call in DFHMAINS does not specify a
    TASKDATALOC parameter and as a consequnce, the TASKDATALOC
    will default to BELOW.
    

Problem conclusion

  • DFHMAINS has been modified and will now define an SFR
    Transaction resource as TASKDATALOC(ANY).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM26713

  • Reported component name

    SERVICE FLOW FE

  • Reported component ID

    5655M1502

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-15

  • Closed date

    2010-11-29

  • Last modified date

    2011-01-03

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

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

    UK62679

Modules/Macros

  •    DFHMAINS
    

Fix information

  • Fixed component name

    SERVICE FLOW FE

  • Fixed component ID

    5655M1502

Applicable component levels

  • R300 PSY UK62679

       UP10/12/02 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.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC5SJS","label":"Service Flow Feature"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 January 2011