IBM Support

PK79539: Rational Business Developer V7.1.0: generation of dynamic prepa re statements not handled properly

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Rational Business Developer V7.1.0:
    
    Gneration of dynamic prepare statements not handled properly
    by the COBOL generator.  The default SQL prepare data area is
    not large enough for certain prepare statements.  EGL needs to
    calculate the minimum required at generation time and ensure
    that a sufficient size is defined.
    
    Symptoms include the following:
    
    1) -104 SQLCODE preparing generated COBOL program.
    2) -803 SQLCODE running generated COBOL program.  Once scenario
        is also followed by an endless loop.
    

Local fix

  • The current default size of the SQL prepare area is not large
    enough to handle the prepare statement in certain EGL
    applications.  The WORKFIELDLENGTH symbolic parameter in the
    build descriptor can be used to change the size of the SQL
    prepare area.
    
    If an EGL application needs 3300 bytes, the WORKFIELDLENGTH can
    be set to 4000.
    
    Note:  Care must be taken with this parameter, however, because
           it affects other memory usage and can cause a program to
           start to use a lot of memory (wasted as well).
    
    To set this default value to 4000, do this in the build
    descriptor used for the generation:
    
      add a symbolic parameter (on the right hand side of the
                                display)
    
        WORKFIELDLENGTH
    
      and set the value to 4000
    
    When the COBOL program is regenerated, and the following should
    be seen in the COBOL program (4000 in the PIC X field):
    
           01  EZESQL-PREPARE.
               49  EZESQL-PREPARE-LENGTH PIC S9(4) USAGE COMP-4.
               49  EZESQL-PREPARE-DATA PIC X(4000).
    

Problem summary

  • The default SQL prepare area was insufficient to hold the
    prepare statement being created by the application. Normally
    this would get a SQL error back on the prepare, but in this
    case it happened to truncate the statement exactly at a
    place where the statement was still valid, but not what was
    wanted. The software has been modified to calculate the
    minimum area required for any prepare statement in the
    program, and create a COBOL prepare area at least as large
    as the maximum + 1000 extra bytes.
    

Problem conclusion

  • Software updated. Fixtest EGLFixtest200901271507 is
    available on the portal.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK79539

  • Reported component name

    RBD EGL FOR COB

  • Reported component ID

    5724S5001

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-27

  • 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

    RBD EGL FOR COB

  • Fixed component ID

    5724S5001

Applicable component levels

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

Document Information

Modified date:
20 March 2009