IBM Support

PI56109: CSV003I REQUESTED MODULE IGG019Z7 NOT FOUND AT IMS INITIALIZATION AND GOT ABEND S806

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abend S806 for module IGG019Z7 is encountered in IMS V13 MSC CTC
    environment.
    The following message is found in syslog and IMS joblog:
    CSV003I REQUESTED MODULE IGG019Z7 NOT FOUND  at IMS
    initialization.
    .
    LOAD macro has been issued from IFG019RA+0CF0 (HDZ2210 UA70407)
    in PLPA. But IGG019Z9 can not be found in the LPAMAP.
    .
    The the customer's MSPLINK definition and IMS CTL start JCL is
    as follows:
    ---------------------------------------------------------------
    <<MSPLINK MACRO in STAGE1>>
      LINKX MSPLINK DDNAME=MSCA1,ADDR=A3EA,TYPE=CTC,BUFSIZE=4608
    .
    <<IMS CTL JCL/ CTC LINK DDNAME override by following //DD card>
    //GIMS6   PROC RGN=64M,SOUT=G,DPTY='(14,15)',TOPSUF=I6,
    // RGSUF=W,PARM1=,PARM2=,
    // ADD1=AAD0
    //MSCA1    DD UNIT=/&ADD1
    .
    ---------------------------------------------------------------
    IMS V12 APAR PM42918 change to the following design:
    This APAR also removes the logic in IMS that links this module,
    which is the MSC CTC Channel End/Abnormal End appendage
    routine, into LPALIB with a IGG019xx name where xx = the suffix
    selected on the IMS stage1 IMSCTF APNDGF= macro. IMS will
    load the module from reslib during IMS initialization.
    ---------------------------------------------------------------
    But this change was not effective for our customer's CTC device
    type in UCB.
    Then, still call the IGG019Z7 at IMS initialization.
    .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V13 systems using Multiple  System   *
    *                 Coupling (MSC) and channel-to-channel (CTC)  *
    *                 links.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: zOS routine IFG019RA received ABENDS806 *
    *                      attempting to open a CTC DCB and load   *
    *                      the channel-to-channel appendage module *
    *                      DFSCMC10 linked to LPA as IGG019Z7.     *
    *                      Open was issued from IMS initialization *
    *                      routine DFSAINB0.                       *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    As of IMS V13 (APAR PM42918 in IMS V12) the IMS SYSGEN Stage1
    process no longer requires the IMSCTF APNDG= parameter be coded
    to produce a channel end appendage name for channel-to-channel
    (CTC) link DCBs. If specified, it will be ignored and message
    'G018 WARNING: OSAM OR CTC CHANNEL END APPENDAGE IGNORED' is
    issued. The DCB + x'42' is overridden with a NOOP value of
    F040 for OPEN to ingore loading the CE appendage module such as
    IGG109Z7 (default name). IMS now loads the CTC CE appendage
    directly from reslib and stores the address in the DEB DEBCEA
    after OPEN.
    
    In this case the DCB CENDA field was set to x'E9F7' = Z7
    (it's not known why) which caused the OPEN routing IFG019RA to
    attempt to load IGG019Z7 from LPA lib. It was not there so a
    S806 abend was generated.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    Due to a bad compare in DFSAINB0 for a CTC UCB, the CENDA field
    of the CTC DCB was not reset to F040 from E9F7, resulting in
    the attempt to load IGG019Z7.
    
    The DEVTYPE DCBDDNAME,DTYPE1 call returned DEVTYPE UCB VALUE
    x'00004101' = UCBTBYT1, UCBTBYT2, UCBTYPE3, UCPFLC respectively.
    These other values vary due to CTC type and features
    (such as ESCON, FICON) and are not constant and can't be
    compared.
    
    DFSAINB0 wss changed to just compare for the one byte UCB device
    type at DTYPE1+2 for a CTC device instead of the full 4 byte
    device type field, to determine if the CTC DCB needs to be reset
    That is, CLI DTYPE1+2 for UCB3CTC = x'41' instead of DTYPE1
    for x'10014100'.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI56109

  • Reported component name

    IMS V13

  • Reported component ID

    5635A0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-27

  • Closed date

    2016-02-09

  • Last modified date

    2016-03-02

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

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

    PI56261 UI35215

Modules/Macros

  •    DFSAINB0
    

Fix information

  • Fixed component name

    IMS V13

  • Fixed component ID

    5635A0400

Applicable component levels

  • R300 PSY UI35215

       UP16/02/13 P F602 Ž

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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020