IBM Support

PK28459: DEPENDENT SEGMENTS NOT BEING OUTPUTTED BY ONLINE DATA EXTRACT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Online Data Extract cannot output dependent segments
    although dependent segments are specified for output.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Online Data Extract users of High        *
    *                 Performance Fast Path Utilities FP Online    *
    *                 Tools Version 2 Release 2 (FMID: H31A220).   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Online Data Extract (ODE) does not      *
    *                      extract the dependent segments          *
    *                      specified on OUTPUT control statement   *
    *                      in FPXCTL DD statement.                 *
    ****************************************************************
    * RECOMMENDATION: Apply the maintenance for this APAR.         *
    ****************************************************************
    Despite specifying the parent segement on SELECT statement and
    the dependent segments on OUTPUT statement, ODE doesn't extract
    the dependent segments. This trouble is caused by PTF/APAR
    UK10345/PK16264 (OPC/ODE site default support).
    
    For example, the segname2 and segname3 are not extracted in the
    following specification.
    
      //FPXCTL  DD    *
      FPXCTL ..................
      SELECT SEG=segname1,FIELD=(.....)
      SELECT SEG=segname1,FIELD=(.....)
      SELECT SEG=segname1,FIELD=(.....)
      OUTPUT SEG=segname1
      OUTPUT SEG=segname2
      OUTPUT SEG=segname3
    
      segname2, segname3: the child segments of the segname1
    

Problem conclusion

  • The extraction condition address was saved in the ODE local area
    and only one module referred it prior to APAR PK16264.
    PK16264 divides the module into two modules, but the extraction
    condition address was kept into the ODE local area.
    Therefore ODE couldn't determine these extraction conditions.
    The extraction condition address is defined into the common
    block.
    
    The macro FPXMBLK has been modify to add the address area
    of the save area of extraction conditions as a global area.
    
    The module FPXPARM1 and FPXPANA0  has been modify to change
    the address area of the save area from a local area to
    a global one to check the extraction conditions.
    220Y
    FPXMBLK
    FPXMBLK0
    FPXPANA0
    FPXPARM1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK28459

  • Reported component name

    IMS HP FP UTILI

  • Reported component ID

    5655K9400

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2006-07-20

  • Closed date

    2006-07-26

  • Last modified date

    2006-08-02

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

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

    UK16597

Modules/Macros

  •    FPXMBLK  FPXMBLK0 FPXPANA0 FPXPARM1
    

Fix information

  • Fixed component name

    IMS HP FP UTILI

  • Fixed component ID

    5655K9400

Applicable component levels

  • R220 PSY UK16597

       UP06/07/28 P F607 Ø

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX89D","label":"IMS HP Fast Path Utilities"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2006