IBM Support

PH65821: 0C4 IN DFHSIP. CICS MAY USE AN MVS JOBSTEP TCB TO ATTEMPT TO LOCATE THE AFCB. IT SHOULD USE THE CICS JOBSTEP TCB TO DO THIS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The DFHAUTH macro attempts to locate the AFCB associated with a
    TCB. Normally a TCB such as QR will have its AFCB. If the
    current TCB does not have an AFCB however, the DFHAUTH macro
    would go straight to the CICS jobstep TCB to obtain its
    AFCB address.
    It would do this via the current TCB's field TCBJSTCB which
    points to the JOBSTEP TCB. In some cases however, a CICS jobstep
    TCB ( which  CICS refers to as the JS TCB ) may not in fact be
    the actual JS TCB as known to MVS for the job. For example, the
    jobs initial program could run under the actual Job Step TCB and
    it then attaches DFHSIP which would run under the CICS JS TCB.
    Although CICS would know this as the JS TCB, it would not be
    the jobstep TCB as far as MVS is concerned.
    
    This situation meant that in some circumstances DFHAUTH would
    redirect to an MVS jobstep TCB to try and locate the AFCB off
    it, when that jobstep TCB was not in fact the CICS JS TCB
    running DFHSIP - it had no AFCB.  When this cccurred, it
    presented as on 0C4 during CICS startup.
    Additional symptoms: IEP FO TCB CAUF
    AFCX ATTACH SVC migrating migration
    Additional keywords: ABEND0C4
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend 0C4 in startup.                   *
    ****************************************************************
    This problem presented as an 0C4 during CICS start up.
    
    The DFHAUTH macro seeks to identify the Authorised Function
    Control Block (AFCB) linked to a TCB. Typically, a TCB such as
    QR will possess an AFCB. However, if the current TCB lacks an
    AFCB, the DFHAUTH macro will directly access the CICS jobstep
    TCB to retrieve the AFCB address. It achieves this via field
    TCBJSTCB in the current TCB, which addresses the JOBSTEP TCB.
    
    However, the CICS jobstep TCB (referred to by CICS as the JS
    TCB) may not actually correspond to the genuine JS TCB
    recognized by MVS for the job. For instance, the job's initial
    program might execute under the true Job Step TCB, subsequently
    attaching DFHSIP, which would operate under the CICS JS TCB.
    While CICS identifies this as the JS TCB, it does not align with
    the jobstep TCB from MVS's perspective.
    As a consequence, in some cases, DFHAUTH will select the MVS
    jobstep TCB in an attempt to locate the AFCB from it, even when
    that jobstep TCB was not the CICS JS TCB executing DFHSIP - this
    MVS jobstep TCB lacks an AFCB. This caused an 0C4 during CICS
    startup.
    

Problem conclusion

  • The DFHAUTH macro has been modified to search the correct TCBs
    when it requires an AFCB.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH65821

  • Reported component name

    CICS TS Z/OS V6

  • Reported component ID

    5655YA100

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-03-25

  • Closed date

    2025-07-11

  • Last modified date

    2025-09-17

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

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

    UO04038 UO04039

Modules/Macros

  • DFHAPDM  DFHASV   DFHCRC   DFHCRNP  DFHCRSP  DFHCSVC  DFHDBCR
    DFHDBCT  DFHDMDM  DFHDMSVC DFHDSDM  DFHDSDS3 DFHDSMT  DFHDSTCB
    DFHDT64M DFHDTDA  DFHDTDC  DFHDTLI  DFHDTLX  DFHDTRC  DFHDTRI
    DFHDTSS  DFHDTST  DFHDUDU  DFHDUSR  DFHDUSVC DFHHPSVC DFHKEAR
    DFHKEDD  DFHKEDS  DFHKEGD  DFHKEIN  DFHKESTX DFHKETCB DFHKETIX
    DFHL2BS4 DFHL2CH4 DFHL2CHE DFHL2CHM DFHL2CHO DFHL2CHP DFHL2LB
    DFHL2SR5 DFHL2WF  DFHLDDM  DFHLDDMI DFHLDLB2 DFHLDLB3 DFHLDLD1
    DFHLDLD2 DFHLDLD3 DFHLDSVC DFHLEPTD DFHLEPTI DFHMNDM  DFHMNSU
    DFHMNSVC DFHMQIG  DFHMQSVC DFHNCSVC DFHPSPSS DFHRXDM  DFHRXSVC
    DFHRXUW  DFHS2PP  DFHSIB1  DFHSIF1  DFHSIJ1  DFHSJNDI DFHSJPTI
    DFHSKC   DFHSMDM  DFHSMPP  DFHSMSU  DFHSOIS  DFHSOLS  DFHSOSVC
    DFHSTP   DFHSTST  DFHWSSN2 DFHWSSR  DFHWSTKV DFHWTI   DFHXCDMP
    DFHXCGUR DFHXCSVC DFHXSAD  DFHXSCT  DFHXSDM  DFHXSFL  DFHXSIS
    DFHXSKR  DFHXSLU  DFHXSPW  DFHXSRC  DFHZDSP  DFHZHPSR DFHZIS2
    DFHZXSTS
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R400 PSY UO04039

       UP25/07/12 P F507

  • R500 PSY UO04038

       UP25/07/12 P F507

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":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
17 September 2025