IBM Support

PI41397: DLI SC04 IN FSYGDBD0

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ================================================================
    PMR 50027,999,000 - DLI SC04 in FSYGDBD0  and
    
    PMR 18169,082,000 - Problems with migration from EZT to IMU
    
    Date reported: 05/07/2015
    =============
    
    Severity: High
    =========
    
    Users Affected:
    ==============
    All IMU users of MU V4.1
    
    Problem Description:
    ===================
    IMS/DLI programs are ABENDing for SC04. This occurs when there
    are no fields defined within segments in the DBD definitions.
    
    
    Problem Summation:
    ==================
    The program FSYGDBD0 walks thru the DBD definitions in attempt
    to build an SSA string. The SSA string is defined of the
    segment name and the key for that segment. The key is the
    1st defined field in the DBD for the specified segment.
    
    The problem is that when there are no fields available, the
    field displacement generated in the DBD is x'ffffffff' (i.e -1).
    
    The logic in FSYGDBD0 does not check for 'no fields', therefore
    it ABENDs due to x'ffffffff' in the displacement field.
    
    Note: The SSA is built for all Parent segments used in the
    RETRIEVE statement. The key must be defined as IMU uses it to
    build the SSA string.
    
    Problem Conclusion:
    ===================
    The FSYGDBD0 logic was changed to check for no fields and issue
    a message if none exist.
    
    A message is issued and the JOB is abnormally terminated.
    
    The work-around is to define (in the DBD) one or more fields
    for the segments in error.
    
    Impact on existing programs:
    ===========================
    There is no impact on existing programs that work properly.
    IMS/DLI programs that are getting SC04  must be re-compiled
    and linked after the APAR is applied.
    
    Changed modules:
    ===============
    FSOFT01.V4R1M0.SFSYLOAD
     FSYGDBD0 - existing module
    ===============================================================
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMU users of MU V4.1                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: IMS/DLI programs are ABENDing for SC04. *
    *                      This occurs when there are no fields    *
    *                      defined within segments in the DBD      *
    *                      definitions.                            *
    ****************************************************************
    * RECOMMENDATION: apply the PTF.                               *
    ****************************************************************
    The program FSYGDBD0 walks thru the DBD definitions
    in attempt to build an SSA string. The SSA string is
    defined of the segment name and the key for that
    segment. The key is the 1st defined field in the DBD
    for the specified segment.
    
    The problem is that when there are no fields
    available, the field displacement generated in the
    DBD is x'ffffffff' (i.e -1).
    
    The logic in FSYGDBD0 does not check for 'no fields',
    therefore it ABENDs due to x'ffffffff' in the
    displacement field.
    
    Note: The SSA is built for all Parent segments used
          in the RETRIEVE statement. The key must be defined
          as IMU uses it to build the SSA string.
    

Problem conclusion

  • The FSYGDBD0 logic was changed to check for no fields
    and issue a message if none exist. A message is issued
    and the JOB is abnormally terminated.
    
    The work-around is to define (in the DBD) one or more
    fields for the segments in error.
    
    Impact on existing programs
    
    There is no impact on existing programs that work properly.
    IMS/DLI programs that are getting SC04 must be re-compiled
    and linked after the APAR is applied.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI41397

  • Reported component name

    MIGRATION UTILI

  • Reported component ID

    5697N4400

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-19

  • Closed date

    2015-08-14

  • Last modified date

    2015-09-02

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

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

Modules/Macros

  •    FSYGDBD0
    

Fix information

  • Fixed component name

    MIGRATION UTILI

  • Fixed component ID

    5697N4400

Applicable component levels

  • R410 PSY UI30225

       UP15/08/19 P F508

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":"SSY4B9","label":"IBM Migration Utility for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
27 October 2020