IBM Support

PM32030: IMU DOES NOT FULLY SUPPORT IDMS IDD AND RETRIEVE STATEMENT.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Per Internal PMR 42924,999,000
    
    ================================================================
    Date opened: 01/01/2011
    
    Severity: N/A
    
    Users Affected:
     IDMS users of IDD and RETRIEVE Statement
    
    Problem Description:
     IMU does not fully support IDMS IDD and RETRIEVE statement.
    
    Problem Summation
     The IDD and RETRIEVE statement support was never fully
    implemented.
    
    Problem Conclusion:
     Changes were made to support IDMS SUBSCHEMA, IDMS RECORD and
     RETRIEVE statement syntax.
     The following IMU macros were impacted:
    
     EASYT007
     IDMSRETR
     IDDSCHEM
     IDDRGEN0
     IDDCNVRT
    ================================================================
    
    ================================================================
    And PMR 54646,004,000 - Abend SC0A decimal overflow exception
    
    
    Date reported: 02/16/2011
    
    Severity: low
    
    Users Affected:
     All IMU users of MU V3.2
    
    Problem Description:
     Customer is getting SC0A exception (decimal overflow) but
     program continues to run.
    
    Problem Summation
      Overflow exception is not a program interrupt ( as per z/OS
      architecture) unless bit 21 in the PSW is set on.
    
      It is up to the user to check for overflow after arithmetic
      instructions.
    
     1.  When MU's ESPI is not on, there is no way to trap field
         overflow condition. The system simply ignores it and
         expects programmer to test condition code after each
         arithmetic instruction.
    
         The only way out would be to add ON SIZE ERROR test after
         every math operation.
         This would be too costly, The CPU usage could skyrocket.
    
     2.  When MU ESPI is on, overflow is detected and an ABEND
         report is created, however, MU percolates ESPI exit
         to other potential handlers (such as LE)  but LE does not
         trap such condition, thus program ends with RC=0.
    
    Problem Conclusion:
     ABEND was added to DEBUG=(...) option of EASYTRAN/EASYPARAMS
     table. When DEBUG=(ABEND, ESPI/ESPI-PART/ESPY-FULL) is
     specified, the IMU ESPI handler FSYESPI1 program was changed
     to issue "ABEND 3000" to terminate the process.
    
     If ABEND is not specified and ESPI/ESPI-PART/ESPI-FULL is
     specified, the IMU ESPI handler FSYESPI1 program percolates
     this issue to LE and other potential interrupt handlers.
    
     Notes:
     1. The LE run-time options TRAP(ON,SPIE) and
        ABTERMENC(ABEND)are required, If your installation is using
        different parameters for these two options, override them
        by coding a DD statement in the application JCL.
    
    
     Example:
      a.  Create CEEOPTS file in SYS1.V3R2M0.SFSYEZTS PDS and add
          the following to it:
    
          ABTERMENC(ABEND)
          TRAP(ON,SPIE)
    
      b.  Add the following DD statement to your application JCL
          when you executing linked programs, or to IMU translator
          JCL when you are running Link & Go.
    
          //CEEOPTS  DD  DSN=SYS1.V3R2M0.SFSYEZTS(CEEOPTS),DISP=SHR
    
    
      Note: For Link & Go, a DD statement can be added to the LKGO
            step in the #EZTPROC PROC.
    
    
    
    Affected Modules:
     FSYESPI1 - Load module in SFSYLOAD
    
     FSYESPI2 - Load module in SFSYLOAD
    
     EASYT007 - CCL1 macro in SFSYFJCC
    
     PENGIEND - CCL1 macro in SFSYFJCC
    
     COBOLBAS - CCL1 macro in SFSYCCLM
    ================================================================
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMU v320 Users                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: IMU does not fully support IDMS IDD     *
    *                      and RETRIEVE statement.                 *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    

Problem conclusion

  • Changes were made to support IDMS SUBSCHEMA, IDMS RECORD and
    RETRIEVE statement syntax.
    The following IMU macros were impacted:
    
    EASYT007
    IDMSRETR
    IDDSCHEM
    IDDRGEN0
    IDDCNVRT
    ==========================================================
      Overflow exception is not a program interrupt ( as per z/OS
      architecture) unless bit 21 in the PSW is set on.
    
      It is up to the user to check for overflow after arithmetic
      instructions.
    
     1.  When MU's ESPI is not on, there is no way to trap field
         overflow condition. The system simply ignores it and
         expects programmer to test condition code after each
         arithmetic instruction.
         The only way out would be to add ON SIZE ERROR test after
         every math operation.
         This would be too costly, The CPU usage could skyrocket.
    
     2.  When MU ESPI is on, overflow is detected and an ABEND
         report is created, however, MU percolates ESPI exit
         to other potential handlers (such as LE)  but LE does not
         trap such condition, thus program ends with RC=0.
    
    ABEND was added to DEBUG=(...) option of EASYTRAN/EASYPARAMS
    table. When DEBUG=(ABEND, ESPI/ESPI-PART/ESPY-FULL) is
    specified, the IMU ESPI handler FSYESPI1 program was changed
    to issue "ABEND 3000" to terminate the process.
    
    If ABEND is not specified and ESPI/ESPI-PART/ESPI-FULL is
    specified, the IMU ESPI handler FSYESPI1 program percolates
    this issue to LE and other potential interrupt handlers.
    
    Notes:
    
    1. The LE run-time options TRAP(ON,SPIE) and
       ABTERMENC(ABEND)are required, If your installation is using
       different parameters for these two options, override them
       by coding a DD statement in the application JCL.
    
    
    Example:
     a.  Create CEEOPTS file in SYS1.V3R2M0.SFSYEZTS PDS and add
         the following to it:
    
         ABTERMENC(ABEND)
         TRAP(ON,SPIE)
    
     b.  Add the following DD statement to your application JCL
         when you executing linked programs, or to IMU translator
         JCL when you are running Link & Go.
    
         //CEEOPTS  DD  DSN=SYS1.V3R2M0.SFSYEZTS(CEEOPTS),DISP=SHR
    
    Note: For Link & Go, a DD statement can be added to the LKGO
          step in the #EZTPROC PROC.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM32030

  • Reported component name

    MIGRATION UTILI

  • Reported component ID

    5697N4400

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-07

  • Closed date

    2011-04-19

  • Last modified date

    2011-05-02

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

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

    UK66901

Modules/Macros

  •    FSYCARD0 FSYCOBAS FSYCVPRC FSYESEND FSYESPI1
    FSYESPI2 FSYET007 FSYIDDCV FSYIDDG0 FSYIDMSR FSYIDSCH FSYPNEND
    FSYTPA00 FSYZTPRC
    

Fix information

  • Fixed component name

    MIGRATION UTILI

  • Fixed component ID

    5697N4400

Applicable component levels

  • R320 PSY UK66901

       UP11/04/21 P F104

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":"320","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
27 October 2020