IBM Support

PK29164: QMF V81 "CONNECT TO" COMMAND LOOPS ON CONNECT COMMAND PROMPT SCREEN WHEN INVALID SERVER NAME IS ENTERED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the QMF 'CONNECT TO xxxxxxxxx' command is issued for a
    connection that should fail, the user is taken to the 'CONNECT
    Command Prompt' panel, from which the user cannot exit using
    PF3.  Only entering a valid server name, cancelling the user
    id, or causing QMF to abend allows to user to exit the panel.
    QMF issues no error messages indicating the connection was
    unsuccessful; it merely remains on the command prompt panel.
    

Local fix

  • no Work Around
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: QMF for TSO/CICS V8.1 users issuing the      *
    *                 CONNECT command.                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Customers can get into a loop           *
    *                      situation on the CONNECT command        *
    *                      prompt panel (DXYEPC01) following       *
    *                      a CONNECT error condition of            *
    *                      SQLCODE30020. The user might not        *
    *                      be aware the error occurred, but        *
    *                      it should be recorded in the            *
    *                      DSQDEBUG data set.  To exit the         *
    *                      loop, the user has to enter a           *
    *                      valid server name, ABEND out of         *
    *                      QMF or have their userid                *
    *                      cancelled. The user should have         *
    *                      seen the 'Lost Connection' prompt       *
    *                      panel allowing them to exit QMF.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The internal looping problem happens because the SQLCODE30020
    message is not mapped properly in QMF.
    

Problem conclusion

  • The SQLCODE30020 is now mapped to a new QMF message DSQ10431.
    MSGDSQ10431 will not allow for bypass of the 'Lost Connection
    Prompt' panel. DSQ10431 will have the same message text as
    DSQ10424 indicating:
    A communication error has been detected.
    The SQLCA information will also be presented with the new
    message.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK29164

  • Reported component name

    QMF-QUERY MGMT

  • Reported component ID

    566872101

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-08-02

  • Closed date

    2006-08-14

  • Last modified date

    2006-09-05

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

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

    UK17194

Modules/Macros

  • DSQCBRDI DSQCRSNC DSQIMSGM
    

Fix information

  • Fixed component name

    QMF-QUERY MGMT

  • Fixed component ID

    566872101

Applicable component levels

  • R810 PSY UK17194

       UP06/08/16 P F608

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":"SSCWRCK","label":"QMF for TSO\/CICS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
05 September 2006