IBM Support

PI76459: RATIONAL DEVELOPER FOR SYSTEM Z (RDZ) NO WAY TO SPECIFY <NM2>MODULENAME,PROGRAM REQUIRED BY EQUAOPTS FILE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In RDz v9.5.1.3 ther is a change from previous versions that
    generates
    wrong <NM2> tag.
    
    Prior to RDz 9513, the Remote DB2 Application and Remote IMS
    Application
    debug configurations generated the following tag in the EQAUOPTS
    file:
    <PGM>program
    
    After the update to RDz 9513, the debug configurations generate
    the tag
    <NM2>*,program
    
    However, the field in the debug configurations is labeled Load
    Module
    (not program), which is conflicting and should produce:
    <NM2>modulename,*
    
    There is no way to specify <NM2>modulename,program
    as per the format of the EQAUOPTS file.
    

Local fix

  • Manually change EQUAOPTS after generation.
    

Problem summary

  • When using the Remote DB2 Application or Remote IMS Application
    debug configurations in RDz, there is no way to specify module
    and program, such that
    <NM2>modulename,program
    is generated in the remote debug profile (the EQAUOPTS file).
    

Problem conclusion

  • The Remote DB2 Application or Remote IMS Application debug
    configurations have been adjusted as follows:
    When a user specifies modules seperated by comma (,) as per the
    user interface
    ie MODULE1,MODULE2
    The following will be generated:
    <NM2>MODULE1,*
    <NM2>MODULE2,*
    In the remote debug profile (the EQAUOPTS file)
    If a user wishes to specify program, then they must also specify
    module name, and use semi-colon(;) as separator. For example:
    1) To specify PROGRAM1 with no module:
    *;PROGRAM1
    which will generate:
    <NM2>*,PROGRAM1
    2) To specify several modules and programs,in different
    combinations:
    *;PROGRAM1,MODULE2;PROGRAM2,MODULE3
    which will generate:
    <NM2>*,PROGRAM1
    <NM2>MODULE2,PROGRAM3
    <NM2>MODULE3,*
    
    The problem listed in this APAR has been resolved with
    IBM Rational Developer for z Systems V9.5.1.4 Fix Pack which
    is available from the Recommended Fixes support download page:
    http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI76459

  • Reported component name

    DEV FOR Z SYS

  • Reported component ID

    5724T0700

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-10

  • Closed date

    2017-02-23

  • Last modified date

    2017-02-23

  • 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

    DEV FOR Z SYS

  • Fixed component ID

    5724T0700

Applicable component levels

  • R951 PSY

       UP



Document information

More support for: Rational Developer for System z

Software version: 950

Reference #: PI76459

Modified date: 23 February 2017