IBM Support

PH16116: IBM DEVELOPER FOR Z SYSTEMS (IDZ) MENU MANAGER ACTIONS THAT INVOKE REXX FOR A JES JOB FAIL

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • IBM Developer for z Systems - IDz - v14
    Attempts to invoke a REXX exec for a JES job via Menu Manager
    fail.  No error message is issued.
    
    For instance, on VMSYS1, using USER1.REXX(RCXDC).
    When invoked from the IDz TSO command shell with the input
    below it works well:
    ex 'user1.rexx(rcxdc)' 'JOB10113 VMSYS1 USER1 USER1 USER11 JES2
    JESMSGLG USER1.USER11.JOB10113.D0000002.JESMSGLOG'
    
    However, if invoked by right clicking on the JES Job10113,
    Jes2::JESMSGLG step, the popup dialog is received with the
    input values, and they all look good.
    
    Click OK, and the dialog goes away, but the expected output
    member is not created, nor is it writting to the remote
    console.
    
    Below is the Menu Manager command being used:
    
    exec 'user1.rexx(rcxdc)' '$input(Job ID,$jobid)
    $input(Host Name,$systemhostname) $input(User Id,$userid)
    $input(Job Owner,$jobowner) $input(Job Name,$jobname)
    $input(Step Name,$stepname) $input(DD Name,$ddname)
    $input(JES Dataset Name,$dsname)'
    

Local fix

Problem summary

  • Error when invoking Menu Manager TSO actions from a JES view
    

Problem conclusion

  • Fixed to allow Menu Manager actions to be invoked from the JES
    view.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH16116

  • Reported component name

    DEV FOR Z/OS

  • Reported component ID

    5724T0700

  • Reported release

    E10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-27

  • Closed date

    2019-12-10

  • Last modified date

    2019-12-10

  • 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/OS

  • Fixed component ID

    5724T0700

Applicable component levels

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

Document Information

Modified date:
27 October 2020