IBM Support

II10834: MSGDFHLG0772 LOGSTREAM FAILURES WITH CICS TRANSACTION SERVER AND THE MVS LOGGER ALSO SEE II11322

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • CICS Transaction Server R1.1 and R1.2
    565514700
    CICS/ESA R510 CICS TS R1.1 566514700
    
        MSGDFHLG0772 DFHLG0772 MSGDFHRM0400 DFHRM0400
        MSGDFHLG0800 DFHLG0800
    
    In cases of a logstream failure or a failure within the MVS
    logger function documentation for CICS and the logger are
    often required for problem analysis.
    .
    PQ00271 ensures CICS initiates a dump whenever a DFHLG0772
            message is issued.
    .
    PQ04998 provides additional information when the logstream is
            printed using DFHJUP
    
    OW27057 and OW27058 are required fixes for the MVS logger
            to ensure a dump is taken when a condition is detected
            that will be returned to CICS as a logstream error
            (i.e. return code 804, 836, etc).
    .
    OW21383 adds support in the IXCMIAPU utility for the
            LOGSTREAM and STRUCTURE NAME keywords.
    .
    OW27153 introduces the D LOGGER command which provided status
            information about the logger address space and coupling
            facility.
            D LOGGER,L provides logstream status information
    .
    When CICS detects a logstream failure and produces a DFHLG0772
    message it will also set an indicator in the CICS catalog
    showing the next start must be INITIAL.   If documentation
    was not collected on the failing run, it may not be possible
    to obtain the required information for problem analysis.
    .
    To allow for documentation collection, CICS has introduced
    a "diagnostic run".
    .
    The "diagnostic run" indicator is set by the recovery manager
    following the detection of a failed logstream.
    .
    Message DFHRM0152 is written documenting that fact the next
    START=AUTO will result in a diagnostic (AUTODIAG) run.
    .
    A "diagnostic run" can be initiated by using
    DFHRMUTIL to update the CICS catalog record.
    Using DFHRMUTIL, if SET_AUTO_START=AUTODIAG is specified,
    it will cause the next start of the CICS region to be a
    "diagnostic run".
    .
    Sample JCL as defined in the CICS Operations and Utilities
    Guide but showing the new AUTODIAG parameter:
    //RMUTL    EXEC PGM=DFHRMUTL,REGION=1M
    //STEPLIB  DD DSNAME=link.dataset,DISP=SHR
    //SYSPRINT DD SYSOUT=A
    //DFHGCD   DD DSNAME=catalog.dataset,DISP=OLD
    //SYSIN    DD *
      SET_AUTO_START=AUTODIAG
    .
    SET_AUTO_START=AUTODIAG causes CICS to perform a diagnostic
    run if START=AUTO is coded in the SIT.  It is used for
    documentation gathering only -- CICS does NOT perform any
    recovery and new work is not permitted to enter the system.
    .
    NOTE - following the "diagnostic run", the logstream remains
    unchanged.  In the case of a failed logstream, an initial start
    of the CICS region must performed.
    .
    Following the "diagnostic run", if PQ24842 is not applied,
    the catalog record must be reset, using DFHRMUTIL.
    If the catalog record is not reset, each time
    a START=AUTO is requested, a diagnostic run is performed.
    .
    Documentation required for analysis of a CICS/MVS Logger
    problem usually requires a dump of the CICS address space
    and a dump of the MVS logger address space when the error is
    detected.
    .
    The logstreams should be printed using DFHJUP (PQ04998 level or
    higher), and the offload datasets saved (IDCAMS REPRO).
    .
    Issue the D LOGGER and D LOGGER,L commands (introduced in
    OW27153) and retain the output.
    .
    Many problems require dumping of the coupling facility
    structure associated with the logstream in error. The
    IXCMIAPU utility is used to identify which structure
    contains a given logstream.
    .
    //LOGRRPT  EXEC PGM=IXCMIAPU
    //SYSPRINT DD SYSOUT=*
    //SYSIN    DD *
     DATA
       TYPE(LOGR)
       REPORT(YES)
       LIST LOGSTREAM NAME(logstream_name) DETAIL(YES)
    
    .
    The following SLIP trap may be used to capture a dump of the
    CICS address space, Logger address space, and the structure
    associated with the failing logstream.
    NOTE - this may result in a an extra dump of both CICS and
           the logger address space
    .
    The sample SLIP provided is such that it will just fit in
    the extended operator command area on MVS V5.  The xx,yy,zz
    values must be replaced with the appropriate operator reply
    numbers as each segment is entered.
    
    In the example, the SLIP will trigger when a DFHLG077x
    message is written to the console.  This is set up in the
    EQ parameter of the SLIP.
    .
    +4,EQ,C4C6C8D3,+8,EQ,C7F0F7F7),
           D F H L        G 0 7 7
    .
    SLIP SET,IF,LPAMOD=(IGC0003E,0),DATA=(1R?
    +4,EQ,C4C6C8D3,+8,EQ,C7F0F7F7),A=SVCD,JOB  <change the message
    LIST=(cicsjob,IXGLOGR,XCfAS),              <change CICS Job
    -->response xx
    xx,DSPNAME=('XCFAS'.*,'IXGLOGR'.*),STRLIS
    T=(STRNAME=LOG_SYSTEST_001,LOCKENTRIEs,AC  <change STRNAME
    C=NOLIM,(LISTNUM=ALL,
    -->response yy
    yy,ENTRYDATA=SERIALIZE,ADJUNCT=CAPTURE)),
    SDATA=(RGN,XESDATA,ALLNUC,CSA,LSQA,PSA,SQ
    SWA,TRT,COUPLE,WLM,GRSQ,LPA),
    -->response zz
    zz,ID=LOGR,REMOTE=(JOBLIST,DSPNAME,SDATA)
    ,END
    For those running DASD ONLY LOGGER, use the following SLIP:
    SLIP SET,IF,LPAMOD=(IGC0003E,0),
    DATA=(1R?+4,EQ,C4C6C8D3,+8,EQ,C7F0F7F7,+C,EQ,F2),
    JOBLIST=(cicsjob,IXGLOGR,XCFAS),A=SVCD,         <change CICS Job
    DSPNAME=('IXGLOGR'.*,'XCFAS'.*),
    SDATA=(RGN,ALLNUC,LSQA,SWA,CSA,PSA,SQA,
    TRT,WLM,GRSQ,LPA),ID=LOGR,
    REMOTE=(JOBLIST,DSPNAME,SDATA),END
    

Local fix

  • Jim Grauel
    CICS Support Center
    RTP
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • close for INTERNET viewing
    

APAR Information

  • APAR number

    II10834

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1997-10-01

  • Closed date

    1997-11-01

  • Last modified date

    2000-09-06

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
06 September 2000