IBM Support

PI51725: MAKE "DEFAULT" INITIAL TARGET BE FROM THE MAINFRAME SYSTEM USED TO LOG IN TO THE ACTIVITY BROWSER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • When the user logs in to the Browser client, they have to select
    a mainframe system to authenticate against. It would improve
    usability if the "Target" pulldown defaulted to a QM Subsystem
    that is on that system.
    
    In particular, take the situation where there are two systems,
    SYSA, and SYSB, and the user has different passwords on each. If
    the user initially logs in using, say, SYSB, and the Target
    pulldown currently defaults to SYSA, the current implementation
    will result the user immediately being presented with second
    login dialog, looking like they have to login to SYSA. It is not
    obvious to the user that they can cancel out of this second
    login dialog.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor z/OS.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the user logs in to the Browser    *
    *                      client, they have to select a           *
    *                      mainframe system to authenticate        *
    *                      against. It would improve usability if  *
    *                      the "Target" pulldown defaulted to a    *
    *                      QM Subsystem that is on that system.    *
    *                      In particular, take the situation       *
    *                      where there are two systems, SYSA, and  *
    *                      SYSB, and the user has different        *
    *                      passwords on each. If the user          *
    *                      initially logs in using, say, SYSB,     *
    *                      and the Target pulldown currently       *
    *                      defaults to SYSA, the current           *
    *                      implementation will result the user     *
    *                      immediately being presented with        *
    *                      second login dialog, looking like they  *
    *                      have to login to SYSA. It is not        *
    *                      obvious to the user that they can       *
    *                      cancel out of this second login dialog. *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

Temporary fix

Comments

  • APPLY the PTF.
    

APAR Information

  • APAR number

    PI51725

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    320

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-02

  • Closed date

    2016-02-16

  • Last modified date

    2016-03-02

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

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

    UI35392

Modules/Macros

  • CQMBLOB  CQMCAEPT CQMCPXPT CQMJAR
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R320 PSY UI35392

       UP16/02/18 P F602

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020