IBM Support

PI90918: DFHMQ0773 INVALID OR EXPIRED FACILITY TOKEN OR DFHMQ0777 LINK3270 ERROR RC=61, RESULTING IN 18/01/15 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Migrating from CICS TS 5.1 to CICS TS 5.2, you start receiving
    ABRG abends.  You see the following messages in the LOG:
    
    DFHMQ0773 E 08:09:23 CICSREGN CKBP 84848 Invalid or expired
                Facility token in message.
    or
    DFHMQ0777 E 13:47:29 CICSREGN CKBP 84848 Link3270 error.
                RC=61.
    
    Followed by:
    .
    DFHMQ0760 I 08:09:23 CICSREGN CKBP 84848
                MsgId=xxxxxx.
    DFHMQ0761 I 08:09:23 CICSREGN CKBP 84848
                CorrelId=xxxxxx.
    DFHMQ0762 I 08:09:23 CICSREGN CKBP 84848 Queue
                name=CICS.BRIDGE.QUEUE.
    DFHDU0203I 10/22/2017 08:09:24 CICSREGN A transaction dump was
               taken for dumpcode: ABRG, Dumpid: 1/0006,
               Tranid: CKBP, Tranum: 00084848, Program: DFHMQBP0.
    DFHMQ0748 E 08:09:24 CICSREGN CKBP 84848 Message removed from
                the request queue during backout processing.
    
    The problem here is that BRIH_FACILITYKEEPTIME is being set
    to 1.  That causes any bridge facility to be kept for only 1
    second after it was last used.  The keep chain for bridge
    facilities is checked for expired entries every time the chain
    is accessed.  We can see task 84848 process the chain and
    delete facility token xxxxxx.  That token had expired 12
    seconds ago but it was still "in use" by the TOR.
    
    The slower the AOR runs the more chance there is for tokens to
    expire before the next request arrives.
    
    It appears that changes made to DFHMQBP0 by PI46862/PI36660
    mean that a bridge facility is now always allocated.  The
    keeptime is set to the value in the request plus 1 (to prevent
    a value of 0 being used).  Under CICS 5.1, without the APAR
    change, a bridge facility was never used for these requests
    and the client never supplied a keeptime value.
    
    It appears that the 1 second delay is sometimes insufficient
    and we need to use a better value when the caller has not
    supplied one.  This APAR will revisit how the keeptime value
    is processed.
    
    
    Additional Symptom(s) Search Keyword(s): KIXREVDAM
    DFHMQ0773E
    DFHMQ0777E
    DFHMQ0760I
    DFHMQ0761I
    DFHMQ0762I
    DFHMQ0748E
    ABENDABRG kixdcfcic690
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users with APAR PI46862 applied.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHMQ0773 INVALID OR EXPIRED FACILITY   *
    *                      TOKEN OR DFHMQ0777 message with ABRG    *
    *                      abend occurs when using the Link3270    *
    *                      MQ Bridge.                              *
    *                      Incorrect MQCIH return code 160 is      *
    *                      returned following a 3270 transaction   *
    *                      abend.                                  *
    ****************************************************************
    * RECOMMENDATION: .                                            *
    ****************************************************************
    After applying PTFs for PI46862, the Bridge facility can expire
    too early, leading to messages DFHMQ0773 and DFHMQ0777 and
    abend ABRG.
    Also in the event of a target 3270 transaction abend, an
    incorrect MQCIH return code 160 (0xA0) is returned instead of
    the correct value 05.  This is the problem reported in
    APAR PI90450.
    Keywords: msgDFHMQ0773 msgDFHMQ0777 MQ0773 MQ0777 abendsABRG
    

Problem conclusion

  • UI31447 UI31448 UI49894 UI50820 UI49895 UI50822
    Module DFHMQBP0 is changed to use the specified Bridge facility
    keeptime if one is provided, or BRIHKT_DEFAULT if not.
    The MQCIH return code is set to the correct value 05 in the
    event of a target 3270 application abend.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI90918

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-30

  • Closed date

    2018-01-16

  • Last modified date

    2018-02-01

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

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

    PI91705 PI91706 UI53231 UI53232

Modules/Macros

  • DFHMQP0@ DFHMQP1@ DFHMQP3@ DFHMQR0@
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R803 PSY UI53232

       UP18/01/18 P F801 {

  • R903 PSY UI53231

       UP18/01/18 P F801 {

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 February 2018