IBM Support

PK80878: RBD debugger is not consistent with VAGEN expected output

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Environment: Windows XP
    
    Product name: IBM? Rational? Business Developer
    
    Version    :  7.5.1
    Description.
    When debugging a record definition statement that worked  as des
    igned in VAGEN 4.5 the RBD/EGL debugger is not consistent with V
    AGEN expected output.
    
    The VAGEN program uses a record defining eg:
    CHARFIELD CHAR, LENGTH(5)
     |
     --? NUMFIELD NUM(5)
    ANOTHERNUMFIELD NUM (5)
    .
    So NUMFIELD redefines CHARFIELD and ANOTHERNUMFIELD is separate.
    
    The procedure does:
    001 P1-WS.CHARFIELD = '    5';
    002 P1-WS.ANOTHERNUMFIELD = P1-WS.NUMFIELD;
    003 '    '
    
    In VAGEN ITF (the debugger), the result is
    eg:
    CHARFIELD = '    5'
    NUMFIELD = ?Not Valid?
    ANOTHERNUMFIELD = 00005
    
    ANOTHERNUMFIELD contains the right value 00005 although it gives
     a warning on 002: Hpt.CM.455.w
    The value in numeric or packed item P1-WS.NUMFIELD is not valid.
     Do you want to continue.
    
    In RBD/EGL with the following test code
    eg;
    ................
    Record P1-WS type basicRecord
      3 CHARFIELD char(5) ;
        4 NUMFIELD num(5) ;
      3 ANOTHERNUMFIELD num(5) ;
    end // end P1-WS
    
    Function P1-MAIN()
      P1-WS.CHARFIELD = '    5';
      P1-WS.ANOTHERNUMFIELD = P1-WS.NUMFIELD;
      ;
    
    When debugging and then checking the variable values of CHARFIEL
    D.NUMFIELD  the debugger view shows '(num(5, 0)) An error occurr
    ed when displaying the variable named CHARFIELD.NUMFIELD.
    
    The error produced : 'egl.core.RuntimeException: EGL0101E The va
    lue of the CHARFIELD.NUMFIELD variable is not in the correct for
    mat.
    EGL0002I The error occurred in P1 processing the P1-MAIN functio
    n.'
    

Local fix

Problem summary

  • When a NUM field redefines a CHAR field, we were not
    treating the byte data in the same way as VAGen did.
    

Problem conclusion

  • The byte data is now interpreted in the same manner as
    VAGen, so '    5' is a numeric '5' when the redefining field
    is a NUM.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK80878

  • Reported component name

    RATL BUS DEV

  • Reported component ID

    5724S5000

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-18

  • Closed date

    2009-03-20

  • Last modified date

    2009-03-20

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

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

Fix information

  • Fixed component name

    RATL BUS DEV

  • Fixed component ID

    5724S5000

Applicable component levels

  • R750 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
20 March 2009